3 ms·
The point of the question is that you should have a spec and a schedule. A groomed prioritized backlog isn't a replacement as it often doesn't have a real spec
by YZF 9y ago
The point of the question is that you should have a spec and a schedule. A groomed prioritized backlog isn't a replacement as it often doesn't have a real spec and doesn't imply a schedule.
What will your product look like? (in enough relevant detail) When does it get delivered? These are two critical questions. These things are always subject to change but a business should know what it's aiming for.
- tootie 9y agoThe point of agile is that your spec and schedule are nonsense. So-called BDUF has failed time and again and the reasonable approach is to not bother planning more than a few weeks at a time and be able to change priorities quickly.
- YZF 9y agoThis isn't about big design up front vs. "Agile". In my personal opinion if anything is a failure it's Agile which has turned into an excuse for pushing people around, poor management, poor software development. You have to keep your eye on the ball, know where it's going and be flexible. You can't just be flexible. You can't build anything of consequence by only planning a few weeks ahead out of context of some larger plan. If you have no idea where you're going you're going to mess it up a few weeks at a time. JMHO and I've done everything under the sun from various flavours of Scrum, XP, to more traditional project management techniques. This question will help you find out if you're going into a chaotic and stressful environment or if things are under some sort of adult supervision...