Sprint Execution - Stand-up, Taskboard etc


Published on

This presentation is about how you could leverage values, principles and practices of Scrum to make your iterations/ building of your product successful.

Published in: Technology, Business
  • Be the first to comment

Sprint Execution - Stand-up, Taskboard etc

  1. 1. SPRINT EXECUTION Bachan Anand [email_address] http://agile.conscires.com/ Slides prepared by Indu Menon, Neeta Singh and Vanessa Brown
  2. 2. Agenda <ul><li>Overview of Agile and Scrum </li></ul><ul><li>Scrum Overview </li></ul><ul><li>Sprint Execution </li></ul><ul><li>Q&A </li></ul>Please dial in to (218) 895-4640 PIN: 3289145 http://agile.conscires.com/
  3. 3. Overview of Agile and Scrum Please dial in to (218) 895-4640 PIN: 3289145 http://agile.conscires.com/
  4. 4. Overview of Agile and Scrum Agile Manifesto <ul><li>Agile is a set of values: </li></ul><ul><ul><li>Individuals and interactions over processes and tools </li></ul></ul><ul><ul><li>Working software (Products) over comprehensive documentation </li></ul></ul><ul><ul><li>Customer collaboration over contract negotiation </li></ul></ul><ul><ul><li>Responding to change over following a plan </li></ul></ul>Please dial in to (218) 895-4640 PIN: 3289145 http://agile.conscires.com/
  5. 5. Overview of Agile and Scrum What is Scrum <ul><li>Scrum is an Agile framework that supports lightweight processes that emphasize: </li></ul><ul><ul><li>Incremental deliveries </li></ul></ul><ul><ul><li>Quality of Product </li></ul></ul><ul><ul><li>Continuous improvement </li></ul></ul><ul><ul><li>Discovery of people’s potential </li></ul></ul><ul><li>Scrum is simple to understand, but requires discipline in order to be successful </li></ul><ul><li>Scrum is not a methodology </li></ul>http://agile.conscires.com/
  6. 6. Overview of Agile and Scrum Foundations of Scrum <ul><li>Empiricism </li></ul><ul><ul><li>Detailed up-front planning and defined processes are replaced by just-in-time Inspect and Adapt cycles </li></ul></ul><ul><li>Self-Organization </li></ul><ul><ul><li>Small teams manage their own workload and organize themselves around clear goals and constraints </li></ul></ul><ul><li>Prioritization </li></ul><ul><ul><li>Do the next right thing </li></ul></ul><ul><li>Rhythm </li></ul><ul><ul><li>Allows teams to avoid daily noise and focus on delivery </li></ul></ul><ul><li>Collaboration </li></ul><ul><ul><li>Leaders and customers work with the Team, rather than directing them </li></ul></ul>http://agile.conscires.com/
  7. 7. <ul><li>Transparency </li></ul><ul><ul><li>Everything about a project is visible to everyone </li></ul></ul><ul><li>Commitment </li></ul><ul><ul><li>Be willing to commit to a goal </li></ul></ul><ul><li>Courage </li></ul><ul><ul><li>Have the courage to commit, to act, to be open and to expect respect </li></ul></ul><ul><li>Focus </li></ul><ul><ul><li>Focus all of your efforts and skills on doing the work that you have committed to doing </li></ul></ul><ul><li>Respect </li></ul><ul><ul><li>Respect and trust the different people who comprise a team </li></ul></ul>http://agile.conscires.com/
  8. 8. Scrum Overview
  9. 9. Scrum Overview Sprint Cycle
  10. 10. Scrum Overview Role: Product Owner <ul><li>Thought Leader and Visionary </li></ul><ul><li>Drives the Product Vision (for example, </li></ul><ul><li>with Story Mapping) </li></ul><ul><li>Prioritizes the Goals - User Stories </li></ul><ul><li>Maintains the Product Backlog with the team </li></ul><ul><li>Accepts the Working Product (on behalf of the customer) </li></ul>http://agile.conscires.com/
  11. 11. Scrum Overview Role: ScrumMaster <ul><li>Servant Leader </li></ul><ul><li>Facilitates the Process </li></ul><ul><li>Supports the Team </li></ul><ul><li>Removes Organizational Impediments </li></ul><ul><li>Socializes Scrum to Management </li></ul><ul><li>Enable close collaboration across all roles and functions </li></ul>http://agile.conscires.com/
  12. 12. Scrum Overview Role: Team <ul><li>Cross-Functional </li></ul><ul><li>4-8 Members </li></ul><ul><li>Self-Organizing </li></ul><ul><li>Focused on Commitments </li></ul>http://agile.conscires.com/
  13. 13. Sprint Execution
  14. 14. Sprints <ul><li>Basic unit of development in the Scrum development methodology </li></ul><ul><li>Scrum projects make progress in a series of “sprints” </li></ul><ul><li>last between one week and one month </li></ul>http://agile.conscires.com/
  15. 15. Sprints Continued <ul><li>Are a &quot;time-boxed&quot; (i.e. restricted to a specific duration) effort of a constant length. </li></ul><ul><li>A constant duration leads to a better rhythm </li></ul><ul><li>Product is designed, coded, and tested during the sprint </li></ul>http://agile.conscires.com/
  16. 16. Timeboxing …why? <ul><li>helps the team and organization in focusing on clear goals. </li></ul><ul><li>to cause movement and to set an expectation that we will limit the time and energy spent in any one direction </li></ul><ul><li>guide line in how we break work down into tasks or execution. </li></ul><ul><li>to avoid gold platting or excessive polishing of an item or thing. </li></ul>http://agile.conscires.com/
  17. 17. Plan your sprint <ul><li>Sprint Planning Workshop </li></ul><ul><li>Decide Your Sprint Duration </li></ul><ul><li>Keep Sprint Duration Consistent </li></ul><ul><li>Select Target Backlog for Sprint </li></ul><ul><li>Clarify Sprint Requirements </li></ul>http://agile.conscires.com/
  18. 18. Sprint Planning <ul><li>Team selects items from the product backlog they can commit to completing </li></ul><ul><li>Sprint backlog is created </li></ul><ul><ul><li>Tasks are identified and each is estimated (1-16 hours) </li></ul></ul><ul><ul><li>Collaboratively, not done alone by the ScrumMaster </li></ul></ul><ul><li>High-level design is considered </li></ul>http://agile.conscires.com/
  19. 19. Sprint planning meeting Business conditions Team capacity Product backlog Technology Current product http://agile.conscires.com/ Sprint prioritization <ul><li>Analyze and evaluate product backlog </li></ul><ul><li>Select sprint goal </li></ul>Sprint planning <ul><li>Decide how to achieve sprint goal (design) </li></ul><ul><li>Create sprint backlog (tasks) from product backlog items (user stories / features) </li></ul><ul><li>Estimate sprint backlog in hours </li></ul>
  20. 20. The Sprint Goal <ul><li>A short statement on what the work will be </li></ul><ul><li>focused on during the sprint </li></ul>http://agile.conscires.com/
  21. 21. A sprint backlog <ul><li>Commit to the Sprint Backlog </li></ul><ul><li>Pull out next priority item from Product Backlog </li></ul><ul><li>Once work in a Sprint Backlog is completed , pull work from Product Backlog </li></ul>http://agile.conscires.com/
  22. 22. Managing the Sprint Backlog <ul><li>Individuals sign up for work of their own choosing </li></ul><ul><ul><li>Work is never assigned </li></ul></ul><ul><li>Estimated work remaining is updated daily </li></ul><ul><li>Any team member can add, delete or change the sprint backlog </li></ul><ul><li>Work for the sprint emerges </li></ul><ul><li>If work is unclear, define a sprint backlog item with a larger amount of time and break it down later </li></ul><ul><li>Update work remaining as more becomes known </li></ul>http://agile.conscires.com/
  23. 23. No changes during a sprint <ul><li>Plan sprint durations around how long you can commit to keeping change out of the sprint </li></ul><ul><li>Change </li></ul>http://agile.conscires.com/
  24. 24. Daily Stand-up meeting <ul><li>Also referred to as the morning rollcall or the daily scrum . </li></ul><ul><li>Meeting is usually held at the same time and place every working day </li></ul><ul><li>Crucial features is that the meeting is intended to be a status update to other team members and not a status update to the management or other stakeholders </li></ul><ul><li>Each member talks about their progress since the last stand-up, the anticipated work until the next stand-up and any impediments they foresee. </li></ul>http://agile.conscires.com/
  25. 25. Daily Stand-up (Cont.) <ul><li>Parameters </li></ul><ul><ul><li>Daily </li></ul></ul><ul><ul><li>15-minutes </li></ul></ul><ul><ul><li>Stand-up </li></ul></ul><ul><li>Not for problem solving </li></ul><ul><ul><li>Whole world is invited </li></ul></ul><ul><ul><li>Only team members, ScrumMaster, product owner, can talk </li></ul></ul><ul><li>Helps avoid other unnecessary meetings </li></ul>http://agile.conscires.com/
  26. 26. Everyone answers 3 questions http://agile.conscires.com/
  27. 27. What is This Meeting For? <ul><li>Tasks </li></ul><ul><ul><li>Synchronize the various team members </li></ul></ul><ul><ul><li>Identify required help and common areas of work </li></ul></ul><ul><li>Impediments </li></ul><ul><ul><li>Raise new impediments </li></ul></ul><ul><ul><li>Pair impediments with people </li></ul></ul><ul><ul><li>Ensure past impediments are being taken care of </li></ul></ul><ul><li>To identify technical issues </li></ul>http://agile.conscires.com/
  28. 28. Come Prepared http://agile.conscires.com/
  29. 29. The Parking Lot <ul><li>Capture items for discussion </li></ul><ul><li>The 15 minute timebox is not the place for long discussion </li></ul><ul><li>Review the parking lot after the daily </li></ul>http://agile.conscires.com/
  30. 30. The Impediments List <ul><li>“ Anything that prevents a team member from performing work as efficiently as possible” - from Victor Szalvay’s article “Glossary of Scrum Terms” </li></ul><ul><li>Rule of thumb : at least one impediment a day </li></ul><ul><li>How do we generate impediments? </li></ul><ul><ul><li>Understand what an impediment is and make sure the team understands as well </li></ul></ul><ul><ul><li>Ask &quot;why are there no impediments today?&quot; </li></ul></ul><ul><ul><li>Hanging notes from the ceiling to entice the team </li></ul></ul><ul><ul><li>If all else fails…beg  </li></ul></ul>http://agile.conscires.com/
  31. 31. Dealing with Impediments http://agile.conscires.com/
  32. 32. Bad Smells of Daily Scrum <ul><li>Storytelling </li></ul><ul><li>Reporting to the SM </li></ul><ul><li>Accounting for time rather then goals </li></ul><ul><li>Invisible (electronic) task board </li></ul><ul><li>Not raising impediments </li></ul><ul><li>Not handling impediments </li></ul><ul><li>Not helping each other </li></ul><ul><li>Low Energy </li></ul><ul><li>Who goes first? </li></ul><ul><li>Cell phones on. Laptops open. People “checked out.” </li></ul>http://agile.conscires.com/
  33. 33. Loss of Rhythm - Symptoms <ul><li>Daily Scrums are skipped or meeting times vary </li></ul><ul><li>Sprint durations are inconsistent or change arbitrarily mid-sprint </li></ul><ul><li>Sprint planning is inconsistent or drifts </li></ul><ul><li>Sprint planning meetings are skipped </li></ul>http://agile.conscires.com/
  34. 34. Promote Rhythm <ul><li>Sustainable pace </li></ul><ul><li>Leads to focus </li></ul><ul><li>Be consistent </li></ul><ul><li>Reference: http://www.scrumalliance.org/articles/34 </li></ul>http://agile.conscires.com/
  35. 35. Collaboration <ul><li>Visit other teams </li></ul><ul><li>Ask other people to join your daily standup </li></ul><ul><li>Use the retrospective to brainstorm </li></ul><ul><li>Identify best practices for working with remote team mates(multiple time zones, cultural differences and tools) </li></ul>http://agile.conscires.com/
  36. 36. Monitor Sprints <ul><li>Burndown and Burn Rate Report </li></ul><ul><li>Taskboard </li></ul><ul><li>Mid-Sprint checkpoint. </li></ul><ul><li>Reference: http://developagile.com/post/760163969/monitoring-a-sprint-in-the-agile-scrum-world </li></ul>http://agile.conscires.com/
  37. 37. A sprint burndown chart http://agile.conscires.com/
  38. 38. Task Board <ul><li>Most important information radiator that an agile team has. </li></ul><ul><li>Illustrates the progress that an agile team is making in achieving their sprint goals. </li></ul><ul><li>Located in an area that is central to the team </li></ul>
  39. 39. Task Board http://agile.conscires.com/
  40. 40. The Sprint Review <ul><li>Team presents what it accomplished during the sprint </li></ul><ul><li>Typically takes the form of a demo of new features or underlying architecture </li></ul><ul><li>Sprint Retrospective </li></ul><ul><li>Informal </li></ul><ul><ul><li>2-hour prep time rule </li></ul></ul><ul><ul><li>No slides </li></ul></ul><ul><li>Whole team participates </li></ul><ul><ul><li>Invite the world </li></ul></ul>http://agile.conscires.com/
  41. 41. How do you learn Scrum – By Doing? <ul><li>Apply few practices at a time </li></ul><ul><li>Understand the values and foundations </li></ul><ul><li>Inspect and Adapt </li></ul><ul><li>Experience the Joy of Doing Scrum </li></ul>http://agile.conscires.com/
  42. 42. How do you learn Scrum ? Experiential Training http://agile.conscires.com/
  43. 43. Pay-it-forward / Donation only trainings <ul><li>1 day Agile & Scrum Training </li></ul><ul><li>Denver/Boulder, CO - July 30 th </li></ul><ul><li>Irvine , CA - August 12 th </li></ul><ul><li>San Francisco, CA -Aug 26 th </li></ul><ul><li>Atlanta, GA - Aug 26 th </li></ul><ul><li>Boston, MA - Sep 30 th </li></ul><ul><li>San Diego , CA – Sep 30 th </li></ul><ul><li>Las Vegas, NV – Oct 7 th </li></ul><ul><li>Seattle, WA - Oct 21 st </li></ul>http://agile.conscires.com/
  44. 44. User groups /Communities <ul><li>ALN – Agile Leadership Network </li></ul><ul><li>Scrum Alliance – Scrum User Groups </li></ul><ul><li>Online User Groups </li></ul><ul><ul><li>Scrum Alliance </li></ul></ul>http://agile.conscires.com/
  45. 45. User groups /Communities <ul><li>APLN – Agile Project Leadership Network </li></ul><ul><li>Scrum Alliance – Scrum User Groups </li></ul><ul><li>Online User Groups </li></ul><ul><ul><li>Scrum Alliance </li></ul></ul>http://agile.conscires.com/
  46. 46. User groups /Communities <ul><li>APLN – Agile Project Leadership Network </li></ul><ul><li>Scrum Alliance – Scrum User Groups </li></ul><ul><li>Online User Groups </li></ul><ul><ul><li>Scrum Alliance </li></ul></ul>http://agile.conscires.com/
  47. 47. Scrum Certifications http://agile.conscires.com/
  48. 48. Q & A http://agile.conscires.com/
  49. 49. Donation only 1 day Trainings <ul><ul><li>Denver – July 30 th </li></ul></ul><ul><ul><ul><li>http://agile.conscires.com/scrum-1-day-training-denver-03/ </li></ul></ul></ul><ul><ul><li>Irvine - August 12 th </li></ul></ul><ul><ul><ul><li>http://agile.conscires.com/1-day-agile-scrum-training-irvine-05/ </li></ul></ul></ul><ul><ul><li>Seattle – October 21 st </li></ul></ul><ul><ul><ul><li>http://agile.conscires.com/agile-scrum-training-seattle-03/ </li></ul></ul></ul><ul><ul><li>San Francisco – Aug 26 th </li></ul></ul><ul><ul><li>Atlanta – Aug 26 th </li></ul></ul><ul><ul><li>San Diego Sep 30 th </li></ul></ul><ul><ul><li>Boston – Sep 30 th </li></ul></ul><ul><ul><ul><li>http://agile.conscires.com/1-day-agile-scrum-training-boston-04/ </li></ul></ul></ul>http://agile.conscires.com/
  50. 50. Thank you ! <ul><li>More Resources at </li></ul><ul><ul><li>http://agile.conscires.com/suggested-reading-list-and-resources/ </li></ul></ul><ul><ul><li>Contact Info </li></ul></ul><ul><ul><ul><li>Bachan Anand </li></ul></ul></ul><ul><ul><ul><li>[email_address] </li></ul></ul></ul><ul><ul><ul><li>949-232-8900 </li></ul></ul></ul><ul><ul><ul><li>http://www.linkedin.com/in/bachan </li></ul></ul></ul>http://agile.conscires.com/