Skip to main content

Tag: Business Analysis

Disassembling Your Cube

Most of us in Information Technology have seen the movie OfficeSpace. It’s funny because we can relate to the situations that the main character, Peter, faced. I’m sure that many of us have experienced a “Did you get the memo?” situation but I question how many of us business analysts have disassembled our cube wall? In one scene, Peter disassembles his cube wall to connect with the outside world, and I’m suggesting that as BAs, we do the same thing. Now before you all take out your cordless drills and start physically disassembling your cubes, I’m speaking metaphorically. We need to break down the walls around us and understand the business that is looking for solutions.

Break Down the Wall

Many of us who practice business analysis sit within and report up through the IT environment. We may even have a title indicative of that such as Business Systems Analyst. But just because we are in IT, we need to stop constraining ourselves with IT thinking and understand what it is that our business does and how their processes work. In this age of telecommuting, multi-tasking, conference calls, and webinars, when was the last time that you actually sat with a business person as they performed their job to truly understand what it was that they did, and why they did it that way? Get out of that cube, get into the business, and learn what your business does. Better yet – see if you can learn how to do it and you try and do the work. This may be more challenging than you think; we often think that someone else’s job is simpler than our own. For instance, you may be studying an easier way for a business user to produce a certain report. When you perform the steps that they tell you, you might get completely frustrated switching between three to four different computer systems, writing down information from one to enter into another, etc. By doing so, you experience the same frustrations that they do, and you will quickly start to think of a better way to do it. While not everyone can perform the work that they are analyzing (say, a BA designing flight controls systems for a military jet doesn’t get to fly the jet – but boy, wouldn’t that be fun!), if you are able to do the work it gives you great insight to the troubles that operators face daily. You start to see the world outside your cube, looking in at IT.

Looking at your profession from the outside is not easy. Be prepared to see things that you do not like, such as disjointed ways for users to interact with the software that your organization puts out. One example; most of us probably use Microsoft Office. This office suite of tools tries to standardize commands as much as possible between Word, Excel, and Powerpoint. Pressing CTRL+F in Word (or COMMAND+F for us Mac users) initiates a search, same as the other Office products. Now consider all the other applications that you use. Is CTRL+F the same in all? I can name a text editor that uses F3 as the search, another program that has no hot key for a search and in which I have to click a button. And that’s just off the top of my head. Does your organization roll-out different applications from different product portfolios that have the design of Office’s parallel commands? Do your accounting applications search in the same way that MS Office does? How about your other applications? By getting outside of your cube and looking in from the outside, you will increase your familiarity with the area that you support. The end result is that you will be able to see a lot more of the world by getting out into it than just looking at it from within your cube.

Don’t Just Accept the Solution

By getting into the outside world, you start to see how the business operates and can start seeing solutions that you didn’t previously know existed. Users may not tell you everything because they are smart and figure out ways to get things done either inside or outside the system (or problem area). What they may see within their span of control as a solution may be completely valid. Based on everything they know, they are requesting a change in the process, but what they are really doing is proposing a solution. It’s your job to get out into the business to uncover the problem instead of just accepting their solution.

Consider this; you, as a BA, have a request from the business to create an Excel-based report from Application A. In your cube, you do your job as a BA and ask what the business need is for this new style of the report. The answer is that the business needs to input this report into an Excel spreadsheet and they cannot do this with the current MS Word-based report. Requirement captured, right? Almost! If you had been outside your cube and in the business, you would have seen users outputting the Word report from Application A and manually entering the data from the report into an Excel spreadsheet in Application B. If your requirement was to create the Excel report, it would have made the key-entry situation easier, but you still have a manual process in place (export from one system and input to another). By getting out of your cube and into the business, you would have seen that the real problem was that the business’s process required getting data from Application A to Application B, and it was not the report format. Merely accepting the requirement at face value may have saved the business a little time, but in the long run, understanding the business problem by seeing it in action would have resulted in saving a lot more time, and would have been a better solution.

Partner with the Business

Because we are so comfortable in our cubes, we tend to stay there. Yeah, we do have nice chairs but we can’t sit in them all the time. We have to get out into the business areas that we support and get them to trust us. Trust us to the point that they know that we really are there to help; to help uncover ways to improve their processes, and to help make their lives easier.

