Downloaded 47 times
More Related Content
Product owner
- 1. Product Owner The Roleof a Product Owner in Scrum
- 2. Agile in aNutshell
- 3. Vision “I believe thatthis nation should commit itself to achieving the goal, before this decade is out, of landing a man on the moon and returning him safely to the earth.” J.F. Kennedy
- 4.
- 5. Product Vision Vision (1-2years) Release Release Release User Story User Story Feature User Story Feature User Story Feature Feature … Feature Feature Feature Feature Feature
- 6.
- 7. Epics, User Stories,Tasks
- 8.
- 9.
- 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.
- 12. INVEST or goodUser Stories Independent Negotiable Valuable Small Estimable Testable
- 13. Example • As anadministrator, 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.
- 15. Example for AcceptanceCriteria As a consumer, I always see current energy pricing reflected on my portal and on-premise devices so that I know that my energy usage costs are accurate and reflect any utility pricing changes. • 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.
- 17.
- 18.
- 19.
- 20. Collaboration with ScrumMaster
- 21. Working with theTeam
- 22.
- 23. Credits • Agile SoftwareRequirements, Addison Wesley Dean Leffingwell Slide 10 User Story Slide 13 + 14 examples for INVEST
- 24. Pictures • Agile in a Nutshell http://c586412.r12.cf2.rackcdn.com/threewalnuts.jpg • Vision http://www.tao-arts.de/wp/wp/wp-content/uploads/2009/07/taoistische-meditation1.jpg • Story Board http://www.solutionsiq.com/Portals/93486/images/recognizing-bottlenecks-in-product-backlog-scrum-agile-software-development.jpg • Epics, User Stories, Tasks http://www.matryoshka-dolls.co.uk/wp-content/uploads/wpsc/product_images/Russian%20Dolls.jpg • Product Backlog http://2.bp.blogspot.com/_81xab5dmFF4/TLHeqg19VdI/AAAAAAAAAGs/lZEHAl6Z-Gc/s1600/too_much_work_too_less.jpg • Prioritization http://www.aquarius-atlanta.com/articles/images/ChooseNow_351x144_4C.jpg • Invest http://ihowtoinvest.com/images/How-to-Invest-Money-3.jpg • Acceptance Criteria http://projectcommunityonline.com/wp-content/uploads/2012/02/bigstock_Inspector_28653311.jpg • Grooming http://3.bp.blogspot.com/-O-sAwr5wP2I/ToRUgQk3NhI/AAAAAAAABK4/soUhXJ9wQwk/s1600/Crystal-ball.jpg • Planning http://files.campus.edublogs.org/blogs.baylor.edu/dist/3/599/files/2011/11/DSC_0277-1y5xiyo.jpg • Daily http://i.imgur.com/Ai5Tf.jpg • Release Planning http://static.tumblr.com/rqcjqni/8I4mc7r89/232.jpg • Demo/Review http://www.elmousa.com/sites/default/files/images/Fotolia_22282220_M_%E8%9C%89%EF%A3%B0%E8%9F%BE%EF%BD%A5.jpg • Collaboration with Scrum Master http://faithoncampus.files.wordpress.com/2009/08/ant_apple.jpg • Working with the Team http://upload.wikimedia.org/wikipedia/commons/thumb/d/dd/Team_Time_Out_Handball.jpg/1263px-Team_Time_Out_Handball.jpg
- 25. Contact Information Sven Schnee Agile Project Manager Twitter: @MrSnow76 Blog: http://MrSnow76.blogspot.com LinkedIn: http://www.linkedin.com/pub/sven-schnee/27/932/5a5 Slideshare: http://www.slideshare.net/MrSnow76 Luis-Miguel Goncalves Agile Project Manager Twitter: @lgoncalves1979 Blog: http://lmsgoncalves.wordpress.com LinkedIn: http://www.linkedin.com/in/luismsg Slideshare: http://www.slideshare.net/lgoncalves1979 This Presentation can be found on our Slideshare accounts.
- 26. Thank you foryour attention!
Editor's Notes
- #3 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
- #4 Create a complete product visionBox for the softwareElevator pitchClear strategy, major featuresEveryone knows what the target is
- #5 Brainstorming for all featuresPersonas to get a user flowCreate complete user flows per personaUse that to help Release Planning
- #6 Clear longterm targetVision consists of several releasesOnly content of current release is clear
- #8 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
- #9 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
- #10 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
- #12 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
- #13 Independence means that a story can be developed, tested, and potentially even delivered on its own. Therefore, it can also be independently valued.
- #19 Luis