Database Reference
In-Depth Information
Figure 19-1.
Down to the final step!
But, before we can begin again, we have some loose ends to tidy up. And we cannot kick off this final stage
without the approval from our client, manager, or contract holder. Let's start by getting the needed approval to
release their fancy new BI solution.
■
several subjects touched upon in this chapter are business practices that will be unique to your company
and are implemented according to how you choose to do business.
Note
The Final Approval Process
Why do you need it approved? The answer is simple. It is because you want to get paid! The final approval process
begins at the end of each cycle. Many developers are afraid to get sign-off because they are afraid someone will
always say, “We missed something.” This is all part of preparing for the next cycle, and we will save that topic for
later in this chapter.
Who gives the approval is likely whomever you have been answering to all along. It is usually a project
manager on your team and a stakeholder who is representing the client receiving the solution. This could also be
your supervisor if the BI solution is being developed for the company you work for as an employee. In this case,
the approval process is handled according to your company's guidelines.
The Sign-Off Document
In Chapter 3, you created a solution plan, and at that time you agreed to create the project. This agreement might
have come in the form of a contract or an accepted solution outline. Once the requirements have been met
within the agreement, the approval process can begin.
If the original agreement has been modified, you may need to create a final invoice. This agreement
should be handled according to how your company chooses to do business, but the goal is for the invoice to
list everything from the original agreement to any new items that were agreed upon. Add lines at the bottom