If you can show the business people that you are not just there to “take their order” as I’m fond of saying (like a waiter/waitress at a restaurant), they will become your trusted partner. But, you have to show them that you can bring something to the table. To do this will require that you understand their problems and bring a solution that shows you understand. If all you do is write down what they request, you provide no additional value. They received what they asked for, and they will wonder why you are even involved in the process in the first place.

Consider the difference from their viewpoint; they may be asking for that new report, but you find a better way to fix their business problem and make their jobs more efficient. Now they will see you as the change agent and the person who understands the problems that they face. They will start to contact you instead of their normal channels because they have seen that you were the one who sought to understand their problem and that you solved it. Instead of just the solution that you delivered on the first project, they may well start to contact you and suggest other fixes that you could make. The business has seen that you, as the BA, are the one that solved the problem on the original project, so now you are a trusted partner. While not all of the changes that they suggest will be something that you can make (or even have the budget for), they are problem areas that the business experiences day in and day out. They can be logged as future projects, or if in an agile development world, onto the project backlog.

So go ahead and break down those walls around you, and not by disassembling your cube. And while I welcome e-mails, I don’t want to see any in my inbox from your management saying that I told you to take apart your cubes. Remember, I was speaking metaphorically.

Don’t forget to leave your comments below


Paul Mulvey is a Lead Business Systems Analyst at UPS. He has just completed creation of a BA Certification program within UPS and is sitting for the CBAP exam in March. He can be reached at [email protected].

Beyond Requirements Analysis – Enterprise Analysis

“What do your Business Analysts do?”

“They develop and manage project requirements, of course. What else would they do?”

What else indeed!

The BA Body of Knowledge (BABOK®) defines what a professional BA should know and do. Much of it is focused on requirements work – but not all. One of the knowledge areas that takes the BA beyond requirements work is “Enterprise Analysis.”

Enterprise Analysis (EA) encompasses those activities that the job title “Business Analyst” actually points toward: analyzing business processes. The majority of these activities is outside of projects, and in fact, put the BA into the position of recommending and justifying projects.

Enterprise Analysis

Analyzing business processes is indeed a big part of what we do during Requirements Analysis. But that is not the only context where this analysis should be done, and in fact, it is not the most valuable time to do it. In the Enterprise Analysis knowledge area, the BABOK identifies several other contexts in which such analysis should be done.

Activity: Creating and Maintaining the Business Architecture

As the name of this activity implies, “Creating and Maintaining the Business Architecture” is an on-going activity that has as its focus the entire enterprise. The “Business Architecture” is a model of all the business processes that are used throughout the enterprise. It shows how they work and relate to each other.

The net result of this is an understanding that most organizations lack, of how all their moving parts mesh with each other. This broad understanding of the enterprise’s processes becomes the foundation for all of the other responsibilities of the BA. But its bigger value comes in providing every member of the organization with a clear understanding of how his or her department and individual job fits into the bigger picture

Recommending and Justifying Projects

The bulk of the activities described in the Enterprise Analysis knowledge area center around proposing and justifying projects. These are activities that occur in some form or other in any organization. But with the BA’s involvement, they can provide much more value and ensure the organization’s resources are spent on the most valuable projects.

Activity: Conducting Feasibility Studies

Projects are created to solve a problem or to take advantage of an opportunity. It is rare for there to be only one available solution to a problem or opportunity, so part of project initiation involves exploring the alternatives. The BA can provide a valuable service by calling upon his or her understanding of the Business Architecture to analyze the feasibility of a variety of options.

Activity: Determining Project Scope

Scope definition should not be the first step in requirements development; it should be done during the project proposal process. How can the decision-maker(s) approve or disapprove a project without a clear understanding of its boundaries?

Activity: Preparing the Business Case

The business case is the logical argument for embarking on a project. It consists of contrasting the status quo (current situation) with the various options for addressing the problem or opportunity at hand and recommending the most appropriate option. In most cases, these options are being contrasted in terms of money (e.g., “If we spend $x on this project, it will result in $y increased revenue per year”).

Activity: Conducting the Initial Risk Assessment

