Improve our team’s development efficiency by identifying what we really want to work on early on, and make sure we are prioritizing the right work at the right time.
Stage | Description |
---|---|
0 | Team does ad-hoc requirements gathering, but nothing organized or done consistently. |
1 | Team uses agreed-upon requirements gathering techniques and to store results from requirements gathering in a shared repository. |
2 | Team has selected format for recording requirements and works with stakeholders to refine those requirements as needed (including removing complexity and breaking apart requirements into smaller increments). |
3 | Team has created a definition of done checklist that captures all the tasks involved in closing out a requirement (e.g, CI testing, code review, customer acceptance, etc.). |
4 | Team has a shared process in place for gathering and reviewing requirements. |
5 | Team regularly reviews the backlog of requirements to prioritize work effectively, and conducts periodic retrospectives on past work to see what went well and how to improve. |
Created at the SEA ISC’22 PSIP tutorial by Erik Kluzek, Christina Holt, Edward Hartnett, Julia Kent, William Lopez, Reed Milewicz, and Elaine Raybourn.
What Are CSE Software Requirements?
An Introduction to User Stories and How to Write Them
This Project Tracking Card originated from the PSIP PTC Catalog. The development of the PSIP PTC Catalog was supported by the Exascale Computing Project (17-SC-20-SC), a collaborative effort of the U.S. Department of Energy Office of Science and the National Nuclear Security Administration.