Review: IREB handbook on agile requirements management (RE@Agile)
Summary: Even though English is now the lingua franca in engineering, it can be more pleasant to read specialist literature in German. In this respect, many readers will be pleased that the recently published IREB handbook on agile requirements management is available in both languages.
Target group: Training providers who would like to offer seminars or training courses on RE@Agile in accordance with the IREB standard. Decision-makers who want to assess whether RE@Agile is suitable for their team. Interested parties who want to understand the content of the curriculum.
Rating: ★★★★☆ On around 100 pages, the handbook presents the content of agile requirements management in a compact and clear manner, which serves the purpose perfectly: It is the link between the curriculum and further reading and can be consumed in a couple of hours. It should not be misunderstood as a textbook, but the authors make it clear in many places that it is not.
Acquire: The manual is available in German and English downloaded free of charge from the IREB website become.
Details: Until about 15 years ago, requirements management and agile development were two separate disciplines. But now they have grown together. How this came about is explained in the entertainingly written Chapter 1 described. Knowing the historical context is helpful to better understand the practice and to get all stakeholders on board in practice.
In Chapter 2 is by no means just about "starting projects successfully", as the title somewhat misleadingly suggests. Instead, it deals with important basics such as objectives, stakeholders and system scope. It also deals with the important topic of change, which is essential in an agile environment. Not only the theoretical basics are presented, but also concrete techniques that can be used in practice. For example, the reader learns that a system context can be captured in the form of a diagram/model or in natural language.
An important aspect of any system is its functionality, and this topic is Chapter 3 dedicated. Compared to the previous chapter, it is somewhat less practical. This is perhaps due to the fact that many decisions regarding the handling of functional requirements can be very project-specific. Nevertheless, there are some practical examples. The further literature must be consulted for more in-depth information.
Non-functional requirements have been out for a long time - it makes more sense to work with quality requirements and boundary conditions. This is what Chapter 4. Here it becomes a good deal more concrete again, for example through lists of classes of quality requirements or boundary conditions. It is clearly illustrated how important this category of requirements is for the success of the project.
Once we know our requirements, they need to be implemented. To do this, they must be prioritized and assessed, which in Chapter 5 is described. So we are moving from content to process. This also creates the bridge to business value. After all, successful products are to be developed and success is measured at business level. Here, too, lists and techniques help to establish the practical relevance.
This provides the core knowledge. However, there are still Chapter 6which deals with scaling. This is because larger organizations in particular are interested in the strategic use of agile approaches. This chapter presents planning tools and "complete solutions", such as the Scaled Agile Framework (SAFe).
Minor weaknesses
I rated the book four out of five stars. This is due to a few minor weaknesses. On the one hand, you realize while reading that different authors were at work here, which sometimes disturbs the flow of reading a little. Secondly, I would have liked the role of the tools used to be explained a little more. It is true that it is mentioned in many places that such tools exist and that their correct use is of strategic importance. Nevertheless, I would have liked further support here too, for example in the form of selection criteria and cost-benefit considerations.
Conclusion
The RE@Agile handbook is suitable for gaining a good overview of the subject matter in a short space of time. It is pleasantly concrete in many places, which holds theory and practice together.
Of course, a 100-page overview cannot replace specialist literature, and the handbook is not intended to do so. Instead, it helps to find the right literature for in-depth study of specific topics. And, of course, it is also an advertisement for the IREB and its certificates, as the IREB is certainly hoping that as many employees as possible will undergo IREB-certified further training.
