When developing software, teams discuss what can be done and what cannot be done given available resources, skills and technology. Three dimensional scopes visualize the potential for this kind of negotiation: they question breadth, depth and the newness of features. This comes in especially handy, when the scope appears to be tightly defined.
The challenge awaits our project: How to deal with the many expectations from our customers that are far beyond the project budget? The answer in my current project – the sports event management system – is based on user story mapping.
Currently, I’m involved in a project to develop an event management system for large sports events. The goal is to replace a few existing systems with one integrated system that is able to cater for the coming needs. End of elaboration is closing in and we’re planning for the incremental delivery to follow during construction. Budgeting, estimation and release planning all turn around features (Part 2).
