...
Sprint estimation – sync or async styles? Thoughts on planning poker?
Joyce Sato-Reinhold thinks: nice to have everyone’s input on each ticket. Async interface nice (+1 Duncan Brain)
Duncan Brain is planning poker useful? Estimation is personalized per person. When sync it was many hours of meetings each sprint between planning, estimation, backlog…
Time to start using estimated points on Jira?
PR Reviews velocity?
Anto Sgarlatta estimates don’t have to be exact; different perspectives on difficulty will even out by having everyone estimate. For contract metrics too it makes sense to have everyone / more people estimate. Our estimates might also move towards agreement over time. Conducting meetings (see backlog refinement below) where we go over the tickets would give us some chance to discuss the tickets (more valuable than straight voting). Discussing why votes are different is more valuable than straight averaging.
Estimation could also be part of the technical breakdown of a feature - after the technical document lead for that feature presents the breakdown, estimation is done together by the team
This would also help with estimating the scope + time required to deliver a feature
Feel free to hold estimates loosely
Estimates could be thought of as belonging more to the team than to individual developers (+1 from Joyce Sato-Reinhold)
Time-based estimation also can lead to unwarranted time stress when tackling tickets of a certain point estimation
Sayaka Ono agrees we should estimate on ticket complexity (not time)
Claiming tickets vs assigning?
Duncan Brain & Sayaka Ono prefer assignment and Joyce Sato-Reinhold prefers picking so we can do a mix. Assignments will also happen with some input
...