Product ownership in scrum

848 views

Published on

2010-11-13, Agile Saturday, Estonia

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
848
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
21
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Product ownership in scrum

  1. 1. ©2010TietoCorporation Product Owning Kaimar Seljamäe Software analyst Tieto, kaimar.seljamae@tieto.com
  2. 2. 2010-11-132 © 2010 Tieto Corporation Agile Saturday Agenda • Introduction • Customer expectations • Team expectations • What does the Product Owner do? • Preparation phase • Sprint planning meeting • During sprint • Sprint Review and Retrospective meeting • Waterfall + Scrum?
  3. 3. 2010-11-133 © 2010 Tieto Corporation Agile Saturday In short: the Product Owner… • represents the voice of the customer • ensures that the Scrum Team works with the “right things” from a business perspective
  4. 4. 2010-11-134 © 2010 Tieto Corporation Agile Saturday Source: http://www.microtool.de/instep/en/scrum.asp
  5. 5. 2010-11-135 © 2010 Tieto Corporation Agile Saturday Customer expectations To achieve business goals, I as a customer wish to: • declare the business priority of every User Story; • have an overall plan; • get the most possible value out of every development week; • see progress in a running system; • change my mind, product functionality, priorities; • be informed of schedule changes. Based on eXtreme Programming teamwork practices.
  6. 6. 2010-11-136 © 2010 Tieto Corporation Agile Saturday Team expectations To be productive, as a team member I expect: • clear and consistent description of expected result; • effective communication with domain experts; • quick feedback from customer; • freedom to plan my own work; • feeling that my commitment is appreciated; • being proud of what I do; • firm belief that success is possible; • reasonable freedom to choose tools and technology.
  7. 7. 2010-11-137 © 2010 Tieto Corporation Agile Saturday Source: http://www.microtool.de/instep/en/scrum.asp
  8. 8. 2010-11-138 © 2010 Tieto Corporation Agile Saturday What does the Product Owner do? (1) 1. Creates and MAINTAINS the Product Backlog. 2. Prioritizes the Backlog according to business value or ROI. 3. Assists with the elaboration of Epics, Themes and Features into user stories that are granular enough to be achieved in a single sprint. 4. Conveys the Vision and Goals at the beginning of every Release and Sprint. 5. Represents the customer, interfaces and engages the customer. …(continues)
  9. 9. 2010-11-139 © 2010 Tieto Corporation Agile Saturday What does the Product Owner do? (2) 6. Participates in the Scrum meetings (daily Scrum, Sprint Planning, Review and Retrospective). 7. Inspects the product progress at the end of every Sprint and has complete authority to accept or reject work done. 8. Can change the course of the project at the end of every Sprint. 9. Communicates status externally. 10. Terminates a Sprint if it is determined that a drastic change in direction is required. See also: http://agile.dzone.com/articles/product-owner-top-10
  10. 10. 2010-11-1310 © 2010 Tieto Corporation Agile Saturday Preparation phase (1) Envision the product Goal: create common vision of the product Means: • High level description in customer language (realistic dream) • Prototype (visualizes the dream) • High level Product Backlog Verify with customer (yes, that’s what we want) Verify with technical people (yes, it’s reasonable)
  11. 11. ©2010TietoCorporation Demo 1 Prototype and vision document
  12. 12. 2010-11-1312 © 2010 Tieto Corporation Agile Saturday Preparation phase (2) Elaborate Product Backlog Goal: prioritized and estimated Product Backlog Means: • User Stories (high level, epics) • Vision document • MindMap
  13. 13. ©2010TietoCorporation Demo 2 Product backlog and mindmap
  14. 14. 2010-11-1314 © 2010 Tieto Corporation Agile Saturday Preparation phase (2) Elaborate Product Backlog Goal: prioritized and estimated Product Backlog Means: • User Stories (high level, epics) • Vision document • MindMap
  15. 15. 2010-11-1315 © 2010 Tieto Corporation Agile Saturday Preparation phase (3) Elaborate Product Backlog (reviewed) Goal: prioritized and estimated Product Backlog Goal: deepen the shared vision via intense communication Goal: strengthen commitment Means: • Get priorities from the customer • Get estimates from the team • User Stories (high level, epics) • Vision document • MindMap • Prototype
  16. 16. 2010-11-1316 © 2010 Tieto Corporation Agile Saturday Sprint planning meeting • Help to compose sprint backlog • Set sprint goals, also refresh shared vision • Explain stories to team • Show scenarios on prototype • Ask team to review estimates • Negotiate Sprint Backlog with the team • Publish User Stories to ScrumBoard
  17. 17. ©2010TietoCorporation Demo 3 User Story card
  18. 18. 2010-11-1318 © 2010 Tieto Corporation Agile Saturday ScrumBoard sample
  19. 19. 2010-11-1319 © 2010 Tieto Corporation Agile Saturday During sprint • BE AVAILABLE for questions and discussion • Review User Stories • Review test stories • Participate in daily standup meetings • Offer help as needed to achieve sprint goals • Elaborate User Stories and prototype for next sprint • Review and discuss test results (bug/feature?)
  20. 20. 2010-11-1320 © 2010 Tieto Corporation Agile Saturday Sprint Review and Retrospective meeting • Introduce user stories • Ask to demonstrate each Story • Review test results • Accept stories, thank the team • Update Product Backlog, Product Burndown chart • Commit to Retrospective to help the team in getting better • Make progress visible to team, customer, management • Encourage customer and users to give a try and give feedback
  21. 21. ©2010TietoCorporation Demo 4 Product burndown and mindmap
  22. 22. 2010-11-1322 © 2010 Tieto Corporation Agile Saturday Waterfall + Scrum? Fixed price + Fixed functionality + Fixed schedule ________________________________ Typical state procurement (riigihange)
  23. 23. 2010-11-1323 © 2010 Tieto Corporation Agile Saturday Waterfall + Scrum? Fixed price + Fixed functionality + Fixed schedule ________________________________ Typical state procurement (riigihange) Can we Scrum? Yes! Should we Scrum? Well, depends….
  24. 24. 2010-11-1324 © 2010 Tieto Corporation Agile Saturday Waterfall + Scrum? • You can use Secret Scrum • gain some advantages of the iterative development process • Software business is not about technology but about effective communication in all levels. • Win the trust of the customer. • Find out what the customer really needs. Work hard towards a shared vision. • Chances are that “fixed” functionality is reviewed.
  25. 25. 2010-11-1325 © 2010 Tieto Corporation Agile Saturday Conclusion Good Product Owner: • Builds up the product vision • Actively communicates the vision! • Is available to the team. • Makes development process controllable by making it transparent to the customer • Actively collects customer feedback and reacts timely
  26. 26. ©2010TietoCorporation Thank you! Questions and answers… Kaimar Seljamäe Software analyst Tieto, kaimar.seljamae@tieto.com

×