Follow a manual added link
The Essential Guide to Requirements Management
Chapters
- 1. Writing Requirements
- Overview
- 1 What is Requirements Management?
- 2 Non-functional requirements examples and templates
- 3 Product requirements document template and examples
- 4 How to write system requirement specification (SRS) documents
- 5 How to Write an Effective Product Requirements Document
- 6 Functional vs. Non-functional requirements
- 7 Characteristics of Effective Software Requirements and Software Requirements Specifications (SRS)
- 8 8 Do’s and Don’ts for Writing Requirements
- 2. Requirements Gathering and Management Processes
- 3. Requirements Traceability
- Overview
- 1 What is Requirements Traceability and Why Does It Matter for Product Teams?
- 2 Requirements Traceability, What Are You Missing?
- 3 Four Best Practices for Requirements Traceability
- 4 Requirements Traceability: Links in the Chain
- 5 What Are the Benefits of End-to-End Traceability During Product Development?
- 4. Requirements Management Tools and Software
- 5. Requirements Validation and Verification
- 6. Meeting Regulatory Compliance and Industry Standards
- 7. Project Management
- 8. Measuring Requirements
- 9. Conquering Key Requirements Management Challenges
Measuring Requirements
In this chapter, we cover accurately measuring requirements and why disciplined organizations collect a focused set of metrics for all of their projects.
These metrics provide insight into the size of the product; the effort, time, and money that the project or individual tasks consumed; the project status; and the product’s quality. Because requirements are an essential project component, you should measure several aspects of your requirements engineering activities.
In this chapter, we’ll look at several meaningful metrics related to requirements activities on your projects, including:
- Product size and requirements quality
- Measuring status and requests for change
- The benefits of measuring requirements