Preparation

As the saying goes, preparation is crucial! This principle is particularly true for sprint planning.

Backlog Refinement

I prefer to organize backlog refinement sessions about a week before sprint planning, focusing on the top five tasks and assessing the complexity of each. Having a well-organized backlog simplifies the sprint planning process considerably. Introducing new features in the backlog refinement session allows your development team to review the tickets, grasp specifications, and identify any technical needs prior to sprint planning, ensuring they are well-prepared.

Strategy and Roadmap Alignment

It's also vital to review your overarching strategy, key performance indicators (KPIs), and roadmap to confirm that your goals are still aligned. Regularly checking in on these elements aids in discussions with stakeholders about the upcoming sprint and helps in formulating initial goals for sprint planning, which can stimulate meaningful conversations during the session.

Review Unfinished Tasks

First, it’s essential to analyze any incomplete tickets from the last sprint (referred to as spillage) and understand the reasons behind this. While it’s important to recognize these issues, detailed discussions should be reserved for the 'Retrospectives' phase, not during planning.

Prioritization of Tasks

Next, revisit the priority items identified in the refinement session. It’s beneficial to review these again as some team members may have been absent, priorities may have shifted, or someone may wish to contribute insights.

Establishing Goals

Once you've discussed the tasks to be undertaken in the upcoming sprint, summarize the sprint's objectives and how they align with your roadmap and team goals. You can start with some preliminary objectives drafted during your preparation, but it’s crucial to encourage team discussion. Clear goals are necessary to evaluate success at the end of the sprint.

Fostering a Positive Culture

Another critical point is to avoid overloading your team with excessive work. If you have been collaborating with your team for a while, you will have a sense of their velocity. Developers may not appreciate being pressured about velocity, so it's best to set goals and allow them to communicate their effort and complexity assessments.

Sprints are relatively short in the context of larger projects, making it vital to cultivate a positive team culture and effective working methods for seamless sprint execution.

Decisions and Actions

Post-meeting, it's important to summarize any significant decisions or actions (including assigning responsibilities) in preparation for the forthcoming sprint. I prefer using Confluence for distribution, though this may vary based on your organizational setup.

Flexibility is Key

Another essential aspect is to maintain flexibility during the sprint. Many mistakenly believe that everything is fixed once the sprint begins, which can lead to inefficiencies and wasted time in pursuit of a flawless plan. Strive to be adaptable while still aiming to meet the sprint goal. This approach may entail managing spillover tasks, bugs, and the core tickets needed to achieve your objectives. It’s also beneficial to allow for the inclusion of urgent tasks mid-sprint or to remove items if necessary to meet the sprint goal.

In conclusion, effective sprint planning should inspire your team to continue striving toward overarching objectives. By clearly defining expectations, you prevent your team from having to guess their responsibilities, which is a failure on the part of the Product Manager. Establish explicit goals, encourage input and adaptability, and create an environment in which your team can thrive.

Thank you for reading! If you want more insights, follow me on Twitter!