It's difficult to agree with one argument I hear quite often from peers. The wording usually varies like
- What are the requirements?
- We did not receive requirements of proper details.
- Cannot proceed further without requirements.
As per experience, such questions are signals of low team engagement into the product or process. In real life, definitions in Project Charter are quite good baseline to go ahead with development without dependency on additional requirements.
Statements in Project Charter is enough to get vision on product features of greater impact
- Infrastructure (either terminals, or server side)
- Industry (automotive, financial, publishing, insurance, medical, ...)
- Functionality (either reporting, or data input, or extract and its modifications, ...)
System properly designed should easily accommodate usual request of changing screen flow, adding attributes and modifying entity relationships. This is the only real requirement.
No comments:
Post a Comment