APR 27, 2001 1:00am ET

Related Links

10 Sustainability Predictions for 2011
February 23, 2011
A Letter to Future Employees: Embrace Analytics
February 3, 2011
A Hunger for Risk
January 6, 2011

Web Seminars

How Customer Analytics Can Lower Costs and Raise Revenue
July 29, 2014
Improve Omni-channel Shopping Experience with Product Information Management
August 21, 2014

Failure to Plan is a Plan for Failure

Print
Reprints
Email

There are two adages I think of regarding planning and launching a business intelligence project. They are: "Failure to plan is a plan for failure" and "Each hour spent planning is worth two hours saved during implementation."

Implementing business intelligence applications can be straightforward—but projects can also fail. If senior management isn’t fully briefed and backing the information technology department’s plan, the project may never see the light of day. In addition, IT managers, MIS directors and chief information officers must take great care in assembling the right implementation team and selecting the right business intelligence product. So, what’s a blueprint for success? What steps can your company and department take to ensure that your business intelligence project planning and implementation come off without a hitch? Here’s a checklist for doing the job right:

  • Define the project.
  • Identify the users.
  • Develop a formal project plan.
  • Assemble the project team.
  • Assess all information and technical needs.
  • Select the software.
  • Configure the business intelligence application.
  • Deploy a support strategy.
  • Train all users.

There must be a compelling need for developing a business intelligence application within your organization. In addition, management and the business community must have a general understanding and an appreciation of the value that BI applications can provide. Without these essential ingredients, there is no project. Individuals use BI applications to access data because they have a compelling need to obtain specific information and use it to solve serious business problems. That’s why thorough planning is extremely important for getting your project off the ground and completed by the established deadline.

In fact, developing a formal project plan is critical to managing expectations and fostering understanding both within your development team and by senior management. The plan should contain the following items: business requirements, scope, deliverables, critical success factors, user acceptance criteria, tasks, timeline, roles and responsibilities. Your plan is a living document that must be updated throughout the life of the project. Your plan is a reference document which individuals can read in order to learn about the details of the project and to help manage expectations as to what will be delivered.

Goals and aspirations are rarely achieved without a plan.

Without a plan, you and your project team may wander aimlessly—hoping to complete the project in a successful manner, but not having the resources and the timeline to really do the job right. A successful BI project is one in which all of the organization’s expectations are met or exceeded. User expectations can not be managed without following a course of action and formally documenting and communicating the scope and deliverables of the project. Remember that failure to plan is a plan for failure. So, I hope these steps will aid you in planning your next business intelligence initiative. The journey of a thousand miles begins with the first step—and in this case your first step begins with proper project planning. Good luck!

The Top Questions To Keep in Mind When Planning a BI Project
  • Why does the organization need a BI application?
  • What does the organization hope to accomplish by using a BI application?
  • Are the project sponsors and key users accepting the plan?
  • Do members of the project team have the skills to make themselves—and the project—successful?
  • Does each member of the project team understand his/her role and responsibilities?
  • Has each member of the project team read the project plan?
  • Do they understand the scope of the project, user expectations and the deliverables?
  • What information will the users need?
  • Which BI applications contain the features and functionality required by the user community?
  • Does the BI application work as intended or as demonstrated by the vendor?
  • Have representatives from the user community reviewed the configured BI application?
  • Have they provided their comments?
  • Who will they contact when they have questions, comments or issues?
  • Do they know how to use the BI application to address their business questions?

Source: Jonathan Wu and Base Consulting

Get access to this article and thousands more...

All Information Management articles are archived after 7 days. REGISTER NOW for unlimited access to all recently archived articles, as well as thousands of searchable stories. Registered Members also gain access to:

  • Full access to information-management.com including all searchable archived content
  • Exclusive E-Newsletters delivering the latest headlines to your inbox
  • Access to White Papers, Web Seminars, and Blog Discussions
  • Discounts to upcoming conferences & events
  • Uninterrupted access to all sponsored content, and MORE!

Already Registered?

Advertisement

Comments (0)

Be the first to comment on this post using the section below.

Add Your Comments:
You must be registered to post a comment.
Not Registered?
You must be registered to post a comment. Click here to register.
Already registered? Log in here
Please note you must now log in with your email address and password.
Twitter
Facebook
LinkedIn
Login  |  My Account  |  White Papers  |  Web Seminars  |  Events |  Newsletters |  eBooks
FOLLOW US
Please note you must now log in with your email address and password.