Interesting read and works well when building a new system with new features when all is complex. I struggle a bit when it is not so complex any more, for example the system needs 300 templates generated as PDF with data coming from different sources. For the first 5 this is challenging for the developers. However, after number 10, this is just a little factory, doing the same over and over again. No complexity here. All clear and no real need to dive into the added value, that was already clear from the first rounds. And all 300 are really needed, which takes about a year to complete. Any suggestions how to incorporate empiricism here in a useful manner?
Good read !!
Interesting read and works well when building a new system with new features when all is complex. I struggle a bit when it is not so complex any more, for example the system needs 300 templates generated as PDF with data coming from different sources. For the first 5 this is challenging for the developers. However, after number 10, this is just a little factory, doing the same over and over again. No complexity here. All clear and no real need to dive into the added value, that was already clear from the first rounds. And all 300 are really needed, which takes about a year to complete. Any suggestions how to incorporate empiricism here in a useful manner?
Hi Michael.
Great points indeed. I believe that Scrum will not be optimal in that case.
You may ant to look into approaches like Kanban. Here's a great video about that topic: https://www.youtube.com/watch?v=FrgMlmHS7cY