Chapter 8. Requirements and test management
This chapter covers
In this chapter, we’ll discuss how to implement collaborative and barrier-free development. We’ve already discussed tools that support release management, connecting the roles and artifacts in a task-based way. We also looked at how you can integrate the software delivery step into this process chain by integrating Mylyn with build engines. But build engines such as Jenkins, Bamboo, and TeamCity are only the infrastructure—they call your scripts, compile and test your application, and then package and deploy it. These steps don’t say anything about the quality of the software in terms of how (and if) it implements customers’ requirements.
In this chapter, we’ll focus on the requirements and test management, and on integrating them with the coding phase.[1] Solid requirements management is essential for project success. “Studies of factors on challenged projects revealed that 37% of factors related to problems with requirements,” such as poor user inputs.[2] As you have already learned, the development phases are highly integrated. Requirements management, development, and delivery are all part of the development lifecycle.