Three simple patterns for successful requirements engineering

Successful requirements engineering requires a fine balance between urgent customer needs and strategic vision.

As an organisation, it is important to achieve the optimum between the following three patterns in order to gain consistency, certainty and measurability in the requirements engineering process.

1. Time to Market: Based on the individual market conditions, the appropriate work package slicing practice has to be defined. Ideally, the packages are as small as possible - deliver value continuously - but must still create substantial value for customers. Shortening lead times is a critical enabler.

2. Verification Cadence: User experience good practices demand that features are continuously tested with end users. It is important to find the right balance between revising and acting. Of course, the underlying business case must always be solid. Fostering an organisation wide understanding of good UX and establishing product metrics are key.

3. Product Runway: The organisation needs a steady flow in the requirements engineering process. If possible, the RE process should be closely aligned with the development process. Work packages must reach a certain maturity in the RE process - Definition of Ready - to be pulled by the development teams. By introducing a simple and transparent good practices, the teams receive a steady runway which also increases the predictability.