Presenter:Jurgen De Smet
Objectives of the session:
The session should lead to a better understanding of decomposing requirements and how this influences its environment. By understanding the effects of decomposition one can better estimate to what level of decomposition he/she really wants to apply in their daily doings.
Intended audience and prerequisites
All people handling requirements from the beginning till the end and who are interested in the how, why and effect of decomposing to the lower level. Especially non believers are welcome, we love to get new insights ourselves.
In order to get things done in small iterations one has to split (decompose) epics, themes into simpler stories, manageable within a single iteration and... it doesn't stop there what about the tasks following? How simple is simple and when does it become insane?
You'll get a presentation on how we actually decompose our requirements towards small and simple tasks related to story points (scrum), based on try outs and experience. Simultaneous we'll show how one could address this in real life and what effects it has within our software development environment. We'll try to give you a link towards code decomposition, removing unknown waste and how it might help in fulfilling fixed price projects.
Justin Wyant made a nice remark on the chaos theory: "The most interesting thing to me about chaos theory is that within all the complexity is an underlying simplicity that shines through." which is a good reasoning to come up with single user stories for an iteration and break things down.
Looking at the tasks we get more doubts about the depth ... we might quote Albert Einstein here: "Everything should be made as simple as possible, but no simpler", so when do we hit the mark: simple as possible? Not always that easy or common ground around us.
So ... after the presentation we must have an open dialog with (hopefully) all participants to gain deeper knowledge about the 'simple level' in relation to decomposing requirements within our IT landscape. Identifying concerns and maybe even pitfalls in order to become better organized and prepared for future projects/implementations.
Format and length: 60 min Interactive presentation