3 ms·
What if that turns out to be an inefficient (poorly-architected) way to break it down? But it's half-implemented by the time someone calls attention to it, and
by rabidrat 8y ago
What if that turns out to be an inefficient (poorly-architected) way to break it down? But it's half-implemented by the time someone calls attention to it, and it doesn't get re-architected because it's too late now.
Breaking things down appropriately is, in my mind, 80% of the work. If you have your head straight, the implementation is easy; but it can take implementing virtually the entire thing to get your head straight.
- jimnotgym 8y ago> What if that turns out to be an inefficient (poorly-architected) way to break it down? Don't break out later stages too early then! Just enough to get to MVP. That is the essence of agile and XP isn't it?
- rabidrat 8y agoIf I don't break them out "too early" then that often means I'm not breaking them out until I'm almost finished :)
- jimnotgym 8y ago> but it can take implementing virtually the entire thing to get your head straight. Seems to fit your needs then!
- randomdata 8y agoWell, the developer didn't need it in the first place. It is not a useful tool for developers as we have better tools for developers. It is management that wants to see the work up in pretty JIRA lights and they want to see it before the project is already done.
- TheCoelacanth 8y agoThat's how agile should be done. You should plan out the things that you are doing short-term in more detail and the things you are doing long-term in less detail because you don't know as much about it and it is more likely to change.