Do we need Daily Scrum on the sprint planning day?
People who have subscribed to Mike Cohn’s newsletter can very well skip this blog
I personally think that we don’t need a daily scrum meeting on the sprint planning day. Assuming that you follow the 3 questions model, let us talk about three questions asked during daily scrum & why you don’t need the meeting on the sprint planning day.
What did you do yesterday?
Every team member would have worked on closing the stories they committed to. Part of it would have already been closed & probably you would have demo-ed it to the product owner & may be to the team. The other stories would have been carried over to the next sprint. You would definitely talk about these during sprint planning.
What are you planning to do today?
You may probably need the sprint planning meeting to answer this question.
Is the team facing any impediments?
Chances are that these impediments were the reason why a few stories got carried over to the next sprint. So, we would totally talk about these in the sprint planning meeting.
This is just my take on this question. What would be yours?
Senior Program Manager @ NielsenIQ
8 年at our workplace, team had decided not to have daily scrum during planning and review & retro days. the reason being, team anyway have a common agenda for these 2 days.
Independent Professional-, Agile & Senior Management Coach | Trusted Advisor | Founder & Co-Author Agnostic Agile (NPO) | Co-Founder & Co-Author Agile 2 | Change Catalyst | SW Developer | 15K+
8 年First thing would be let the team decide. It depends. You say sprint planning day. First thing it depends on how long is the sprint and therefore sprint planning "official timebox" - a mere guidance. So for a one week sprint that would be a 2 hr timebox. Then it depends on how long sprint planning actually takes and is done. And when it is done. Then it depends on when the team normally does their Daily Scrum. And we are not there yet, it depends on what actually is in flow. And that may depend on when the sprint review has been done on the previous working day. So many scenarios are possible. E.g. Sprint review was on Fri morning. There was some feedback and working around the retro, team actually started to work on some of that feedback. As not to waste time and as this was fully inline with PO's priorities. Why waste half a day? Now, Monday morning sprint planning takes place. It takes 1.5 hour. Team normally does a Daily Scrum at 2pm, midday, just after lunch. Then why not do it on that Monday? And maybe ion the Friday. As my teams work in a continuous flow, and as the Daily Scrum takes usually less than 10 minutes, I am a big fan of doing it every day at the same time. The work does not stop with / between the Sprint Review and Sprint Planning. On a sprint planning day a Daily Scrum is also a good way to kick off the new work.
Working with teams to help them work better.
8 年We don't bother with a stand-up on the first of last day of a Sprint; the team is about to demo what is done on the last day, and we're figuring our what's next on the first day. The gap between closedown and start-up is usually where the SM and PO spend some time discussing stories based on what is "done" The rest of the team usually uses that time for "good works"; we only allocate 80% of the team's available time to the Sprint. Generally its small bug fixes, refactoring, learning, addressing technical debt, infrastructure tasks, research and so on.
Technical Program Management | Leader | Agilist
8 年I agree with you Ken. I was referring to a team level daily scrum. Given the scenario you have explained, i would agree with you.