BI Solution Planning: Scooter's
Lemonade Stand
For
this assignment, we will be outlining the steps necessary for planning to
implement a business intelligence solution for Scooter's Lemonade Stand. Ultimately, we need to take a look at the entire project, break it down into smaller pieces, and then plan as many pieces as possible before beginning development. This will allow us to estimate the time, the cost, as well as plan the best solution for the customers needs.
The
first step in the planning stage is the interview process, in which we attempt
to gather as much information as we can about the lemonade stand's current data
storage practices, their expectations, and their needs. This will allow us to
more accurately estimate the scope, cost, and time of the project.
The Client: Scooter's Lemonade stand has been in business
for three summers and has only one location on the sidewalk in front of Scooter's
Mom's house. He currently has three products that he sells, regular lemonade,
strawberry lemonade, and sugar free lemonade. Scooter has been keeping his
sales records in a spiral notebook.
After interviewing Scooter about his business intelligence
needs, he has clearly outlined what he wants:
1. One
place to store data to improve on current organization practices.
2. The
ability to easily import sales data.
3. The
ability to report on the sales data to improve on current decision making
processes.
On the flip side, he also outline what he doesn't want from
his BI solution:
1. The
solution must not be expensive.
2. The
solution must not be complicated
3. The
finalization date must not be during summer.
Now that we have all of the client's requirements from the
interview stage, we must document this in a development plan. This document
will clearly describe the scope of the project, so that everybody is on the
same page when the project begins.
Now that we have outline the project from the big picture
perspective, we need to break it down and figure out exactly what needs to be
done to create this solution. This will allow us to estimate time and cost more
accurately.
For Scooter's solution, we need to:
1.
Create the database
2.
Create the data warehouse
3.
Create the ETL process
4.
Create cubes
5.
Create reports
6. Test
7.
Train Scooter/Create documentation.
Due to the fact that Scooter's time frame is so long, the
fact that we have a one man team will not hinder the project. As seen in the
chart below, even though each job must be completed before moving to the next,
the project will still be done in the allotted time frame.
Now that we have an idea of how long this project will take,
we need to estimate how much this will cost. The overall cost is a huge deal
for Scooter, as it is with all businesses. According to our breakdown schedule,
this project will take an estimated 36 hours to complete. Working at $30/ hr,
this works out to about $1080.
Once the time frame and cost are approved by the client, we
are able to begin logically planning out our database and data warehouse before
developing them.
Scooter has been keeping all of his sales data in a spiral
notebook. He has been keeping records of each transaction that takes place. Due
to the nature of his business, he does not keep records of his customers. A
simple database will allow him to store his information in one secure spot.
After that, we need to document how we will build the data
warehouse. While Scooter may not need one yet, since he has to input all of his
data manually, he may need one in the future. Due to the fact that the
timeframe is so wide, we are able to implement this feature.
Now, we have planned out all that we can before the actual
development begins. We have a road map for the entire project, as well as
blueprints to create our database and data warehouse.
During the development
process, it's important to log all issues that are encountered and their
resolutions in the Solution Outline. This will help avoid issues and help with
better planning on future projects.