An important piece of information that the decision-makers need is an understanding of the risks involved in a project. Clearly, you cannot do a complete risk-planning workshop before the project has been initiated (that is part of the Project Planning process). But an initial survey of the project risks can provide the decision-makers with key information.

Activity: Preparing the Decision Package

The BA has no authority to approve or disapprove any project. The people who do have that authority rarely have the time that is necessary to do the requisite research. So, the BA’s role in the decision-making process is to do all of the necessary research, and compile it into a form the decision-makers can use.

Activity: Selecting and Prioritizing Projects

After a project has been approved, it should not be a foregone conclusion that it will begin immediately. Projects must be prioritized against each other so the organization’s resources can be deployed in the most appropriate way. Again, the BA is not the decision-maker, but provides the necessary analysis to the decision-makers.

Project Work beyond Requirements

The last three activities that the BABOK includes under the “Enterprise Analysis” knowledge area are project-related activities that go beyond Requirements Analysis. They continue the theme of Enterprise Analysis by maintaining a broad organizational view of the project.

Activity: Launching New Projects

Here, the BA works with the appropriate people in the organization to ensure that the necessary resources, including the right project manager, are committed to the project. The BA’s unique role in these activities is to focus on the bigger picture of why the project was approved and how it fits into the bigger organizational context. This ensures that the intent of the decision-makers is honored as the project is framed and kicked off.

Activity: Managing Projects for Value

In this activity, the BA works closely with the project manager to ensure the project is tracking toward providing the value that was promised in the business case (above). The BA helps the project manager keep the project’s value proposition on track. And if the assumptions on which the project was approved turn out to be false, the BA can help the decision-makers determine their best response.

Activity: Tracking Project Benefits

In this last activity, the BA closes the loop on the business case (above). The business case proposed making certain investments in order to accrue certain benefits. After the project is over, the actual investments are known, and the actual benefits can be measured. At some appropriate time after deployment, the BA should report back to the decision-makers about how the results of the project compare with the business case. This discussion process will help the organization make better decisions in the future.

Expanding Your Value as a BA

Requirements Analysis is an important way for the BA to provide value to his or her organization. By adding Enterprise Analysis, the BA can dramatically increase his or her value by ensuring that every project fits well into the bigger picture and provides the best possible result to the organization.

Don’t forget to leave your comments below


Alan S. Koch, PMP is a speaker and writer on effective Project Management Methods. He is a certified Project Management Professional and President of ASK Process, Inc, a training and consulting company that helps companies to improve the return on their software investment by focusing on the quality of both their software products and the processes they use to develop them.

Mr. Koch’s 29 years in software development include:14 years designing, developing and maintaining software; five plus years in Quality Assurance (including establishing and managing a QA department); eight years in Software Process Improvement and 10 years in management

Mr. Koch was with the Software Engineering Institute (SEI) at Carnegie Mellon University (CMU) for 13 years where he became familiar with the Capability Maturity Model (CMM), earned the authorization to teach the Personal Software Process (PSP) and worked with Watts Humphrey in pilot testing the Team Software Process (TSP).

For more information about Mr. Koch: http://www.ASKProcess.com/experience.html.

This article was originally published in Global Knowledge’s Business Brief newsletter. (www.globalknowledge.com)

Copyright © Global Knowledge Training LLC. All rights reserved

Pro Sports and Business Analysis Come Together

Let me share a little about me. I love my family, the business analysis profession, professional sports, Rocky Balboa, and Bruce Springsteen. When my loves blend I couldn’t be happier! It happened a few weeks ago when the Dallas Cowboys unveiled their new $1 Billion; yes that’s a “B”, stadium. Pro sports and business analysis came together for me. Let me explain.

prosports1Jerry Jones, the owner of the Dallas Cowboys, who I do not love since I am a NY Giants fan, had a pet feature for this stadium…sixty yard long, high definition screens that are 90 feet above the field and run along the side lines.

Man, and I thought my 47″ HDTV was cool.

Prior to having the screens constructed the Cowboys allegedly showed the specifications to the NFL, National Football League, and obtained sign-off to move forward. The screens were built and installed. Although I have not been to the stadium they look really cool.

