Almost 27 years of experience has taught me that estimation is a waste of time and a totally futile activity. Better to use that time simply getting on with the task
30 years for me. Only continuous delivery works in a 2 week sprint. Most valuable items only. No time estimates should ever be promised. Stick to Fibonaci estimates only.
For Scrum masters, I've told plenty that I won't estimate. If they insist, I tell them to fill in a number themselves. It does make for some 'challenging' conversations, but I think it's worth it.
The happiest, most productive teams I've worked on have been ones that are free to self organise - working in cycles that last 6 weeks.
For clients, good communication and managing expectations is key. Generally just showing them progress from time to time is the best way. Making dated promises is usually a sure-fire recipe for disappointed clients.
Almost 27 years of experience has taught me that estimation is a waste of time and a totally futile activity. Better to use that time simply getting on with the task
RIGHT ON!!!
30 years for me. Only continuous delivery works in a 2 week sprint. Most valuable items only. No time estimates should ever be promised. Stick to Fibonaci estimates only.
I just don't do them at all
what if client & Scrum master insist on asking time estimation fo reach task ? is NO or Can't a good answer ?
For Scrum masters, I've told plenty that I won't estimate. If they insist, I tell them to fill in a number themselves. It does make for some 'challenging' conversations, but I think it's worth it.
The happiest, most productive teams I've worked on have been ones that are free to self organise - working in cycles that last 6 weeks.
For clients, good communication and managing expectations is key. Generally just showing them progress from time to time is the best way. Making dated promises is usually a sure-fire recipe for disappointed clients.
thanks for sharing your experience, appreciate it.
Yessir