Suborbital-Systems-Public/ReadySetGit
3
0
Fork 0
Code Pull Requests Packages Projects Releases Activity

Fix linter warnings

Browse Source
This commit is contained in:
William Sandner
2021-08-01 15:15:57 +02:00
parent 70a43d171f
commit 704e13c18f
30 changed files with 135 additions and 106 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
Risks.md
View File

@@ -1,3 +1,4 @@
<!-- markdownlint-disable-next-line MD041 -->
##### Project
::[PROJECT-NAME](Home)
@@ -11,7 +12,7 @@
- [Project plan](Project-Plan)
- [Software development methodology](SDM)
##### References:
##### References
- [Risk Management during Requirements](http://www.systemsguild.com/pdfs/s5req.lo%201.pdf) by Tom DeMarco and Tim Lister
- [Taxonomy-Based Risk Identification](http://www.sei.cmu.edu/pub/documents/93.reports/pdf/tr06.93.pdf) by Carr, Konda, Monarch, Ulrich, and Walker (SEI)
@@ -55,7 +56,7 @@ take away our lessons learned and any valuable project bi-products.
pretend everything is fine and hope that none of the
stakeholders notice.
#### Risks that consume development resources.
#### Risks that consume development resources
::The project has a fixed deadline. The requirements are prioritized.
If we lose time, we will reduce project scope.
@@ -76,7 +77,7 @@ delivery date.
| Name | Description | Likelihood | Impact | Plan | Status | Owner |
|-----------------|---------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-------------------|
| ::Requirements | Requirements are only partly known at project start. Customers may not allocate sufficient resources to exploring requirements. | Medium | Critical to Catastrophic | Requirements will be detailed first for the top priority goals. Indicator: Track the rate at which requirements are discovered. Contingency: request more customer effort. | Amber | Requirements Lead |
| ::Goals | Stakeholders goals may conflict. | Medium | Critical | Keep an explicit list of stakeholders goals. The project manager will report progress to each declared goal. | Green | Customers |
| ::Goals | Stakeholders goals may conflict. | Medium | Critical | Keep an explicit list of stakeholders goals. The project manager will report progress to each declared goal. | Green | Customers |
| ::Communication | Communication problems in development team. They are dispersed among several sites, and have not worked together before. | Medium | Critical | Use these [tools](SDM#communication) to help communication. The main indicator of miscommunication will be software defects detected by our [QA activity](qa-plan). | Green | QA lead |
| ::Acceptance | Customer may accept delivery of the system although it does not really meet their goals. | Medium | Critical | Customers are asked to declare acceptance criteria as each release is planned. | Green | Customers |
| ::Scope | The total features requested may be beyond what the development team can deliver in the time available. | High | Marginal | Assign levels of important to the use cases. Make the first review of project scope after 12 months. | Green | Customers |
@@ -173,4 +174,4 @@ the project could deliver.
RISKNAME
RISKNAME and strength of character of
RISKNAME
RISKNAME
RISKNAME