The Product Owner and Complex Projects
The Scrum framework is a structure that allows the management of complex projects in an easier way, by delivering pieces of work, by empowering the scrum team and by welcoming changes along the way. The Product Owner is the one who will create the product backlog and prioritize the tasks.
The Scrum Framework
The Agile Scrum framework is designed to deliver products and projects of any size. This includes projects, programs, and portfolios. Scrum provides guidelines on delivery techniques, events, and roles. Many of the same ceremonies are held within both a standard Agile scrum project and an Agile Scrum program focusing on the larger enterprise. The same goes for team member roles and scrum artifacts. Within both types of projects and programs, the Scrum Master’s role remains a focal champion of adherence to the Scrum framework to deliver the highest value features in a prioritized order to meet the established Return on Investment (ROI) for the executing organization. Differences are noted in the execution around the framework of principles, ceremonies, and roles.
Scrum Principles
Agile Scrum utilizes several principles whether delivery is by a single scrum team or a larger enterprise initiative using program delivery methodologies. The Scrum Master is the facilitator, coach, and champion who protects the larger team while delivering. Six of the primary principles adhered to with Agile scrum are:
● Transparency – Inspect and Adapt
● Self-Organizing teams
● Team collaboration
● Value-based prioritization
● Time-boxed delivery and
● Iterative development.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course:
Course Contents
Section 1: Agile Project Management
Section 2: Using the Agile Manifesto to Deliver Change
Section 3: The 12 Agile Principles
Section 4: The Agile Fundamentals
Section 5: The Declaration of Interdependence
Section 6: Agile Development Frameworks
Section 7: Introduction to Scrum
Section 8: Scrum Projects
Section 9: Scrum Project Roles
Section 10: Meet the Scrum Team
Section 11: Building the Scrum Team
Section 12: Scrum in Projects, Programs & Portfolios
Section 13: How to Manage an Agile Project
Section 14: Leadership Styles
Section 15: The Agile Project Life-cycle
Section 16: Business Justification with Agile
Section 17: Calculating the Benefits With Agile
Section 18: Quality in Agile
Section 19: Acceptance Criteria and the Prioritised Product Backlog
Section 20: Quality Management in Scrum
Section 21: Change in Scrum
Section 22: Integrating Change in Scrum
Section 23: Managing Change in Scrum
Section 24: Risk in Scrum
Section 25: Risk Assessment Techniques
Section 26: Initiating an Agile Project
Section 27: Forming the Scrum Team
Section 28: Epics and Personas
Section 29: Creating the Prioritised Product Backlog
Section 30: Conduct Release Planning
Section 31: The Project Business Case
Section 32: Planning in Scrum
Section 33: Scrum Boards
Section 34: Sprint Planning
Section 35: User Stories
Section 36: User Stories and Tasks
Section 37: The Sprint Backlog
Section 38: Implementation of Scrum
Section 39: The Daily Scrum
Section 40: The Product Backlog
Section 41: Scrum Charts
Section 42: Review and Retrospective
Section 43: Scrum of Scrums
Section 44: Validating a Sprint
Section 45: Retrospective Sprint
Section 46: Releasing the Product
Section 47: Project Retrospective
Section 48: The Communication Plan
Section 49: Formal Business Sign-off
Section 50: Scaling Scrum
Section 51: Stakeholders
Section 52: Programs and Portfolios