Product Ownership is a Team Sport
A number of agile brands downplay the need for business analysis and requirements management on agile projects, putting large store in the role of the Product Owner. This workshop tackles some of the problems this misconception can result in and shows how effective product ownership almost always requires a team with a variety of skills and backgrounds to be effective. Product Ownership requires clarity of vision, alignment with organisational strategy, understanding of the development process and the ability to communicate with a wide variety of stakeholders across all levels both inside and outside the organization. The complexity of the role is most often more than a single person can (or should) cope with – effective product ownership requires a teamwork approach covering a variety of skills and knowledge. Product ownership encompasses areas covering: * Product Management * Marketing * Business Advocacy * Customer Advocacy * End User Advocacy * Domain Subject Matter Knowledge * Analysis * User Experience and Graphic Design * Innovation * Communications * Decision Making * Legal and Compliance Details: http://confengine.com/agile-pune-2014/proposal/835/product-ownership-is-a-team-sport Conference: http://pune.agileindia.org/
Recommended
Recommended
More Related Content
More from Naresh Jain
More from Naresh Jain (20)
Recently uploaded
Recently uploaded (20)
Product Ownership is a Team Sport
- 1. 11/22/2014 1 Hi -I’m Shane
- 2. 11/22/2014 2 Agenda ▪ ▪ ▪ ▪ ▪ ▪ The Product Owner ▪
- 3. 11/22/2014 3 6 Project Types ▪ ▪ ▪ ▪ ▪ ▪
- 4. 11/22/2014 4 The Cinderella Project ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ ▪ Your Project
- 5. 11/22/2014 5 The Octopus ModelProduct Ownership • • • • • • • • • • • •
- 6. 11/22/2014 6 Product Ownership TeamDelivery Team
- 7. 11/22/2014 7 14 Decreasing queue length
- 8. 11/22/2014 8 What’s in that BacklogValue Focus
- 9. 11/22/2014 9 Knowing when to Stop 19
- 11. 11/22/2014 11 Of Babies & BathwaterValue Stream Mapping (VSM) ▪ ▪ ▪ ▪ ▪ ▪
- 12. 11/22/2014 12 Value Stream Mapping Customer Requests a New Account Help Desk Submits Request Processed for Initial Approval New Account Entered into System Help Desk Notified Customer informed new account is established 0.5Hrs 0.5Hrs 1Hr 1Hr 0.5Hrs 12Hrs 24Hrs 48Hrs 24Hrs 48Hrs 24Hrs 1Hr Total Process Time: 6.5Hrs Total Elapsed Time: 180Hrs 180Hrs 6.5Hrs = Process Productivity = 3% Final Approval Customer Folder Created 2 HrsPurpose Alignment Model Market Differentiation Mission Criticality High High Low Low
- 13. 11/22/2014 13 Vision ▪ ▪ ▪ ▪ ▪ ▪ ▪ Tools for Discussing Objectives & Scope OFF ON have a satisfied client group/s meet the project's objectives/requirements meet an agreed budget - resources, capital, equipment deliver the product on time add value for the organisation meet quality requirements have a sense of professional satisfaction for the team Off - Success Factor is not relevant. It is measured however. On - Success Factor is relevant. Degree of relevance is indicated by position of “slider”. OFF ON OFF ON OFF ON OFF ON OFF ON OFF ON
- 14. 11/22/2014 14 Kano Analysis ▪ ▪ 29
- 15. 11/22/2014 15 ImaginationIn Conclusion ▪ ▪ ▪ ▪ ▪ ▪
- 16. 11/22/2014 16 Questions? Contact Information