Okay. I didn’t mean to say everyone wants a one size fits all solution - but please understand that many seem to think that it’s that simple.
1/
1/
I’m not proposing that we need an alternative to blink estimation.
If we have a need to make the sort of decisions that blink estimation can try to inform - then there are plenty of techniquesxpeople are using. If they work well, then simply use them.
2/
If we have a need to make the sort of decisions that blink estimation can try to inform - then there are plenty of techniquesxpeople are using. If they work well, then simply use them.
2/
What I seek is alternatives to the sort things we currently believe is important to decide.
To me, the important consideration, and the discussion that led to the #NoEstimates hashtag, is about why we limit our ourselves to decisions that require estimates.
3/
To me, the important consideration, and the discussion that led to the #NoEstimates hashtag, is about why we limit our ourselves to decisions that require estimates.
3/
This is a starting point for exploring alternatives if the sort I am seeking. Not “what will we do instead of this type of estimating?”, but rather “is there another way to approach managing software development then making decisions based on estimates?”
4/
4/
I don’t expect this conversation to be interesting to many people. It’s interesting to me. If someone doesn’t get any good out of it, I can live with that. I’ve learned a lot, and gotten a lotta good from this sort of open conversation.
5/5
5/5
• • •
Missing some Tweet in this thread? You can try to
force a refresh
