Product owner


Published on

PO role in SCRUM

  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • SVENShorter Time to MarketAlways software to releaseKnow what the customer wants and build it in short timeboxesBe able to flexibly respond to changing demands and market requirements
  • Create a complete product visionBox for the softwareElevator pitchClear strategy, major featuresEveryone knows what the target is
  • Brainstorming for all featuresPersonas to get a user flowCreate complete user flows per personaUse that to help Release Planning
  • Clear longterm targetVision consists of several releasesOnly content of current release is clear
  • Start with the most important Feature/EpicBreak it down to user storiesBreak user Stories down to smaller User StoriesBefore working on User Stories break them down to Tasks
  • Too much to do in generalInstead of that is our release date and those features have to be done by then we work on one feature after another and finish them
  • There is exactly one Priority oneThere is only one priority twoOnce the first ten Priorities are set, the rest isn’t that important anymoreIt’s quite difficult to prioritizeTalking with the team and finding out about critical problems and unknown territory helpsCost of Delay can be a great help
  • LUISWritinga good backlog with good User Stories requires hard workUser Stories should always be framed in the view of a user of the systemUnexperienced Product Owners need help from coaches or trainings
  • Independence means that a story can be developed, tested, and potentially even delivered on its own. Therefore, it can also be independently valued.
  • Luis
  • Product owner

    1. 1. Product OwnerThe Role of a Product Owner in Scrum
    2. 2. Agile in a Nutshell
    3. 3. Vision“I believe that this nationshould commit itself toachieving the goal,before this decade is out, oflanding a man on the moonand returning him safely to theearth.” J.F. Kennedy
    4. 4. Story Board
    5. 5. Product VisionVision (1-2 years) Release Release Release User Story User Story Feature User Story Feature User Story Feature Feature … Feature Feature Feature Feature Feature
    6. 6. Release Planning
    7. 7. Epics, User Stories, Tasks
    8. 8. Product Backlog
    9. 9. Prioritization
    10. 10. The User Story• As a <role>, I can <activity> so that <business value> where:• ‹ ‹ <role> represents who is performing the action or perhaps one who is receiving the value from the activity. It may even be another system, if that is what is initiating the activity.• ‹ ‹ <activity> represents the action to be performed by the system.• ‹ ‹ <business value> represents the value achieved by the activity.
    11. 11. Invest
    12. 12. INVEST or good User Stories Independent Negotiable Valuable Small Estimable Testable
    13. 13. Example• As an administrator, I can set the password expiration period so that users are forced to change their passwords periodically.• As an administrator, I can set the password strength characteristics so that users are required to create difficult-to-hack passwords.
    14. 14. Acceptance Criteria
    15. 15. Example for Acceptance CriteriaAs a consumer, I always see current energy pricing reflectedon my portal and on-premise devices so that I know that myenergy usage costs are accurate and reflect any utility pricingchanges.• Conditions of Satisfaction 1. Verify the current pricing is always used and the calculated numbers are displayed correctly on the portal and other on- premise devices (see attachment for formats). 2. Verify the pricing and the calculated numbers are updated correctly when the price changes. 3. Verify the “current price” field itself is updated according the scheduled time. 4. Verify the info/error messages when there is a fault in the pricing (see approved error messages attached).
    16. 16. Planning
    17. 17. Daily
    18. 18. Grooming
    19. 19. Demo/Review
    20. 20. Collaboration with Scrum Master
    21. 21. Working with the Team
    22. 22. Book Recommendations
    23. 23. Credits• Agile Software Requirements, Addison Wesley Dean Leffingwell Slide 10 User Story Slide 13 + 14 examples for INVEST
    24. 24. Pictures• Agile in a Nutshell• Vision• Story Board• Epics, User Stories, Tasks• Product Backlog• Prioritization• Invest• Acceptance Criteria• Grooming• Planning• Daily• Release Planning• Demo/Review• Collaboration with Scrum Master• Working with the Team
    25. 25. Contact InformationSven Schnee Agile Project Manager Twitter: @MrSnow76 Blog: LinkedIn: Slideshare: Goncalves Agile Project Manager Twitter: @lgoncalves1979 Blog: LinkedIn: Slideshare: Presentation can be found on our Slideshare accounts.
    26. 26. Thank you for your attention!