Analysis

Please note: A revised and extended version of this post can be found here. I recently coached a team that ran into problems because the user stories in their sprint turned out to be too big. This inspired me to create a cheatsheet (pdf) with 8 common Agile strategies for splitting up user stories. During the next sprint planning session, the team successfully managed to split large user stories into smaller ones and helped the product owner prioritize them. In this post, I want to share the cheatsheet and extend it with some background and additional examples. Hopefully, you can…

One of the hardest things you'll have to do when you write applications for customers, directly or indirectly, is capturing the requirements in a form that is understandable for all involved parties. Especially when the projects are complicated, finding a good mode for writing down functionality becomes progressively harder. There are many things to keep in mind:  Requirements should not be too technical, otherwise the customer will not be able to understand; Requirements should clearly describe their intended goal, so that developers can keep this in mind; Requirements analysis shouldn't deliver huge documents that are hard to maintain;…