Published on March 12, 2014
The Product Owner and the Scrum Team Can one person do this at scale? Derek Huether, Enterprise Agile Coach LeadingAgile
Derek Huether – Enterprise Agile Coach Twitter: @derekhuether or @leadingagile Google: +derekhuether or +leadingagile LinkedIn: /derekhuether or /company/leadingagile
What makes Agile great?
Simple by Design
4 Values Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
12 Principles Satisfy the Customer Welcome Change Deliver Frequently Collaborate Daily Support & Trust Motivated Teams Promote Face-to-Face Conversations Deliver Working Software Promote Sustainable Pace Promote Technical Excellence Maximize Through Simplicity Have Self-Organized Teams Reflect & Adjust Regularly
Incremental Iterative 1 2 3 1 2 3
What makes Scrum a great Agile delivery framework?
Simple by Design
Scrum Framework Scrum Team 1. Product Owner 2. Development Team 3. Scrum Master Scrum Events 1. The Sprint 2. Sprint Planning 3. Daily Scrum 4. Sprint Review 5. Sprint Retrospective Scrum Artifacts 1. Product Backlog 2. Sprint Burndown 3. Delivery Increment
What is a Product Owner? The Product Owner is the sole person responsible for managing the Product Backlog. Product Backlog management includes: Clearly expressing Product Backlog items; Ordering the items in the Product Backlog to best achieve goals and missions; Optimizing the value of the work the Development Team performs; Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and, Ensuring the Development Team understands items in the Product Backlog to the level needed.
Product Owner Success 1. For the Product Owner to succeed, the entire organization must respect his or her decisions. 2. The Product Owner’s decisions are visible in the content and ordering of the Product Backlog. 3. No one is allowed to tell the Development Team to work from a different set of requirements, and the Development Team isn’t allowed to act on what anyone else says.
Product Owner is a BIG Job! • Product Manager… vision and direction • Project Manager… sequence and status • Business Analyst… elaborating requirements • Quality Assurance… inspecting outcomes • Management… terminating and changing • User Experience… usability • Team Member… participates with the team
The downside of Agile (including Scrum) is the same thing that makes it great Last 10 years have been team focused Next 10 years must be enterprise focused
How do we scale Scrum and the Product Owner role?
Analysts Testers Developers Product Owner Scrum Master SME’s Clarity (Scope) User Story Accountability (Structure & Governance) Measurable Progress (Deliverables & Metrics) User Story User Story User Story User Story User Story User Story Screen Updates Databases Updates Reports
Clarity Different Scope for Different Timelines
Scope • Epics ( < 1 release) • Features ( < 1 sprint) • User Stories (3-5 days) • Tasks (< 8hrs)
Accountability (Structure) Different Teams for Different Jobs
Team Portfolio Teams – These teams govern the portfolio and make sure that work is moving through the system. Programs Teams – These teams define requirements, set technical direction, and provide context and coordination. Product Teams – These teams integrate services and write customer facing features. This is the proto-typical Scrum team. Services Teams – These teams support common services across product lines. These teams support the needs of the product teams. PO Team Team Team
Team Team PO Team Team Portfolio Teams – These teams govern the portfolio and make sure that work is moving through the system. Programs Teams – These teams define requirements, set technical direction, and provide context and coordination. Product Teams – These teams integrate services and write customer facing features. This is the proto-typical Scrum team. Services Teams – These teams support common services across product lines. These teams support the needs of the product teams.
Team PO Team Team PO Team Team Team PO Team Team Team Team Team Team Product & Services Teams Program Teams Portfolio Teams Scrum Kanban Kanban
Accountability (Governance) Roles and Responsibilities Inputs and Outputs
Portfolio Teams - Epics Inception Elaboration Construction Transition Program Teams - Features Analysis and Design Build Integrate Stage Product & Services - Stories Ready DoneIn Progress Sprint(s) Release Release Sprint(s) Portfolio Planning Release Planning Sprint Planning Daily Planning
Measurable Progress (Deliverables) Epics, Features, Stories
Portfolio Teams - Epics Inception Elaboration Construction Transition Program Teams - Features Analysis and Design Build Integrate Stage Product & Services - Stories Ready DoneIn Progress Sprint(s) Release Release Sprint(s) Epics Features Stories
Measurable Progress (Metrics) Structure, Adoption, Governance
Structure Governance Metrics Adoption
To be successful in the next 10 years, do you still think one person can do all this?
Canvas Prints at Affordable Prices make you smile.Visit http://www.shopcanvasprint...
30 Días en Bici en Gijón organiza un recorrido por los comercios históricos de la ...
Con el fin de conocer mejor el rol que juega internet en el proceso de compra en E...
With three established projects across the country and seven more in the pipeline,...
Retailing is not a rocket science, neither it's walk-in-the-park. In this presenta...
Product Owner. The Scrum product owner is typically a project's key stakeholder. Part of the product owner responsibilities is to have a vision of what he ...
The thing I don’t see here is how to ensure that the Product Owner team doesn ... how do we ensure that the Product Owner does ... one person can fill ...
The Product Owner is the Team member who ... (and the team). If they don't have it, they can't do ... Scaling Scrum Scaling Srum Scrum@Scale Scrum at Scale ...
Each scrum team is made up of Development team + Scrum Master + Product Owner. ... can happen that one person cannot do ... product ownership does not ...
Why a Product Owner Team? ... to deal with the challenges of the Scrum Product Owner at scale. ... requires more than one person to do ...
A Scrum team can easily scale to ... New roles in a Scrum team are the ScrumMaster or product owner. ... one person who attends the Scrum of Scrums ...
... This post discusses scaling the product owner role ... can be managed by one product owner, ... between the teams, running Scrums of Scrums ...
Scrum teams should have one product owner, ... the product owner and the scrum team come ... This is done by the development team asking "Can we also do ...
The Product Owner (PO) is the member of the team ... At scale, a single person cannot handle product and ... can be responsible for the backlog for one or ...