Showing posts with label #agile #scrum #team #agilecoach #sprintplanning #team #scrummaster. Show all posts
Showing posts with label #agile #scrum #team #agilecoach #sprintplanning #team #scrummaster. Show all posts

Wednesday, October 18, 2017

Estimating versus Sizing

We were having a discussion in our team room, around the importance of using right term during grooming or planning. Should we use word Sizing vs. Estimation. 

In my mind, the word estimation brings along it's own baggage. We have all been held accountable to estimate that we've regretted. As per Nassim Taleb, we are bad at estimation because there is a whole bunch of randomness just waiting to pounce on our lovely estimated. And as we know randomness in our project goes only in one direction; more money, more time and more scope. We try to manage the randomness by trying not to:

- Estimate in detail, since it can't be accurate anyways so why bother taking so much time.
- Estimate precisely, we try using range or complexity rather than hours or days 
- Estimate big stories vs. try to bite off small chunks, 

But I still have seen fellow team members trying to be accurate while providing estimation. So how about we stop estimating and instead start sizing using Story Points. In brief, Story Points are meant to offer a way to size user stories. For instance, a user story might be marked as small, medium and large. Another way to size stories is to use fibonacci sequence like 1, 3, or 5 etc. I don't want to discuss Story Points in this blog. It is another topic on it's own. 

We can figure out some abstracted buckets with team and use them in our grooming/planning conversations. Those conversations will move lot quickly since the amount of debate between developers is dramatically reduced. We should always look back later to see how we did and adapt. We want to have discussion around good user story but not waste our time on how it's estimate looks like :). 

Let's RIP ESTIMATING! 
Manisha

Monday, September 12, 2016

Value of Sprint Planning meeting

As per Scrum Guide, "Sprint planning" meeting is held to identify/plan the work to be performed in the Sprint. It is a time-boxed event, where teams collaboratively plan the work of the entire sprint. Also, we should try answering two questions in the meeting :
  • What can be delivered in the increment resulting from the upcoming Sprint?
  • How will the work needed to delivery the increment be achieved?
In my mind, the Sprint Planning meeting should create a shared understanding of the piece of work. POs should make sure team understand the value and can visualize the real objective behind the work. 

Also, I don't like one big fat meeting. I am a big fan of backlog grooming meetings, which happens regularly and almost part of any scrum cadence. I would suggest doing it every day like stand-up. May be just after standup, team pick up one top backlog story and discuss with POs. They together try to understand the story. Doing everyday has following advantages:
  • Not taxing to your brain: Since sitting in a long meeting for hours makes every one very tired. Towards the end, everyone just wants the meeting to be over and lose the sprint of asking questions.
  • Keeps it focused: Doing one everyday is lot easier and PO feel less pressurized about the decision since it is not at the eleventh hour and he can give patient hearing to teams point without getting worries about the sprint commitments.
  • Teams can re-iterate over single story multiple times and get proper clarity. 
  • Team members are more involved during this mini planning session vs. big fat one. Also they are in the team space, which makes things lot simpler for them to look or clarify. 
  • Sprint Planning meeting becomes a breeze. We finished our meetings in 30 minutes :).
I did face little roadblocks at times in this process: 
  •  At times team member's memory needed to be refreshed because either they forgot or they were on holiday that day. 
We use to have three columns before backlog column:
  • Feature/Story Requested - PO adds them to be in the backlog as per DoR
  • Feature/Story Discussed - PO discusses them with entire team and they size the card
  • Feature/Story Ready to be prioritize - It is ready to be pulled into the sprint
Never stop the collaboration because you have time pressure, would be my suggestion. Let me know things which you might have tried in your team.

Thanks
Manisha