3. Who said that? “ If you don't know how well you are doing, then you know you are not doing very well” Anonymous “ Good stuff ain’t cheap, and cheap stuff ain’t good” Hubert Green
4.
5.
6. What are requirements? Requirements are a negotiated set of measurable customer wants and needs.
7. When do you gather requirements? Initiation Executing Controlling Planning Closing Right here
8.
9.
10. Worth a thousand words ($)… Source of errors Cost to correct in $1,000
Needs emergence – There is some type of issue or problem that arises, pick your poison. Our work force is not flexible We cannot communicate in real-time Needs recognition A project emerges, maybe supported by market survey Executive support Needs articulation This is where the documentation begins Generally on the customer’s side
Challenges from the customer’s side
Requirements Define what the deliverable will look like and what it will do.
Association of Computing Machinery ’84 ATT bell labs estimates. These are relative numbers, but we can see the relationship between the catching errors early and the cost to correct errors later in a project.
Challenges noted, how did the project fare compared to others?
Bad choice, sometimes needed. Do we get paid for this effort?