1. What are some of the features of well-written requirements?
2. What are some of the most common problems with writing requirements?
3. Did I find any internet site(s) that I would especially recommend to others?
1.Some of the features of the requirement are as follows:
- Requirements is classified into four categories as
- Mandatory – A feature that must be built with no exception.
- Desirable- A feature that must be built only if the constraint is flexible.
- Optional – Feature that can be built but it’s always a choice
- Possible future requirement – A feature beyond when the project is completed mostly suggestion about future project expansion it’s more like optional requirement of future (URL 1, 2017)
There can be a possible hybrid requirement also (Shenoy, 2017)
- A good requirement must have the following characteristic they are
- Verifiable – State requirement in such a way that it can be tested and demonstrated.
- Clear and concise – State one requirement in a statement with clear and unambiguous without multiple interpretations.
- Consistent – Must not interfere with another requirement
- Complete – Must be complete i.e. must have all the information needed.
- Traceable – Cannot be broken into smaller requirement
- Viable – Statement for requirement must be measurable or tangible
- Necessary – Must be ready to meet the systems requirement.
- Implementation free – Does not specify how the function can be implemented but defines function provided by the system
(Slide3, URL 4,2017)
2.The scenario in projects are quite uncertain because of that we need a good specific scope statement so that we can identify the requirement by looking at the big picture. Some of the Problem that we may face as follows:
- Language problem- Lacking the clarity and ambiguity in the statement of requirement.
- Squeezing solution into the problem- A statement of requirement strictly speaking must have all the attributes as mentioned above in response to question 1. Squeezing solution into the problem will lead to additional suggestion and scope creep.
- GIGO for validation – GIGO model is also known as garbage in and garbage out state that valid input/ requirement should be introduced in the project. Bringing in unnecessary requirement may lead to scope creep.
- Lack of knowledge – Having improper knowledge on how to collect requirement can often lead to unnecessary time and cost.
- Bad Assumption – Sometimes you don’t have enough to state the requirement this error cannot be eliminated but can be reduced to a certain extent (P.3 URL 2,2017)
3. URL No.
Let me know your views,
In the comment below.
I am your friendly PM!