The hype around the screens was all positive until the third quarter of the first pre-season game. The opposing team’s punter kicked a ball right into the screen causing a do-over. Just like that the stadium “project” went from a success to a big concern in some critical stakeholders’ eyes. The NFL is now reviewing the situation, the height of the screens, the impact on games, etc. A decision will be made soon if the screens need to be moved, who has to pay for the work and when they can safely be moved, if necessary.

So, what does sign-off really mean? Does sign-off of a requirements specification mean anything if the end solution does not meet the needs of key stakeholders? In the case of the Cowboys, they’ll most likely argue to the NFL that they received the necessary approval on the plans. This may result in the NFL picking up the tab for the move of the screens, but there is still an impact to everyone involved. In my opinion only having this type of sign-off is worthless. If you stop there, all it does is allow parties to place blame on other parties. Why do you think so many customers are skeptical about signing off on requirements documents?

Now, let’s talk about the right way to obtain sign-off. The Indianapolis Colts, who I am impartial to because they play in a different division than the NY Giants, were planning on a similar screen set-up when they were building their new stadium. To verify the screens would not impede the game, they built a “prototype” of the screens and had their punter try to hit the mock screens. He was very successful in hitting them which resulted in the team changing the design and placement of the screens due to this simulation. Now that’s what I call sign-off you can be confident about.

In addition to my disliking the Cowboys, the moral of the story is you need to make sure you obtain the right level of approval throughout a project. At different stages of a project you need to take the opportunity to ensure you are headed in the right direction. I think the Cowboys did the right thing about getting the plans approved. The issue was they stopped there. By simulating the scenario with their punter, the Indianapolis Colts were able to obtain the right level of approval.

I’d love to hear your sign-off stories, good and bad!

Have fun simulating,

Kupe

Don’t forget to leave your comments below


Jonathan “Kupe” Kupersmith is Director of Client Solutions, B2T Training and has over 12 years of business analysis experience. He has served as the lead Business Analyst and Project Manager on projects in various industries. He serves as a mentor for business analysis professionals and is a Certified Business Analysis Professional (CBAP) through the IIBA and is BA Certified through B2T Training. Kupe is a connector and has a goal in life to meet everyone! Contact Kupe at [email protected].

The Business Analysis Center of Excellence; A Vital Strategic Asset

The Business Climate

In the twenty-first century, business processes have become more complex; i.e., more interconnected, interdependent, and interrelated than ever before. Businesses today are rejecting traditional organizational structures to create complex communities comprised of alliances with strategic suppliers, outsourcing vendors, networks of customers, and partnerships with key political groups, regulatory entities, and even competitors. Through these alliances, organizations are addressing the pressures of unprecedented change, global competition, time-to-market compression, rapidly changing technologies, and increasing complexity at every turn. Since business systems are significantly more complex than ever, projects that implement new business systems are also more complex. To reap the rewards of significant, large-scale business transformation initiatives, designed to not only keep organizations in the game but make them a major player, we must be able to manage complex business transformation projects.

Why Now?

