Agile Requirements Management

Agile requirements management is characterised by the idea that it's not useful to specify all requirements to the smallest detail. In fact, the incremental nature of agile projects allows us to start development rather quickly. We profit from short feedback cycles as we adapt any requirements whenever necessary.

For sure, requirements management should be as straightforward as possible. The best way to achieve this is a well-organised backlog, which requires regular discussions and prioritisation together with the domain experts.

Bridging the Gap between Domain Experts and Developers

Personally I find it important to combine domain esxpertise with a good deal of technical knowledge. This way it's possible to understand the requirements and to transform them in a structured form that can serve as the basis for software development.

I'm happy to offer support regarding such tasks. In an agile project this will likely mean that I assume the role of product owner:

Imprint: Dr. Andreas Rüping, Sodenkamp 21 A, 22337 Hamburg, Germany, Tax Id 26/225/34412 (Tax office Hamburg-Nord), VAT identification number DE235918641