A set of properly formulated requirements enables the development team to kick-start the development. Unfortunately, documentation often demands that the team has to start by finding out what the requirements really mean and rather crawl out of the starting blocks. In traditional software developmetn this problem can hide under a long development cycle, but when applying agile methods such as Scrum, the problem becomes painfully clear.

An approach that has proven to be surprisingly effective is the combination of focusing on conceptualizing and modeling domain according to Domain Driven Design and the story format with concretized scenarios advocated by Behaviour Driven Development. This approach can also be used to enhance or supplement other requirements formats, such as use-cases in RUP.

During this full day course we work with a concrete example to discuss key issues, discover the pitfalls and find out how these can be avoided. In the example we introduce one requirement at a time, actively work to reformulate it in a terse way, revise the model that needs to be changed and continue with the next requirement. Along the way we touch on several key issues and put together a checklist to use in requirements formulation.

We also see how this ties together the entire development cycle from early requirements formulation to final acceptance testing.

After this course, your requirements will never be the same again.

For more information about the course, see the detailed course description (pdf)

Questions or concerns about the course?
Contact sales@omegapoint.se