Quantifying requirements volatility effects
Science of Computer Programming
Requirements engineering process improvement: an industrial case study
REFSQ'11 Proceedings of the 17th international working conference on Requirements engineering: foundation for software quality
| Hi-index | 0.00 |
Requirements are a crucial ingredient of any successful project. This is true for any product-software, hardware, consumer appliance, or large-scale construction. You have to understand its requirements-what is needed and desired-if you are to build the right product. Most developers recognize the truth in this statement, even if they don't always live up to it.Far less obvious, however, is the contribution that the requirements activity makes to project management. Requirements, along with other outputs from the requirements activity, are potent project management tools.In Requirements-Led Project Management, Suzanne and James Robertson show how to use requirements to manage the development lifecycle. They show program managers, product and project managers, team leaders, and business analysts specifically how to: Use requirements as input to project planning and decision-making Determine whether to invest in a project Deliver more appropriate products with a quick cycle time Measure and estimate the requirements effort Define the most effective requirements process for a project Manage stakeholder involvement and expectations Set requirements priorities Manage requirements across multiple domains and technologies Use requirements to communicate across business and technological boundariesIn their previous book, Mastering the Requirements Process, the Robertsons defined Volere-their groundbreaking and now widely adopted requirements process. In this second book, they look at the outputs from the requirements process and demonstrate how you can take advantage of the all-important links between requirements and project success.