Hi folks,
Id like to find out what are the factors that make your Sprint planning events take shorter or longer times, and perhaps share your reflection on how your team perceives its effectiveness and efficiency…
In the teams Ive served, i noticed that they do not like to spend a lot of time figuring out how to work together as a team during sprint planning, and simply communicate and interact via their stories and tasks that have been broken down to serve each individual of the team. Most of what they want to achieve in a sprint has already been laid out through high level objectives, and they have more of a continuous development cadence rather than a more volatile, value/ goal-driven sprint. This results into their 2 week sprint planning to takr only 1 -1.5 hours.
So far it has worked for them, but when issues such as bugs or clarifications are required, they resort to email or chat to communicate, resulting in various issues with traceability and lack of shared visibility in the progress.
For the individual team member, the practice seems to feel efficient and effective, but i have my doubts if i zoom out to whole team level.