Sprint cadence

Using a scrum-based approach during two-week sprints can offer numerous benefits. It enables continuous assessment of planned versus actual completion, ensuring the team stays on track and can make necessary adjustments. Moreover, it allows for evaluating the impact of unplanned interruptions or work requests that may arise during the sprint. It is crucial to start with a well-planned initial execution sprint scheduled a week before the start of the first sprint. This approach provides enough time for the team to plan and prepare adequately. During this initial sprint, the team should establish a repeatable approach throughout the project.

Every Day

• Stand Up: Virtual in Google Chat or as part of a recurring meeting

• Adding to and reviewing the backlog as needed with assistance from PM

• Continued monitoring of impediments, cross-team needs, and scope changes

• Adhering to established standards and levels of quality

• Adhering to established Monday.com usage standards

Day 1 — Start of the Sprint

• Monitor Progress: Throughout the sprint, monitor progress towards the sprint goal and adjust the plan as needed.

Day 5 — Mid-Sprint

• Review: Progress on current Sprint

• Determine the goals of the upcoming sprint

• Prioritize: Develop a prioritized list of tasks on deck for execution

• Estimate Effort: Review the estimated hours and reestimate or assign a level of effort to each task

• Communicate the Plan: Share the sprint plan with the team, the project stakeholders, and any other relevant parties.

Day 10 — End of the Sprint

• Sprint Review: Conduct a sprint review to present completed work to stakeholders and gather feedback.

• Sprint Retrospective: Hold a sprint retrospective to discuss what went well, what didn't, and what items can improve in the next sprint.

The Delivery Team can effectively plan and execute each sprint in a successive version model by following these steps.