Intro agile for PO's
- 1. AGILE & SCRUM Like us: Visit: Follow me: Tweet: CONSTANT HIGHER MORE LEARNING QUALITY FUN Day 1 www.facebook.com/PracticalAgile www.practical-agile.com @Linkedin @PracticalAgile1
- 2. Anat Alon
- 3. 1. Detailed long term Planning 2. Collect and defined all requirements in advance 3. Worked on multiple releases 4. Good enough development 5. Full of Blame
- 6. Round 1
- 8. Round 2
- 10. WHAT IS AGILE?
- 11. SCRUM PROCESS OVERVIEW 3 Roles: Product owner Scrum Master Team 4 Ceremonies : Sprint Planning Daily Sprint review Retrospective 3 Artifacts: Product Backlog Sprint Backlog Burndown Charts
- 12. PRODUCT OWNER (PO) • Responsible for maximize ROI How? • Defines the features of the product • Defines success criteria for release • Prioritizes feature according to MVP • Give feedback
- 13. How? • Share the vision: Engage the development teams in creating value for your customers • Identify the problem: Talk directly and frequently with your customers • Identify the risk: Talk directly and frequently with your development teams • Validate your vision & plan
- 14. Agile Principle 1-4 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software 2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage 3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to a shorter timescale 4. Business people and developers must work together daily throughout the project
- 15. Agile Principle 5-8 5. Build project around motivated individuals. Give them the environment and support they need, and trust them to get the job done 6. The most efficient and effective method of conveying information to and within development team is face-to-face conversation 7. Working software is the primary measure for progress 8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely
- 16. Agile Principle 9-12 9. Continuous attention to technical excellence and good design enhances agility
- 17. LOW QUALITY TECHNICAL DEBT Time Work left 20 10 12 14 16 18
- 18. Agile Principle 9-12 9. Continuous attention to technical excellence and good design enhances agility 10.Simplicity – the art of maximizing the amount of work not done – is essential 11.The best architectures, requirements, and designs emerge from self-organizing teams 12.At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly
- 19. WHAT WE KNOW Product development process can be defined as a predictable and repeatable process WHAT WE THOUGHT
- 21. WHAT WE THOUGHT WHAT WE KNOW Product development is an evolving and adaptive process
- 22. Traditionally throws content “over the fence”
- 23. The PO takes an active role throughout the development lifespan Traditionally throws content “over the fence” NO MORE! CONCEPT CHANGE
- 24. ARTIFACT I: THE PRODUCT BACKLOG
- 25. Product Backlog 1. Clear 2. Ranked 3. Optimize the value 4. Visible transparent 5. Ensure understanding
- 27. SIZING REQUIREMENTS HOW MANY ITEMS FIT IN THIS JAR?
- 28. As a {persona/user} I would like to {do something} so that {achieve something} In order to {achieve something} as a {persona/user} I would like to {do something} User Stories
- 30. Product Backlog Refinement = Grooming The team and the PO together review the backlog in order to make it ready for the next 2-3 sprints How? Grooming = Clarifying, Estimating, and Splitting Recommended to allocate ~5% of the sprint time
- 31. The terms and conditions to be met in order to accept a requirement as Done ACCEPTANCE CRITERIA
- 32. GIVEN a pre-condition WHEN an action happens THEN an expected result occurs Helps the team visualize what will it look like when it gets Done
- 33. •GIVEN login dialog WHEN user enters username=“Mickey” AND password=“Mouse” THEN user succeeds to login
- 34. •GIVEN login dialog WHEN user enters username=“Mickey” AND password=“Mouse” THEN user succeeds to login •GIVEN login dialog WHEN user enters username=“Mickey” AND password=“TheMouse” THEN user fails to login
- 35. •GIVEN login dialog WHEN user enters username=“Mickey” AND password=“Mouse” THEN user succeeds to login •GIVEN login dialog WHEN user enters username=“Mickey” AND password=“TheMouse” THEN user fails to login •GIVEN login dialog AND login_type=“secure” WHEN username=“Mickey” AND password=“Wrong” WHEN submit WHEN submit THEN user is blocked
- 36. TEXT • Validate business assumption • Validate effort (risk and time)
- 37. Parking lot
- 38. “THE VALUE OF AN IDEA LIES IN THE USING OF IT” Thomas Edison