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

Text formatting

Browse Source
This commit is contained in:
William Sandner 2021-08-01 12:40:47 +02:00
parent 355af643e5
commit 2ffaf0efc4
1 changed files with 15 additions and 41 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

56
Feature-Format.md
View File

@ -1,3 +1,4 @@
<!-- markdownlint-disable-next-line MD041 -->
##### Project ##### Project
::[PROJECT-NAME](Home) ::[PROJECT-NAME](Home)
@ -56,50 +57,23 @@ Notes and Questions:
### Feature Attribute Values ### Feature Attribute Values
- Priority - Priority
- Essential: The system could not or would never be used without - Essential: The system could not or would never be used without this feature. It would be much harder to test, document, or package the product without this feature.
this feature. It would be much harder to test, document, or - Expected: Key stakeholders strongly desire and expect this feature. It may have been promised to them in a certain release. It's absence would substantially reduce the success of the project.
package the product without this feature. - Desired: Stakeholders desire this feature. It's absence would reduce the success of the project.
- Expected: Key stakeholders strongly desire and expect - Optional: This feature would be nice to have. Adding it could have some advantage, but delaying it would not have a big effect on the success of the project.
this feature. It may have been promiDIAGRAMsed to them in a certain
release. It's absence would substantDIAGRAMially reduce the success of
the project.DIAGRAM
- Desired: Stakeholders desire this feDIAGRAMature. It's absence would
reduce the success of the project.
- Optional: This feature would be nice to have. Adding it could
have some advantage, but delaying it would not have a big effect
on the success of the project.
- Effort - Effort
- Months: A very large feature that is too big to estimate and - Months: A very large feature that is too big to estimate and should be broken in to smaller, better-defined features.
should be broken in to smaller, better-defined features.
- Weeks: A large feature that will take 40 to 160 hours to add. - Weeks: A large feature that will take 40 to 160 hours to add.
- Days: An average or easy feature that would take less than 40 - Days: An average or easy feature that would take less than 40 hours to add.
hours to add. - Hours: A very easy feature that would take less than 8 hours to add.
- Hours: A very easy feature that would take less than 8 hours to - Note that "adding" a feature means doing all of it's design, implementation, technical documentation, user documentation, and testing. Even the easiest feature takes hours to add.
add
- Note that "adding" a feature means doing all of it's design,
implementation, technical documentation, user documentation,
and testing. Even the easiest feature takes hours to add.
- Risk - Risk
- Dangerous: Implementing this feature successfully would require - Dangerous: Implementing this feature successfully would require overcoming risk factors that are more than three or unknown in number. It should be broken down into parts, better specified, or risk factors should be eliminated prior to implementation.
overcoming risk factors that are more than three or unknown - 3-Risks: Implementing this feature would require three risk factors to be overcome. Any single release should contain at most a few such high-risk features, and contingency plans should be considered. You should be able to list the risks.
in number. It should be broken down into parts, better - 2-Risks: Implementing this feature would require two risk factors to be overcome. This is normal for challenging features. You should be able to list the risks.
specified, or risk factors should be eliminated prior - 1-Risk: Implementing this feature as specified would require one risk factor to be overcome. This is normal for many features. You should be able to describe the risk.
to implementation. - Safe: Implementing this feature as specified is just a matter of time and effort, there is no real risk of failure.
- 3-Risks: Implementing this feature would require three risk - A "risk factor" is a task or fact that is currently in doubt, but that must turn out well in order for the feature to be successfully implemented. See tips on managing risk below.
factors to be overcome. Any single release should contain at
most a few such high-risk features, and contingency plans should
be considered. You should be able to list the risks.
- 2-Risks: Implementing this feature would require two risk
factors to be overcome. This is normal for challenging features.
You should be able to list the risks.
- 1-Risk: Implementing this feature as specified would require one
risk factor to be overcome. This is normal for many features.
You should be able to describe the risk.
- Safe: Implementing this feature as specified is just a matter of
time and effort, there is no real risk of failure.
- A "risk factor" is a task or fact that is currently in doubt,
but that must turn out well in order for the feature to be
successfully implemented. See tips on managing risk below.
### Further Information ### Further Information