1 / 24

ICE-BREAKER

ICE-BREAKER. Take a sheet from the while note-pad on your table and do the following: Write the following at the top: Your profile name on meetup Your first and last name. Draw an illustration the following . If you are familiar to the product owner role, your feelings about that role.

lail
Télécharger la présentation

ICE-BREAKER

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ICE-BREAKER • Take a sheet from the while note-pad on your table and do the following: • Write the following at the top: • Your profile name on meetup • Your first and last name. • Draw an illustration the following. • If you are familiar to the product owner role, your feelings about that role. • If you are not familiar to that role, your feeling about Agile in general. 1 Footnote SOURCE: Source

  2. Scrum An Introduction – Specific lens on product owner. For New York XP & Agile Programmer’s Meetup. Date: 23-JUL-2009 • Nirmal Merchant • email: nirmal.merchant@gmail.com • phone: +1(201)918-3197

  3. AGENDA • Scrum at Jet speed • Meet the Product Owner • Exercises • Product Owner Challenges

  4. Traditional vs. Scrum Projects • Traditional Projects: • fixed scope* • fixed time* • fixed budget* • Agile Projects: • time boxed • fixed budget • varying scope

  5. Why Scrum?

  6. Introduction to Scrum: Producing a Working Software. Continuously delivering value.

  7. Product Backlog: A Collection of Stories Stories are prioritized in the order of diminishing business value

  8. Story: The Requirement. A good story follows the INVEST thumb rule. • Story# 001 Priority Points • As Adam, I want to be able to read posts from my subscribed feeds on my mobile phone so that I can read them while I am travelling. • Acceptance Criteria • Given that I am a subscriber to a feed and that I am equipped with a portable device able to access the internet while I am on the move, when I choose to synchronize my subscriptions, then new posts from the feeds are downloaded on my device. • Given that I am a subscriber to a feed and have synchronized my subscriptions on my mobile, when I am in an area where I have no network coverage, then I should still be able to read the posts that I have subscribed to. • Success: • * Display the number of unread posts for each subscribed feed. • Exceptions: • * If no network coverage “Cannot connect to the internet.” • * If cannot find feed “Error in synchronizing feed” • Development Tasks: • * Create an XML file using RSS2.0 standard. • * Update XML file when posts are added / modified / removed. • * Update XML file when comments are added / modified / removed • * Publish the URL to the XML file on the blog.

  9. Estimating Effort: Working with Relative Effort

  10. Release Planning: Sequencing the Execution of Stories. Deliver high risk high value items first. • Sprint 1

  11. Reporting Progress: Keeping the Customer in the Driver’s Seat. • Keeping the end in sight… Managing risks early on…

  12. AGENDA • Scrum at Jet speed • Meet the Product Owner • Exercises • Product Owner Challenges

  13. Who is a Product Owner. • One person who represents all business & customer interests to the team & is responsible for the profitability of the product • - Ken Schwaber • & Jeff Sutherland

  14. Making the Business Case • Maximizing Profitability of the Product • Does it makes solid financial sense to fund your projects over others? • What is your ROI? • Who has the time to perform the extensive research and analysis of data that are required to determine ROI? 1 Footnote SOURCE: Source

  15. Defining the Projects • Maximizing Profitability of the Product

  16. Actively Managing a Product Backlog • Maximizing Profitability of the Product 1 Footnote SOURCE: Source

  17. AGENDA • Scrum at Jet speed • Meet the Product Owner • Exercises • Product Owner Challenges

  18. Exercise: Objectives, Outputs and Outcomes • Goal: • Identify the key drivers for the requirement. • Define the intended outcomes and free ourselves of the outputs communicated. • What’s communicated: • I want to lose weight • I want to be change my job • I want to volunteer for a non-profit • I want the iPhone 3Gs 1 Footnote SOURCE: Source

  19. Exercise: Prioritizing Stories • Feature Bidding Method: • Irrespective of the effort required in building a feature, find out from the stakeholders how much would they be willing to spend from a fixed budget on a specific feature, relative to the others, such that no two features have the same bid. • Three Bucket Iterative Method: • With each iteration, ask the sponsors to divide the list of story cards in three buckets of priority – High, Medium, Low. Repeat this process till the time you have only one card in the high, medium and low buckets. With every sprint repeat this method with the most recent stack. • The Deck of Cards Method: • Print all the stories on index cards and arrange them in an order such that the one at the top is the most important and the one at the bottom is the least important. 1 Footnote SOURCE: Source

  20. AGENDA • Scrum at Jet speed • Meet the Product Owner • Exercise and Demo • Product Owner Challenges

  21. Product Owner Challenges • Who is the product owner? 1 Footnote SOURCE: Source

  22. Individual or Team Effort? • Individual or Team? • If Individual, what should be their allocation? • If Team, who should be in the team? • What should be each team member’s allocation? 1 Footnote SOURCE: Source

  23. Staying Ahead of the Team • How should a product owner plan their work to stay ahead of the team? 1 Footnote SOURCE: Source

  24. Suggested Resources • Websites: • Agile Manifesto http://agilemanifesto.org/ • Agile Alliance http://www.agilealliance.org/ • All About Agile http://www.agile-software-development.com/ • Agile Sofware Development http://agilesoftwaredevelopment.com/ • Blogs • Agile Chronicles http://blog.versionone.net/blog/2009/03/the-product-owner-team.html • Xebia http://blog.xebia.com/2008/05/22/scrum-the-mythical-product-owner-role/ • Ken Schwaber http://www.controlchaos.com/ • Mike Cohn http://blog.mountaingoatsoftware.com/ • Jeff Sutherland http://jeffsutherland.com/scrum/ • Scott Ambler http://www.ambysoft.com/scottAmbler.html • http://www.martinbauer.com/articles/how_to_plan_a_cms_project/objectives_outputs_and_outcomes • Books • The Art of Agile Development by James Shore and Shane Warden • User Stories Applied: For Agile Software Development by Mike Cohn • Agile Software Development with Scrum by Ken Schwaber and Mike Beedle • Agile Estimating and Planning (Robert C. Martin Series) by Mike Cohn • Networks/Groups • Agile Project Leadership Network http://www.aplnnyc.org/ • The New York XP and Agile Meetup Group http://xp.meetup.com/26/t/wm1_gn

More Related