Project Plan with Gantt Timeline
A real Gantt chart: tasks by phase with dates, owners, dependencies, progress bars across 16 weeks and schedule status.
SpreadsheetProject PlanningFree
Trace every requirement to its source, design and tests, and see coverage and verification at a glance.
Shown with sample data
Trace every requirement to its source, design and tests, and see coverage and verification at a glance.
A requirements traceability matrix proves that everything agreed was built and tested, and that nothing was built that nobody asked for. Each requirement links back to its source and forward to its design reference and test cases; the matrix flags gaps, failed tests and untested must-haves and calculates coverage and verification by priority. The sample traces an HR self-service portal.
Forward traceability follows requirements to design and tests, proving everything is delivered. Backward traceability follows tests and features back to requirements, proving nothing unrequested was built.
Usually the business analyst or QA lead, with input from developers and testers. It must be updated at every change, not reconstructed before go-live.
Yes, especially in regulated environments. Many agile teams keep a lightweight matrix linking epics and user stories to acceptance tests.
Download a copy
Downloads need a free account.