Centers of excellence are emerging as a vital strategic asset to serve as the primary vehicle for managing complex change initiatives. A center of excellence is a team of people that is established to promote collaboration and the application of best practices (Geiger, Jonathan G. Intelligent Solutions: Establishing a Center of Excellence. BIReview: March 20, 2007. http://www.bireview.com/article.cfm?articleid=222). Centers of excellence exist to bring about an enterprise focus to many business issues, e.g., data integration, project management, enterprise architecture, business and IT optimization, and enterprise-wide access to information. The concept of centers of excellence (COE) is quickly maturing in twenty-first century organizations because of the need to collaboratively determine solutions to complex business issues. Project management offices (PMO), a type of COE, proliferated in the 1990s as a centralized approach to managing projects, in response to the challenges associated with complex projects in an environment with low levels of project management maturity and governance. Industry leaders are effectively using various types of COEs, and BACOEs are among them.

A Slippery Slope

We are fortunate to have learned from the implementations of PMOs. The Project Management Institute’s research program studied PMOs in an attempt to publish a PMO standard. However, they were unable to do so, because they found out that there is no real standard practice for PMOs (Hobbs, 2007 PMI PMO Research Report). Here is what they discovered:

  • PMOs have been prevalent since the mid 1990s; yet, most have been in existence for two years or less
  • Only 50% of PMOs are seen as relevant and adding value
  • Most operate autonomously from other PMOs
  • Most organizations have trouble finding the right “fit” culturally and politically
  • Closure and restructuring happens frequently
  • Implementation time takes six months to two years; yet, there is a short time to demonstrate value before being closed or restructured; many are closed or restructured before they are completely implemented
  • There is a wide variability in the percentage of projects within the mandate of the PMO
  • Either all or none of the project managers are located within the PMO
  • Most PMOs have a very small staff due to the key issue of cost

Conclusions: it is a difficult endeavor to establish a center of excellence that is accepted and supported by the organization. A considerable amount of due diligence is needed to make sure the new center is successful.

It’s About Value

For a BACOE to be viewed as adding value, one of the critical functions is benefits management, a continuous process of identifying new opportunities, envisioning results, implementing, checking intermediate results, and dynamically adjusting the path leading from investments to business results. Therefore, the role of the high-value BACOE is multidimensional, including: (1) provide thought leadership for all initiatives to confirm that the organization’s business analysis standards are maintained and adhered to, (2) conduct feasibility studies and prepare business cases for proposed new projects, (3) participate in all strategic initiatives by providing expert business analysis resources, and (4) conduct benefits management to ensure strategic change initiatives provide the value that was expected. The BACOE is staffed with business/technology experts, who can act as a central point of contact to facilitate collaboration among the lines of business and the IT groups.

Implementation Considerations

Integration

Although the BACOE is by definition business focused, it is of paramount importance for successful centers to operate in an environment where business operations and IT are aligned and in synch. In addition, the disciplines of project management, software design and development, and business analysis must be integrated. Therefore, to achieve a balanced perspective, it is important to involve business operations, IT, PMO representatives and project managers, and representatives from the project governance group in the design of the BACOE. Indeed, your organization may already have one or more centers of excellence. If that is the case, consideration should be made to combining them into one centralized center focused on program and project excellence. The goal is for a cross-functional team of experts (business visionary, technology expert, project manager and business analyst) to address the full solution life cycle from business case development to continuous improvement and support of the solution for all major projects.

Mission

Understanding the business drivers behind establishing the BACOE is of paramount importance. The motive behind establishing the center must be unambiguous, since it will serve as the foundation to establish the purpose, objectives, scope, and functions of the center. The desire to set up a BACOE might have originated in IT, because of the number of strategic, mission-critical IT projects impacting the whole organization, or in a particular business area that is experiencing a significant level of change. Whatever the genesis, strive to place the center so that it serves the entire enterprise, not just IT or a particular business area.

Placement

One of the biggest challenges for the BACOE is to bridge the gap that divides business and IT. To do so, the BACOE must deliver multidimensional services to the many diverse groups. Regardless of whether there is one COE, or several more narrowly focused models, the BACOE organization should be centralized. “Organizations with centralized COEs have better consistency and coordination, leading directly to less duplication of effort. These organizations configure and develop their IT systems by business processes rather than by business unit, leading to more efficient and more streamlined systems operations” (2006 USAG/SAP Best Practices Survey: Centers of Excellence: Optimize Your Business and IT Value. SAP America Inc. February 16, 2007). Best-in-class BACOEs evaluate the impact of proposed changes on all areas of the business and effectively allocate resources and support services according to business priorities.

Positioning is equated with authority in organizational structures; the higher the placement, the more autonomy, authority and responsibility is likely to be bestowed on the center. Therefore, positioning the center at the highest level possible provides the “measure of autonomy necessary to extend the authority across the organization, while substantiating the value and importance the function has in the eyes of executive management” (Bolles, Dennis PMP. Building Project Management Centers of Excellence. New York, NY: American Management Association. 2002). In the absence of high-level positioning, the success and impact of the center will likely be significantly diminished.

One Size does not fit All

The “perfect fit” takes several elements into consideration:

  • The maturity of the organization’s processes and capabilities
  • The size of the organization
  • The diversity of the products and services

bacentreexcel_1

What is the Focus?

The current state of the organization must be taken into consideration, as in the effectiveness of the strategic planning and project portfolio management practices, the business performance management processes and strategies, the maturity of IT architecture, development and support processes, and the strength of the business focus across the enterprise. Clearly, organizations with more mature practices achieve higher levels of value from their COEs. Organizations can absorb a limited amount of concurrent change, while maintaining productivity levels, at any given time. Therefore, a gradual approach to implementing the BACOE is recommended. One option is to adopt a three-phased approach moving across the BACOE maturity continuum from a project-focused structure to a strategic organizational model.

Where to Start?

Based on the history of best practices for setting up centers of excellence, there is a proven implementation approach, including the steps listed below.

  1. Visioning and concept definition
  2. Assessing the organizational knowledge, skills, maturity, and mastery of business analysis practices
  3. Establishing BACOE implementation plans
  4. Finalizing plans and creating action teams to develop and implement the infrastructure for the center

Visioning

It is important to create a vision for the new center. Create a preliminary vision and mission statement for the center, and develop the concept in enough detail to prepare a business case for establishing the center. Vet the proposal with key stakeholders and secure approval to conduct the assessment of business analysis practices and plan for the implementation of the center.

During meetings with the key stakeholders, secure buy-in and support for the concept. Large-scale organizational change of this nature typically involves restructurings, cultural transformation, new technologies, and forging new partnerships. Handling change can well mean the difference between success and failure of the effort. Techniques to consider during the visioning phase include (Kotter, John P. (2002) Getting to the Heart of How to Make Change Happen. Boston, MA: Harvard Business):

  • Executive sponsorship – A center of excellence cannot exist successfully without an executive sponsor. Build a trusting, collaborative relationship with the sponsor, seeking mentoring and coaching at every turn.
  • Political management strategy – Conduct an analysis of key stakeholders to determine those who can influence the center, and whether they feel positively or negatively about the center. Identify the goals of the key stakeholders. Assess the political environment. Define problems, solutions, and action plans to take advantage of positive influences, and to neutralize negative ones.
  • A sense of urgency – Work with stakeholder groups to reduce complacency, fear, and anger over the change, and to increase their sense of urgency.
  • The guiding team – Build a team of supporters who have the credibility, skills, connections, reputations, and formal authority to provide the necessary leadership to help shape the BACOE.
  • The vision – Use the guiding team to develop a clear, simple, compelling vision for the BACOE, and set of strategies to achieve the vision.
  • Communication for buy-in – Execute a simple, straight-forward communication plan using forceful and convincing messages sent through many channels. Use the guiding team to promote the vision whenever possible.
  • Empowerment for action – Use the guiding team to remove barriers to change, including disempowering management styles, antiquated business processes, and inadequate information.
  • Short-term wins – Wins create enthusiasm and momentum. Plan the implementation to achieve early successes.
  • Dependency management – The success of the center is likely dependent on coordination with other groups in the organization. Assign someone from your core team as the dependency owner, to liaise with each dependent group. A best practice is for dependency owners to attend team meetings of the dependent group, so as to demonstrate the importance of the relationship and to solicit feedback and recommendations for improvements.

Organizational Readiness

The purpose of the organizational readiness assessment is to determine organizational expectations for the BACOE and to gauge the cultural readiness for the change. Form a small assessment team to determine key challenges, gaps and issues that should be addressed immediately. The ideal assessment solution is to conduct a formal organizational maturity assessment. However, a less formal assessment may suffice at this point.

Planning

Develop a BACOE Business Plan and Charter that describes the center in detail. Planning considerations include the elements listed in the table below. It is helpful to draft the plan and charter, and then conduct a BACOE kickoff workshop where they are viewed, refined and approved.

Planning Considerations
Description of Kick-off Workshop Agenda Items
Strategic Alignment, Vision and Mission Present the case for the BACOE, and reference the business case for more detailed information about cost versus benefits of the center.
Assessment Results Include or reference the results of the assessments that were conducted:

  • Maturity of the business analysis practices
  • Summary of the skill assessments
  • Recommendations, including training and professional development of BAs and improvement of business analysis practice standards
Scope Describe the scope of responsibilities of the BACOE, including:

  • The professional disciplines guided by the center, (i.e., PM and BA, just BA)
  • The functions the center will perform
  • The processes the center will standardize, monitor and continuously improve
  • The metrics that will be tracked to determine the success of the center
Authority Centers of excellence can be purely advisory, or they can have the authority to own and direct business processes. In practice, centers typically are advisory in some areas, and decision-makers in others. Remember, the organizational placement should be commensurate upon the authority and role of the center. When describing the authority of the COE, include the governance structure, i.e., who or what group the COE will report to for guidance and approval of activities.
Services A center of excellence is almost always a resource center, developing and maintaining information on best practices and lessons learned, and is often a resource assigning business analysts to projects. Document the proposed role:

  • Materials to be provided, e.g., reference articles, templates, job aids, tools, procedures, methods, practices
  • Services, e.g., business case development, portfolio management team support, consulting, mentoring, standards development, quality reviews, workshop facilitators, and providing business analysis resources to project teams
Organization Describe the BACOE team structure, management, and operations including:

  • Positions and their roles, responsibilities, and knowledge and skill requirements
  • Reporting relationships
  • Linkages to other organizational entities
Budget and Staffing Levels At a high level, describe the proposed budget, including facilities, tools and technology, and staffing ramp up plans.
Implementation Approach Document formation of initial working groups to begin to build the foundational elements of the center. In addition, describe the organizational placement of the center, and the focus initially: (i.e., project centric, enterprise focus, or strategic focus).

Launch

After the workshop session, finalize the BACOE Charter and Business Plan, and launch the center. Form working groups to develop business analysis practice standards, provide for education, training, mentoring and consulting support, and secure the needed facilities, tools, and supplies.

Final Words

Establishing centers of excellence is difficult, because it destabilizes the sense of balance and power within the organization. Ambiguities arise when all stakeholders are adjusting to the new model. These may manifest themselves as resistance to change, and can pose a risk to a successful implementation. Therefore, coordinate and communicate about how the center will affect roles and responsibilities accompanies the implementation of the center. Do not underestimate the challenges that you will encounter. Pay close attention to organizational change management strategies and use them liberally.

Value to the Organization

To establish BACOE to last, demonstrate the value the center brings to the organization. Develop measures of success and report progress to executives to demonstrate the value added to the organization because of the BACOE. Typical measures of success include:

  • Project cost overrun reduction – Quantify the project time and cost overruns prior to the implementation of the BACOE, and for those projects that are supported by the BACOE. If a baseline measurement is not available in your organization, use industry standard benchmarks as a comparison. Other measures might be improvements to team member morale and reduction in project staff turnover. Be sure to include opportunity costs caused by the delayed implementation of the new solution.
  • Project time and cost savings – Track the number of requirements defects discovered during testing and after the solution is in production prior to the implementation of the BACOE, and for those projects that are supported by the BACOE. Quantify the value in terms of reduced re-work costs and improved customer satisfaction.
  • Project portfolio value – Prepare reports for the executive team that provide the investment costs and expected value of the portfolio of projects; report actual value new solutions add to the organization as compared to the expected value predicted in the business case.

Great Teams…You Need One!

When staffing the BACOE, establish a small but mighty core team dedicated full-time to the center, co-located, highly trained, and multi-skilled. Do not over staff the center, as the cost will seem prohibitive. Augment the core team’s efforts by bringing in subject matter experts and forming sub-teams as needed. Select team members not only because of their knowledge and skills, but also because they are passionate and love to work in a challenging, collaborative environment. Develop team-leadership skills and dedicate efforts to transitioning your group into a high-performing team with common values, beliefs, and a cultural foundation upon which to flourish.

Don’t forget to leave your comments below


Kathleen (Kitty) Hass is principle consultant, K. Hass and Associates, specializing in strategy execution, business analysis and project management disciplines. Ms. Hass is a prominent presenter at industry conferences, author and lecturer. Expertise includes implementing a mature BA Practice, implementing PMOs, BACOEs, and portfolio management, facilitating IT strategic planning, leading software-intensive projects, executive coaching, building and leading strategic project teams, and managing complex programs. Her company provides high-value facilitation and consulting services to agile and traditional organizations. Ms. Hass has provided professional services to Federal agencies, the intelligence community, and Fortune 500 companies. Professional certification include: SEI CMM appraiser, Baldrige National Quality Program examiner, Zenger-Miller facilitator, and Project Management Professional. She is Director at Large for IIBA and a member of the BABOK committee serving as lead author of the Enterprise Analysis chapter. She authored numerous white papers and articles on leading edge PM/BA practices, in 2008 published the Business Analysis Essential Library Series; Managing Project Complexity – A New Model, and in 2009 contributed to The 77 Deadly Sins of Project Management. Ms. Hass can be reache at [email protected]

This article was originally published June 2009 in ModernAnalyst.com www.modernanalyst.com

Estimating the Business Analysis Phase of a Project. Is it Even Possible?

Years ago I worked on a large effort to reengineer a distribution center for a major retailer. We provided an estimate for both the business analysis work and for the entire project, which would involve the organization’s first use of Electronic Data Interchange (EDI), new business processes, many software changes, and the purchase of new barcode scanners. The business analysis effort took far longer than we anticipated, and at the end of it we refined our estimate for the total project. When we reported the new estimate to the president of the company, he literally pounded his fist on the table and asked, “How did we get to this point? Why didn’t we know sooner? You’ve already spent all this time on the project and what do we have to show for it? Nothing! Absolutely nothing!”

I have always thought of business analysis as the most ambiguous and the most fun of the project phases (by phase I mean phase, increment, or iteration). However, for many years it was my least favorite phase to estimate. I felt like I was guessing, simply pulling numbers out of the air. No wonder we were so far off.

Estimating the business analysis phase(s) is not easy. It is not hard, but it takes a willingness to think about exactly what work will be produced, and many business analysts do not have the patience. So for those of you who do not have the “stomach” to spend the required time to estimate business analysis, here are some tips.

  1. Break the effort into manageable pieces. We can estimate a whole lot better when our business analysis phase(s) are small.
  2. As we progressively elaborate our requirements, we can progressively elaborate our estimates. We go from Rough Order of Magnitude (ROM) to budgetary (deliverables identified) to definitive (requirements defined to a low level of detail).
  3. It is helpful to use a variety of estimating techniques. When we’re first asked how long business analysis will take, we really cannot be precise. We use analogous estimating, or experience with a previous project. If we have good history, we might be able to use parametric estimates. For example, if we know that it takes two hours to model a business process and we have five processes to model, it will take ten hours to model business processes. Providing detail on each of these techniques is beyond the scope of this blog, however.
  4. I have found it helpful to brainstorm with the people who are actually going to do the work. They usually have a more realistic idea of what needs to be done and how long it will take. I also like yellow sticky notes, since they can be easily added, taken away, and moved.
  5. But here’s the real key to estimating business analysis. Identify all the deliverables (work products, artifacts) you will produce during the business analysis effort. It is essential to first identify the approach you’re going to take, whether plan-or change-driven (Waterfall/Agile). It is also helpful to use the BABOK knowledge areas to identify which work products will be completed. During the course of an Elicitation event, for example, we might send out an agenda (one work product), update our traceability matrix (another deliverable), create an “as-is” process model (another deliverable), and update our list of issues (yet another deliverable). Next we think of the tasks needed to complete each work product, and finally how many hours the task will take.

Of course the real, real key is having the courage to communicate bad news. Which brings me back to the president pounding his fist. What I should have done was reported the plan vs. actual of the business analysis effort regularly, rather than surprising him after months of work.

What a lesson learned!


Elizabeth Larson, PMP, CBAP, CEO and Co-Principal of Watermark Learning (www.watermarklearning.com) has over 25 years of experience in business, project management, requirements analysis, business analysis and leadership. She has presented workshops, seminars, and presentations since 1996 to thousands of participants on three different continents. Elizabeth’s speaking history includes, PMI North American, EMEA, and Asia-Pacific Global Congresses, various chapters of PMI, and ProjectWorld and Business Analyst World. Elizabeth was the lead contributor to the PMBOK® Guide – Fourth Edition in the new Collect Requirements Section 5.1 and to the BABOK® Guide – 2.0 Chapter on Business Analysis Planning and Monitoring. Elizabeth has co-authored the CBAP Certification Study Guide and the Practitioner’s Guide to Requirements Planning, as well as industry articles that have been published worldwide. She can be reached at [email protected]