Once you understand current practices, the next step is to determine the goals you want to achieve. You might want to establish a community of practice, increase business analysis awareness within your organization, standardize practices or build a business analysis center of excellence. All of these are worthy goals, but each is going to require a slightly different focus and approach. Remember, goals are the objectives that management is going to hold you accountable for achieving. Do your best to define goals that are specific and quantifiable; this will make it easier to demonstrate success throughout the project. Taking time to define project goals lays the groundwork needed to build a roadmap. In addition, well-understood goals set the tone for your project by establishing scope and communicating expectations to leadership. All are needed for successful project execution.

Build a Roadmap for Improvement

Whereas goals provide a strategic view of what you want to achieve, a roadmap describes the path that you are going to take. Roadmaps are excellent tools for detailing, at a tactical level, the activities that need to be accomplished in order to achieve your goals. The roadmap is often the most powerful and frequently used communication tool for your project, so spend the time necessary to ensure it is clear and accurate. The activities on your roadmap should all be roughly at the same level of abstraction, and it is a best practice to show dependency so that an order of execution is communicated. Examples of activities can include: research business analysis tools, develop training material, or begin pilot projects. Each action is self-contained and easily understood. When you are building your roadmap, remember that this is not a project plan. Activities do not need to be broken down to tasks or assigned a number of days or resources. Instead, your roadmap should describe a path of activities that need to be followed in order to achieve the goals that have been identified. A time scale can be included, but think in months instead of days.

Prove the Value of Business Analysis

Projects only get the resources and support they need when they are backed by management. Unfortunately, selling a project upwards can be difficult. Even though you know that improving business analysis competency will lead to higher project success rates, you still need to prove it to management. I have found that the best way to build your case and win over support from the top offices is to frame your project in terms that management understands: costs and benefits. A common vehicle for delivering this information is the business case. By building a business case that ties improving business analysis competency back to real project costs, software defects, or other tangible metrics that your organization uses to judge success, you can demonstrate how business analysis competency benefits the bottom-line. This is also a great time to look at the goals that you have identified and tie them back to the goals of your organization. Linking business analysis competency improvement back to the greater goals of your organization strengthens your business case and demonstrates how good business analysis practices will enable management to hit their own targets, winning over support and building buy-in.

Recommendations

Every organization should build a plan before beginning to improve their business analysis competency. Consider using a time-boxed discovery and planning effort to flush out the details of a plan and build support for the project. Taking the time at the beginning of your improvement effort to investigate existing practices, establish goals, and document a roadmap for the future will set your project up for success. In addition, building a business case that is based on metrics and aligned with the overall goals of your company will demonstrate reasons for and the importance of improving business analysis practices. Having a plan in place from the beginning not only enables success, but serves as a foundation for achieving the types of improvements that make good organizations great.

Don't forget to leave your comments below.