Requirements Engineering with Scrum

How can engineering be driven within Scrum Requirements and how can this be carried out with high quality in compliance with the current standards? This section deals with this specific question. First here we will look into the key tasks of the Product Owner and the possibilities to estimate and plan requirements. The chapter additionally describes an adapted and optimized mode for dealing with requirements.

How can engineering be driven within Scrum Requirements and how can this be carried out with high quality in compliance with the current standards? This section deals with this specific question. First here we will look into the key tasks of the Product Owner and the possibilities to estimate and plan requirements. The chapter additionally describes an adapted and optimized mode for dealing with requirements.

This chapter goes into more detail on how professional requirements engineering can be achieved within the Scrum framework. It is based on the idea of the 3-staged product backlog that we described earlier.

Not every team can rely on user stories and personal communication only. The enterprise world is full of company-wide norms and regulations on how to write and maintain requirements. We do not propose to leave direct communication aside, but rather incorporate it into a more formal process for agile requirements engineering.

Scrum Iterative Requirements Engineering

Diagram 18: Iterative Requirements Engineering

Every requirement that is analyzed, specified, documented and not transformed into a feature that delivers value is considered a waste in lean thinking. In agile projects, potential waste is minimized by interleaving requirements engineering with development and testing. This bridges the gap between analysts and developers and fosters communication and close collaboration.