Database Reference
In-Depth Information
This is your opportunity to listen to what the sponsor really believes he
is paying for. After you have finished listening to the sponsor, restate
everything he said as you understand it. Does he agree with your
understanding? If so, now you have a starting point for a discussion about
reality.
A more formal way to gather these requirements is through a three-step
process of elicit, confirm, and verify:
•
Elicit
: What are we going to build?
Outputs of the elicit phase are objects such as the business
requirements document.
•
Confirm
: Is this what you asked for?
A customer-signed business requirements document.
•
Verify
: Did you get what you wanted?
A customer-signed business requirements document (if a change
occurred).
Defining the Criteria for Success
Defining success criteria for any big data project will vary wildly by projects.
Many of the criteria are goal oriented, but some are more budget oriented.
Getting the details of these criteria into your business requirements
document is imperative for setting yourself up for victory.
Table 19.1
shows
an example of stating your project success criteria. A simple list such as this
allowsyoutoconcentrate onthesuccesscriteria withoutworrying aboutany
additional metadata around simply listing them out.
Table 19.2
shows an
exampleoflistingoutthebusinessobjectivesfortheprojectalongwithsome
additional metadata around stakeholders, success, and how to measure.
Both of these documents will provide valuable references as your project
progresses.
