4 ms·
Sorry, there is no "faster" button. The only lever you have is cutting scope as you go. Fixed scope just makes no sense. Otherwise you get one of three outcomes
by ajmurmann 8y ago
Sorry, there is no "faster" button. The only lever you have is cutting scope as you go. Fixed scope just makes no sense.
Otherwise you get one of three outcomes:
1. We underestimated how much we can get done. People now start gold playing stuff and wasting time that would be better spent on future backlog items.
2. You estimated just right and are done Friday at 5pm. Obviously this doesn't happen frequently.
3. You overestimate and now something's gotta give. People will start cutting corners or putting in over hours as a punishment for being bad at estimation. This is not sustainable.
We need to get away from the fixed scope mentality with which Scrum had poisened the Agile pool. If we cannot trust or developers to do the best work they can and wanting to be proud of their work, the organization has entirely different problems.
- myth2018 8y agoExperience shows that this is not the way things work. Real-world team members present varying levels of maturity and, therefore, commitment levels to the aimed results. Some will work at their natural pace and deliver the thing, provided the estimates were accurate; some will relax and leverage the fact that it's always OK to say that there was not enough time; some will work hard at the beginning and get contaminated over time; and so on. It is sad to work without a 100% mutual trust, but we have to be realistic. Building trust takes time.