APN Auckland Event 9 - Scrum 101, Unleashing the Theory

1,232 views

Published on

The core of the practice of Agile is the delivery of individual projects; it's where most practitioners start out, and it fundamentally changes the way a project team works together and works with their stakeholders.
Scrum is one of the most popular Agile delivery approaches at the moment. In this APN session, Carolyn uses one of her recent projects as a way to illustrate each facet of Scrum and how it panned out in real life, from start to finish.

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,232
On SlideShare
0
From Embeds
0
Number of Embeds
98
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Thank you Kevin.
  • APN Auckland Event 9 - Scrum 101, Unleashing the Theory

    1. 1. Carolyn Sanders - Fronde Scrum 101 – Unleashing the theory
    2. 2. Fronde – our sponsor <ul><li>Began as Synergy in Wellington, 1992. Renamed Fronde in 2006 </li></ul><ul><li>Early adopter: using Agile project management and development in early 2000s... before it was hip </li></ul><ul><li>Exclusive partner with Rob Thomsett </li></ul><ul><li>Co-founders of Agile Professionals Network in New Zealand (with ASB) </li></ul>Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    3. 3. Today – Scrum 101 <ul><li>A little bit about where it came from </li></ul><ul><li>A lot about how Scrum works </li></ul><ul><li>Some examples from an actual project </li></ul><ul><li>What it’s useful for, and what it doesn’t fix </li></ul><ul><li>How to get started if you want to try it out </li></ul>Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    4. 4. 1. Agile Manifesto <ul><li>We have come to value: </li></ul><ul><li>Individuals and interactions over processes and tools </li></ul><ul><li>Working software over comprehensive documentation </li></ul><ul><li>Customer collaboration over contract negotiation </li></ul><ul><li>Responding to change over following a plan </li></ul><ul><li>That is, while there is value in the items on </li></ul><ul><li>the right, we value the items on the left more . </li></ul>Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    5. 5. Agile Values <ul><li>Openness: the project is for the stakeholders </li></ul><ul><li>Honesty: in estimating and planning </li></ul><ul><li>Courage: to face the consequences </li></ul><ul><li>Trust: in those individuals and their estimates </li></ul><ul><li>Money: because projects aren’t free </li></ul><ul><li>Commitment: to deliver on our promises </li></ul>Credits: First five from Rob Thomsett, last from Jeff Sutherland Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    6. 6. Agile Landscape Agile Architecture and Governance Agile Manifesto and Values Agile Project Management Agile Delivery Agile Programming Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    7. 7. Where Scrum started and who started it <ul><li>Software Development truths: </li></ul><ul><ul><li>Can’t write down all the requirements up front </li></ul></ul><ul><ul><li>Impossible to estimate debug/test time at the end </li></ul></ul><ul><li>Agile Delivery: small cross-functional teams, delivering frequently and incrementally to the customers </li></ul><ul><li>Scrum: Dr Jeff Sutherland and Ken Schwaber, on real projects </li></ul><ul><li>And: Gabrielle Benefield and Pete Deemer, and… </li></ul>Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    8. 8. 2. Scrum on one page © Pete Deemer and Gabrielle Benefield, The Scrum Primer Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    9. 9. 3. The example project <ul><li>Project H: building an Intranet in MOSS </li></ul><ul><ul><li>For a client, with their experts </li></ul></ul><ul><ul><li>Three MOSS experts, a tester and a BA </li></ul></ul><ul><ul><li>Very constrained budget and deadline </li></ul></ul><ul><ul><li>Willing to trade off scope to get quality </li></ul></ul>Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    10. 10. “ Individuals and Interactions” – Scrum Roles Product Owner: get all the input, prioritise the outputs* Team: build the output. Self Managing* Scrum Master: get the process going well Stakeholders: have their say and do their bit Project Manager?* Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    11. 11. Individuals and Interactions again Co locate the team. CO LOCATE THE TEAM I REALLY MEAN IT WORK TOGETHER IN A ROOM Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    12. 12. Our team room Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    13. 13. “ Customer Collaboration” - the Product Backlog - the theory <ul><li>All the stuff we could do: </li></ul><ul><li>Features </li></ul><ul><li>User Stories </li></ul><ul><li>Known Bugs </li></ul><ul><li>Explorations </li></ul>The Vision <ul><li>The Product Backlog </li></ul><ul><li>Specific items </li></ul><ul><li>Prioritised </li></ul><ul><li>Business value assigned </li></ul><ul><li>Effort estimated by team </li></ul>Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    14. 14. The Product Backlog – how we did it* Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    15. 15. The Product Backlog – estimation with Planning Poker The Fibonacci series: 1, 1, 2, 3, 5, 8, 11, 19, 30, 49… Planning Poker cards: 0, ½, 1, 2, 3, 5, 8, 13, 25, 40, 100, ?, coffee James Grenning & Mike Cohn Let’s try it. Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    16. 16. Sprint Planning – the theory Product Backlog items prioritised estimated How many hours the team can work in this Sprint, times “focus factor”* <ul><li>Sprint Planning </li></ul><ul><li>- Break down the Backlog items into tasks </li></ul><ul><li>Agree on tasks </li></ul><ul><li>Estimate tasks </li></ul><ul><li>Commit to the outputs </li></ul><ul><li>Sprint Backlog </li></ul><ul><li>Estimated </li></ul><ul><li>Committed to </li></ul><ul><li>Sequenced </li></ul>Do the Sprint Potentially deployable output: working software Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    17. 17. Sprint Planning – “Working Software” means what, exactly? Defining “Done” – hanselminutes.com Podcast 119 Quality Support Documentation Content Testing Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    18. 18. Sprint Planning – what we did Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    19. 19. Sprint Planning again – what else we did Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    20. 20. “ Responding to Change” in the Daily Scrum – the theory <ul><li>What I did yesterday </li></ul><ul><li>What I plan to do today </li></ul><ul><li>What’s holding me up </li></ul>Rules Same time every day for 15 minutes No discussions during the Scrum Update the Sprint Backlog: hours’ effort remaining Update the Burndown © Pete Deemer and Gabrielle Benefield, The Scrum Primer Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    21. 21. Daily Scrum – what we did Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    22. 22. Daily Scrum – what we did (the task wall) Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    23. 23. Daily Scrum – what else we did Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    24. 24. Behind the Daily Scrum – what else we did Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    25. 25. “ Responding to Change”: Sprint Review / Demo – theory and practice <ul><li>A little “Ta Da!” moment </li></ul><ul><li>Not a presentation , a demonstration </li></ul>Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    26. 26. Retrospective – theory and practice <ul><li>Look Back </li></ul><ul><li>Plus / Minus / Interesting </li></ul><ul><li>Do Again / Do Differently </li></ul><ul><li>Dot prioritisation </li></ul><ul><li>Caused by / Exposed By </li></ul><ul><li>Look Forward, Adjust Course </li></ul><ul><li>Actions Arising </li></ul><ul><li>Measuring Velocity: focus factor </li></ul><ul><li>Product Backlog re-estimate </li></ul>Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    27. 27. Notes from our last retrospective + Co location, co location, co location -- Sitting in a line in the room + Kashin -- Home Page churn -- retesting and retesting + giving the product a name -- Sprint length – too short, too long interesting: defining how to define reqts Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    28. 28. Release Planning – theory and practice Sprint 1 Sprint 2 Sprint 4 Sprint 3 Sprint 5 Release 1 Release 2 Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    29. 29. I said I’d come back to…. <ul><li>Just one product owner? </li></ul><ul><li>Sprint 0 and Sprint N </li></ul><ul><li>Sprint length </li></ul><ul><li>Velocity / Focus Factor </li></ul><ul><li>The self-managing, cross-functional, team* </li></ul><ul><li>The role of the project manager* </li></ul><ul><li>How to build a product backlog from a Vision* </li></ul>Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    30. 30. The cross-functional team? <ul><li>Individual burndowns </li></ul>Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    31. 31. What the PM does © Rob Thomsett, Agile Project Management Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited Agile Project Management Stakeholders Related Projects Risks Returns Costs Schedules Priorities Resources Assumptions Policies Scope Priorities Quality Strategy Risk Time-boxed Delivery Just in Time Architecture User Stories Group Estimation Continuous Feedback Solution Design & Build Release Planning Documentation Regular Deployment Agile Project Delivery
    32. 32. Building a Product Backlog – Agile PM <ul><li>Stakeholders and impact on them </li></ul><ul><li>Success Criteria </li></ul><ul><li>Outcomes and Benefits </li></ul><ul><li>Scope </li></ul><ul><li>Stakeholder Stories </li></ul><ul><li>Quality </li></ul><ul><li>Risk Profile and Risks </li></ul><ul><li>Project Approach and Release Strategy </li></ul>© Rob Thomsett, Agile Project Management Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    33. 33. 4. Scrum can fix…. <ul><li>“ I know we’re only two weeks from go-live, but we can’t integrate the modules….” </li></ul><ul><li>“ Well it works on the developer’s PC” </li></ul><ul><li>“ Ta da!” “Oh, no….” </li></ul><ul><li>“ Requirements v15.1.3 page 63 has a typo” </li></ul><ul><li>“ What do you mean, usability? I can read it just fine” </li></ul>Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    34. 34. Scrum might expose … <ul><li>“ How long is a piece of string?” </li></ul><ul><li>“ I’m not sure what I want, but tell me when you’re done” </li></ul><ul><li>“ There’s a bug in the server operating system patch database congrosinator v0.3.4” </li></ul><ul><li>“ This is top priority”, “No, this is!” </li></ul><ul><li>“ My code doesn’t need testing, I am a god” </li></ul><ul><li>“ But the Scrum methodology doesn’t say to write down the requirements…” </li></ul>Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    35. 35. 5. How to get started <ul><li>Just like learning to drive </li></ul><ul><li>Pick an appropriate project </li></ul><ul><li>Get training – The Scrum Alliance can help </li></ul><ul><li>Get a coach </li></ul><ul><li>www.scrumalliance.org </li></ul><ul><li>scrumtraininginstitute.com/library </li></ul><ul><li>Learn, apply, then adjust </li></ul>Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    36. 36. Training & Certification <ul><li>Certified Scrum Master </li></ul><ul><li>Certified Product Owner </li></ul><ul><li>Certified Scrum Practitioner </li></ul><ul><li>Certified Scrum Trainer </li></ul><ul><li>Certified Scrum Coach </li></ul>Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited
    37. 37. Q&A <ul><li>Carolyn Sanders </li></ul><ul><li>Principal Consultant – Agile and PM </li></ul><ul><li>www.fronde.com </li></ul>Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited

    ×