Добавил:
Upload Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
Seven Steps to Mastering Busin - Barbara A. Car...docx
Скачиваний:
1
Добавлен:
01.07.2025
Размер:
3 Мб
Скачать
☆

Tips for Those Performing Both Roles

For the individual playing this dual role, the challenge is to be aware of the conflicting focus and to try to act in one role at a time. You may find you are having disagreements with yourself, and it may be helpful to have a fellow PM or BA listen to your internal debate to try to help you make decisions. Be aware that you probably have a preference for one role or the other, and you may find yourself neglecting the tasks of the role that you enjoy the least. If you prefer doing PM work, you may miss requirements. If you prefer doing BA work, you may allow the schedule to slip or forget to direct your team members. This situation is further complicated if you are also assigned to other project responsibilities (e.g., you are also the technical architect) or assigned to work on other projects. Your project schedule, budget, and product quality may be affected. Be sure to plan for the time needed to do both jobs adequately.

If you frequently find yourself in this situation in your organization, use your excellent communication skills to heighten management’s awareness regarding these conflicting roles. Make management and your team aware of your conflicting responsibilities and the challenges associated with them. Seek help in managing the schedule and help in gathering and documenting the requirements. If possible, try to minimize your involvement in other concurrent projects.

Other Business Analysis Professionals

For large projects, more than one BA may be needed. When multiple BAs are working on the same project, they need to plan the business analysis work and then divide the work appropriately. When one of the BAs is designated as the senior BA, he or she usually will decide which tasks will be assigned to each BA. BAs must work closely together during project initiation and requirements elicitation since they may be working on closely related business areas.

There are many different strategies for dividing business analysis work. Some teams delegate one BA as the data analyst, one as the process analyst, and one to gather business rules. This division allows each analyst to focus on a particular type of requirement and then cross-check their work by linking or tracing their requirements components to the others. Another delegation strategy is by high-level business process. Each BA is assigned to a high-level business process and is responsible for analyzing all of the requirements components needed for that process. Regardless of the delegation approach used, BAs should consolidate their requirements and make sure that all relationships between requirements components have been documented.

Subject Matter Experts and Users

A subject matter expert (SME) is a person who has a particular expertise needed on a project. The expertise may be on the business side (a person who understands the business needs), on the technical side (a person who can provide design ideas), or outside the organization (an external customer). The acronym SME has become popular because it can be used to describe anyone on a project who has expertise.

The role name user is also used frequently. This word refers to a person who “uses” the software under discussion. Many people prefer the role name SME to user because it sounds more positive and because it is more accurate during analysis/requirements elicitation. Be aware that although many SMEs may also be “users” of the software, many are not. A department manager may be an SME because he or she understands the business goals of the department but is not a user because he or she doesn’t actually enter any data into the software system. Alternatively, a user is not necessarily an SME. A data entry person who simply enters data on a computer screen without any knowledge of the reason for the data entry is not an expert.

As mentioned earlier, business analysis professionals must be able to use varied language when talking and writing to best communicate to the intended audience. Titles and role names of stakeholders are used inconsistently. Be sure to clarify terminology and titles when listening. Some people use the word customer to mean a person external to the organization who purchases products. Some IT people use the word customer to mean anyone inside the organization who uses IT services. A simple mistake like the confusion around this term can cause requirements elicitation to take longer than anticipated.

Business domain SMEs know about the business area being analyzed. Ideally, they are experts on the business. They are workers and managers in the business area and they are people outside of the business who have some interaction with the particular area of the business being studied. These are the people who BAs sometimes refer to as their customer; these are the people for whom the BA is trying to solve a business problem and create a solution that will make the business more efficient and effective.

During the requirements elicitation phase, it is important to talk with experts on the business. An SME can really be anyone who has some information about the business that you are analyzing. These are the people who provide you with the critical understanding of the business: why things are done, how they are performed, and what the results are. Without these SMEs, there is no business analysis. Some of the SMEs may report to the sponsor, but some will not. On small projects, the sponsor may be the head of a department using application software that interfaces with other departments. SMEs are business people from various organizational units who have varying amounts of interest in your project. Your biggest challenge is to convince these people that they should spend time with you and tell you everything that you want to know about their business. Successfully convincing them that you are on their side and working to help them is the best secret to being a successful BA.

Users of the solution must be identified and supported during the design and implementation phases of a project. They should be involved in screen and workflow design. They also should be involved in user acceptance testing (see Chapter 5). In addition, BAs usually are responsible for training users in the software and procedural changes that will be necessary upon solution implementation.

All SMEs are not created equal. Expect many challenges with personality types, working styles, and motivations. Understanding and winning over these experts will not be easy. It will require you to get to know these individuals, do research before meeting with them, and use every bit of charm that you can possibly command to convince them that they should tell you their deepest, darkest secrets. These are not personal secrets, but honest revelations about how they do their jobs, what their most important issues are, and why broken processes are not working.

Соседние файлы в предмете [НЕСОРТИРОВАННОЕ]