The spiral model is risk driven. It attempts to resolve the biggest risks first. Risk considerations are used to decide how much effort and detail is needed for each type of work: requirements, design, implementation, quality assurance, and deployment.
Other issues in this repository describe risks that are common to all system development projects. The title of each of these issues starts with "Risk: ", and all of them are initially labeled "High Risk".
[ ] Add more issues to describe other risks that are unique to this project. Start the issue title with "Risk: ".
[ ] On a continuous basis, update the risks issues to reflect: status and progress of resolving, planning, and managing risks, the severity of risks (High, Moderate, and Low labels), and the relative significance of risks, based on their likelihood and impact.
[ ] Each week, create, (re)prioritize, (re)assign or otherwise modify project tasks, with a goal of reducing the most significant risks in the coming week. These tasks may be captured in this repository, or elsewhere. Be sure to communicate with the team.
Never delete or close any of the risks issues. Even the Low Risk issues should be reviewed frequently in case they are affected by changing circumstances.
4 Issue by smattingly,
The spiral model is risk driven. It attempts to resolve the biggest risks first. Risk considerations are used to decide how much effort and detail is needed for each type of work: requirements, design, implementation, quality assurance, and deployment.
Other issues in this repository describe risks that are common to all system development projects. The title of each of these issues starts with "Risk: ", and all of them are initially labeled "High Risk".
Never delete or close any of the risks issues. Even the Low Risk issues should be reviewed frequently in case they are affected by changing circumstances.