Sprints: Planning, organizing, running and measuring

Introduction

• Payment Compass was an example of where there was buy in from the Tech team and Business Side for Agile Scrum and ITS-PRO at the beginning of the Project. Pair that with a team that really wanted see a viable solution released within a 5 month timeframe, Agile Scrum principles and practice helped team get where it wanted to go. Team got the hang of it so Scrum Master responsibilities were assumed by the Product Owner starting after the 1.0 Release and PM support was no longer needed.    

   

• If you look at the Payee Sprint 1 (Warm Up), you will see 12 tasks were complete and 19 items were incomplete https://its-pro.ucsd.edu/secure/RapidBoard.jspa?rapidView=10982&projectKey=PP&view=reporting&chart=sprintRetrospective&sprint=26    

   

• If you look at Payee Sprint 2, you will see 48 tasks were complete and 10 issues were incomplete https://its-pro.ucsd.edu/secure/RapidBoard.jspa?rapidView=10982&projectKey=PP&view=reporting&chart=sprintRetrospective&sprint=29    

   

• If you look at Payee Sprint 3, you will see 44 tasks were complete and 3 issues were incomplete https://its-pro.ucsd.edu/secure/RapidBoard.jspa?rapidView=10982&projectKey=PP&view=reporting&chart=sprintRetrospective&sprint=33 

   

• Idea of Sprint Planning versus Reality 

  Brad Williams | Williams Family on Instagram: "Rookie move. Don’t use parchment if you plan on broiling. 🤣🤣#cookingfail #instagramvsreality"  

   

• Q&A with TritonGPT https://tritongpt.ucsd.edu/chat/shared/749d4b91-6262-4f01-aba2-efeb444dccf2

  • Value of Sprint Planning for Project Management 

  • Sprint Planning Pitfalls

  • Tools that support Sprint Planning

  • Prerequisites for Sprint Planning

  • Atlassian Training Material

     

     

Sprint Mechanics

• Meeting Frequency

  • It Depends

    • Option 1

      • Typical Sprint Planning every other week followed by Sprint Review every other week as well

        • Best Case Scenario per sprint

          • 1 hour Sprint planning

          • 1 hour Sprint review

          • 30 minutes backlog grooming

    • Option 2

      • Carve out 15-30 minutes end of existing weekly meetings to add tasks to sprints and close out sprints

      • setup 30 backlog grooming meeting every 2 weeks

• Board Creation 

  • Scrum Board

  • Board Settings

    • Estimation - Change from Story Points to Original Time Estimate

    • Issue Detail - Add Start Date and Due Dates

• Sprint for single project 

• Sprint for multiple projects 

• Starting a second sprint (deferred)

• Closing Sprint (deferred)