IIBA ECBA – Business Analysis Elicitation and Collaboration (IIBA -ECBA) Part 4

16. Exercise: Confirming Elicitation Results

Exercise Confirming Elicitation Results after completing this topic, you should be able to demonstrate your understanding of the task techniques and roles involved in confirming elicitation results. In this exercise, therefore, you are required to demonstrate your understanding of the task techniques and and roles involved in conforming elicitation results. There are several tasks involved in conforming elicitation results identifying tasks involved in confirming elicitation results, identifying techniques and guidelines involved in confirming elicitation results, and finally, identifying the stakeholder roles involved in confirming elicitation results.

The purpose of confirming elicitation results is to review the information that you received during the session. As a business analyst, you need to check that information is accurate and consistent with other confirmed elicitation results. Which statement describe the inputs and elements used to confirm elicitation results? Here we have the options unconfirmed elicitation results are the single input to the task. Sources may include documents and stakeholder knowledge. Business analysts may conduct meetings with stakeholders to confirm results. Results should never be compelled with recent or historic iterations. The elicitation activity plan is the single input to this task. And finally, stakeholders compare elicitation results against information sources.

And here we have the answer for you to compare. Option one that’s correct unconfirmed elicitation results is information that you have elicited and discovered during various sessions and needs to be evaluated in the task confirm benefitation results. Option two that’s correct. Documents and stakeholder knowledge could be discovered during a workshop, a meeting with prototypes, or through a survey. Option three. That’s correct. Conducting meetings with stakeholders ensures that information captured is accurate and complete. Option four. That’s incorrect. It is actually a good practice to ensure that elicitation results are compared against confirmed elicitation results from other sessions. Option five. That’s incorrect.

The input to the Confirmed Elicitation results task is actually unconfirmed elicitation results. The elicitation activity plan is the input to the conduct elicitation task. Option six and the last one that’s correct stakeholders compare elicitation results against information sources such as other stakeholders, or documentation and reviews with implementation subject matter experts. Checking that the information you received during an elicitation session is accurate and consistent with other confirmed elicitation results is part of your responsibilities as a business analyst. Which statements describe the inputs and elements used to confirm elicitation results? Here have the options stakeholders compare elicitation results against information sources.

Results may be compared for consistency with recent or historic iterations. Variations of results and inconsistencies uncovered using specifications and models will be addressed. Sources should only consist of specific documentation approved by the stakeholders. Business analysts should not conduct meetings with stakeholders to confirm results. And finally, unconfirmed elicitation results as a single input to the task. And here you have the answer. Option one that’s correct elicitation results are compared against confirmed elicitation results from other sessions. Option two that’s correct. Not only are results compared with recent or historic iterations, they’re also compared against confirmed elicitation results from other sessions.

For currency and consistency. Option Three that’s correct the variation of results helps to identify inconsistencies for additional information that may require additional elicitation sessions. Option Four that incorrect sources may include any information that you elicited and discovered during various sessions. Option Five that’s incorrect conducting meetings with stakeholders ensures the information captured is accurate and complete objects and the last one that’s correct unconfirmed solicitation results is information that you have elicited and discovered during various sessions. Needs to be evaluated in the Confirmed Elicitation Results task. Now, while progressing through the Elicitation plan, as a business analyst, you will look to the plan to compare sources and elicitation results, match the descriptions of each technique and guideline to the techniques and guidelines used to confirm elicitation results.

Option One is typically formatted with a list of various solicitation activities, attendees, and how it will be conducted. Option Two confirms activity results and determines inconsistencies. Option Three compares solicitation results to source information and other documents. Option Four confirms the elicitation results, reflect the stakeholder needs and the last options. Option Five facilitates the review of elicited results and reviews. Drafted elicitation results. Here are the targets elicitation Activity Plan existing business analyzes information, document analyzes reviews, interviews and workshops, and here is the answer for you to compare.

The Elicitation activity plan is typically formatted with a list of various solicitation activities, attendees and how it will be conducted. It includes activities participants and the method to be used to conduct the license activity. Existing business analyzes information confirms activity results and determines inconsistencies that can occur between written expressed requirements and diagrams used in other session. Document analysis compares Elicitation results to source information and other documents. An example of this may be if the business analyst compares the business rules defined in a session to those held within existing policies. Reviews can be formal or informal. They confirm that the elicitation results reflect the stakeholder need and remove any potential errors for the resulting solution. Interviews will facilitate the review of Elicited results.

The business analyst should send the information in advance, provide an agenda, and advise the stakeholder that he or she will be required to provide further feedback leading to an agreement. Workshop review drafted Elicitation Results in order to encourage participation and feedback, participants can be paired to discuss information. The objective of confirming Elicitation Results is to ensure that the results are valid, accurate and appropriate. Which option best describes the output of the Confirmed Elicitation Results task? Here we have the options integrated information deemed relevant by stakeholders and the business analyst raw data gathered from stakeholders by the business analyst, information about problem deemed relevant by customers and end users and finally, a document ratified by senior executives within the organization. Here you have the answer. Option One this is the correct option.

The output of the task is confirmed. Elicitation results. All the information deemed relevant during the task is integrated into one single document. Option Two this option is not correct. It describes the output of the conduct solicitation task, which is unconfirmed elicitation result. Option three. This is correct. Customers and end users are involved in confirming elicitation results, but a better description would say that all stakeholders confirm the relevance of the information. Option four. That’s incorrect. All stakeholders involved in a project, as well as the business analysts, are involved in producing the confirmed elicitation results. Now all stakeholders must agree on and confirm validity, accuracy, and appropriateness when confirming elicitation results.

Who is the key stakeholder responsible for confirming the elicitation result? Here you have the options the domain subject matter expert, the regulator, implementation subject matter expert, or the end user. Here you have the answer for you to compare. Option One this is the correct option. The domain subject matter expert is the key stakeholder who bears responsibility for confirming the results. This individual provides expertise and identifies any omissions in the result. Option two. That’s incorrect. A regulator is not the key stakeholder responsible for confirming the result. The regulator determines whether the business analyzes information and requests meet regulatory and legal requirements.

Option three. That incorrect. Implementation subject matter expert is not the key stakeholder responsible for confirming the results. Although this individual may assist the domain subject matter expert option Four in the last one that’s also incorrect. The end user not the key stakeholder responsible for confirming the results. The end user may, however, assist in confirming these results.

17. Communicating BA Information: Inputs and Elements

Communicating business analyzes information, inputs and Elements After completing this topic, you should be able to recognize considerations for communicating business analyzes information. The purpose of communicating business analyzes information is to ensure a shared understanding by stakeholders and so that the business analysis effort can proceed. The inputs include business analyzes information in any form that it may be in. It could be in the form of notes, designs, memos presentations. The Stakeholder Engagement approach helps the business analyst to understand how they can communicate and when they should communicate with the stakeholder. The task itself is to communicate business analyze information and as said earlier, that information can be in any form. The output is that the business analyzes information has been communicated. Communicating business analyzed information includes confirmed elicitation and analyzed elicitation results and can include information of any kind. This could be use cases.

They are perfect for the domain stakeholders. Since use cases are focused on a particular objective for a stakeholder, they are also wonderful to use when communicating with an implementation subject matter experts. As the use case also includes information about how the system is to respond. Communicate business analyzes information, overview the task communicate business analyzes information has to inputs business analyze information and the Stakeholder Engagement approach. The output is communicated business analyzes information. Inputs business analyzed information takes the form of any kind and at any level of detail and means a communication need exists. Information can be provided at any level of detail, at a high level for executives in a summary format or at a very detailed level in order for the implementation team to be able to confirm that information is complete and accurate and ready to be taken and used for further activities in the project.

Communication continues as it is iterative and as long as the need that is within the solution scope exists. But what does that mean? Well, basically as we progress through elicitation and we are confirming information, we are going to uncover additional levels of information that need to fill stakeholders requirements and provide a complete set of information in order to move forward. All of these activities facilitate stakeholder collaboration and promote positive reactions or will help to mitigate any negative reactions. The Stakeholder Engagement approach provides details for the business analyst and describes the various stakeholder needs for communication, when and how they need to be communicated and to what level.

The purpose of the information package is to communicate requirements and designs in various formats. They can be user stories that’s typically used in an adaptive approach to assist in planning and review activities. Inputs The Stakeholder Engagement approach describes various stakeholders need for communication. Prepare the information Package The purpose of the information package is to communicate requirements and designs, assist in planning and review activities, communicate inputs to solution design, and meet contractual or regulatory requirements. Detailed requirements help the implementation team to understand the level of effort required to be able to design and create the solution. It also helps the project manager to understand the level of effort and what kind of resources are needed. The information package also helps to confirm whether or not the requirements are meeting any contractual or regulatory requirements. The primary goal is to ensure the information is clear, accurate and understood by all stakeholders and can be used for further development. The business analyst will determine who will be receiving the information. The stakeholder will review the information to ensure the needs are met and the business analyst will ensure that the requirements are within the scope of a solution.

The stakeholders should therefore receive information in their preferred style of communication. This can be over the phone, through an email or through a formal presentation. The business analyst also determines the type of information to be communicated. This is based on who the stakeholder is and their role in the initiative. Prepare the information package. The main goal is to communicate clear and usable information. Role of Business Analyst The role of business analyst is to determine the audience stakeholder needs, the preferred style of communication, information to communicate, if content and format are appropriate, how other activities are supported, and if any constraints must be considered. The business analyst will determine if the content and the format are appropriate to the audience and if the information is at the right level of detail for those participants.

The business analyst will also determine how other activities are supported by the business analyzes information. This often shows itself in the form of training and town hall meetings in order to communicate how the changes will be impacting various departments. Of course, the business analyst also has to ensure that and that the constraints of the requirements themselves are communicated effectively. To ensure stakeholder agreement is reached, business analyzing information can be provided to stakeholders in either a formal or informal format. Informal approaches include email, telephone, conversations in the hall or a meeting. Formal approaches include a presentation. This is typically a high level overview of an initiative. It includes a description of the scope and how the solution meets the goals and objectives of the business and how the functions are supporting the change. Presentations are a great way to facilitate decisions. Possible package formats documentation can be formal or informal.

The presentation is a high level overview and it covers the goals of change, the functions of solutions, and information needed to make decisions. The business analyst will provide the appropriate level of detail for the stakeholders. A business domain subject matter expert is unlikely to care about the level of detail that an implementation subject matter expert cares about. An implementation subject matter expert who has provided highlevel detail is likely to fill in the blanks and may not meet the goals and objectives of the user in the resulting solution. It’s really important to allow stakeholders time to review and make any queries about the business, analyze information and give them enough time to be able to express and point out the concerns that they have and collaborate with them in order to reach some conclusions.

There are varied approaches to communicating with group collaboration that reaches many stakeholders at one time. Reviews are a perfect example of this. We’re often getting cross functional teams into a room to walk through the requirements and the business analyzed information, have likely discussion and provide the appropriate level of detail for stakeholders and allow them time to review, make any queries, and point out concerns. Communication Platforms communication platforms include group collaboration, which reaches many stakeholders and facilitates immediate discussion and feedback. There are times when individual collaboration is the only way that you can get feedback from a particular stakeholder.

These are often done over the phone or in meetings, but this does not preclude you from providing information prior to a meeting in order for them to prepare. Email and nonverbal methods are used when information has been through a few cycle of review and the stakeholder reviewing the information is familiar with the content. These approaches are best used when a conversation is not required to provide clarification, but rather a stepping stone toward moving from communicated requirements to the next phase of business analyzes activities.

18. Communicating BA Information: Guidelines and Techniques

Communicating Business Analyzed Information Guidelines and Techniques After completing this topic, you should be able to recognize the guidelines and techniques used to communicate business analyzes Information The business analyzed approach provides guidance on the formality and level of detail needed by stakeholders. It states the frequency of communication and specifies how communication may be affected by the number and geographical dispersion of stakeholders. The business analyst may find themselves up early in the morning collaborating online with a group of stakeholders in another time zone.

This requires a very formal approach with checklists, a firm agenda, and a clear confirmation of stakeholder agreement and stakeholder concerns. The information management approach specifies how the information will be packaged and the communication methods used to ensure that stakeholders agree. The information management approach includes where the information will be stored and accessed and who has access to the information. Guidelines and tools.

The business analyst approach identifies formality and the level of detail, states the frequency of communication and specifies how communication may be affected by the number and geographical dispersion of stakeholders. The information management approach specifies packaging and communication methods.

Interviews are conducted with an individual to ensure that he or she understands the business analyze information. The business analyst will also have the opportunity to elicit feedback and gain agreement. Reviews are conducted in groups or with an individual and are typically formal using a checklist and a list of questions.

This will result in feedback and hopefully agreement on the content. Inspections are a type of review and are very formal. It includes all key stakeholders, including both the implementation team and the domain subject matter expert as well as chair of the meeting. There is a clear checklist, clear instructions on how the requirements are reviewed and the type of feedback needed in order for the business analyst to incorporate any changes before moving to the next phase, which is implementation. Workshops are a facilitated approach. It engages participants in group discussions and can include cross functional teams. This helps in communicating how other groups are impacted by the solution. Techniques include interviews intended for an individual, reviews intended for groups or individual collaboration and workshops intended for groups. You.

19. Communicating BA Information: Stakeholders and Outputs

Communicating Business Analyzes Information stakeholders and Outputs After completing this topic, you should be able to recognize how to work with stakeholders when communicating business analyzes information. The domain subject matter expert will validate the business analyzes information information that is specific to their particular domain and will also require information about goals and objectives of the business in order to ensure that their needs are aligned to the business goals. The implementation subject matter experts will use the business analyze information in the form of requirements and designs to implement the solution.

He or she may have needs that will result in requirements such as data integration and nonfunctional requirements. The tester must understand the requirements in order to create test cases. There are excellent sources of information needed to create testable requirements. The tester must understand the requirements in order to create test cases. They are excellent sources of information needed to create testable requirements.

Customers may need to be communicated with to explain what form the change will take. As with customers, the end user needs to be communicated at the appropriate time to help them adjust to the change and prepare for the new solution. This assists in adoption of the new solution and the quicker realization of the return on investment around productivity. Other stakeholders, such as compliance or legal departments, will need to be informed at appropriate times during the project.

Operational Stakeholders operational stakeholders include the domain subject matter expert who validates business analyzed information, the implementation subject matter expert who needs information about requirements and designs for implementation, and the tester who must understand requirements and designs. Other Stakeholders other stakeholders include the customer who must be regularly updated, the end user who must also be regularly updated, and other stakeholders who must be provided with information at some point during the initiative.

Typically, the business analyst will communicate with a regulator or compliance expert only when the requirements are at a sufficient level of detail and completion to inform the regulator of how the requirements might be impacted by regulation and to ensure that our business rules are included. Human resources may need to be informed that the roles and responsibilities of stakeholders change. This will include any union representatives in order to ensure that any process changes and activities within a process align with collective agreements. When is Business analyzed information considered to have been communicated? When stakeholders understand the Content the business analyst will know when a stakeholder understands the content.

Typically, this comes in the form of agreement and or an understanding of your explanation. It is important for the business analyst to communicate to the stakeholders the implications of the change and the impact the solution will have on their respective departments. This may raise additional concerns which requires the business analyst to address those concerns and ensure that the solution is of sufficient value to meet the stakeholder needs, but not necessarily the ones output communicated. Business Analyze Information Business analyze information is considered to have been communicated. When the stakeholders understand the context and they understand its implications.

20. Exercise: Communicating BA Information

Exercise Communicating Business Analyzes Information after completing this topic, you should be able to demonstrate your understanding of the tasks, techniques and roles involved in communicating business analyzed information. Therefore, in this exercise you are required to demonstrate your understanding of what’s important regarding the guidelines and techniques involved in communicating business analyze information.

There are several tasks involved in communicating business analyzes information, identifying considerations relevant for communicating business analyzed information, identifying guidelines and techniques used to communicate business analyze information, and identifying how business analyzed information is communicated to stakeholders. As a business analyst, you should ensure that there is a shared understanding by stakeholders so that the business analyzed effort can proceed. You can do this by communicating business analyze information. Which statements describe the considerations for communicating business analyzed information? Here we have the options business analyze information and the Stakeholder engagement approach form inputs to the task. The objectives and goals of the information package must be determined.

A format for the information package must be chosen. An appropriate communications platform should be selected, communications should be done formally to ensure consistency across the organization and finally, our stakeholders should receive the same information in the same format to ensure a standardized approach. And here we have the answers for you to compare. Option one that’s correct business analyzes information includes information of any kind such as confirm, elicitation and analyze the elicitation results. The stakeholder engagement approach is an input that provides details and describes various stakeholders communication needs. Option Two that’s correct the primary objective or goal is to ensure that the information is clear, accurate and understood by all stakeholders and that it can be used for further development.

Option Three that’s correct the format for packages can be informal or formal depending on the audience. Informal packages include email, telephone and meetings. Formal packages involve high level overviews during presentations. Option Four that’s correct communication platforms include group collaboration involving many stakeholders at one time, individual collaboration done via telephone or meetings or email and nonverbal methods if the stakeholder is familiar with the content. Option Five that’s incorrect communication can be done formally or informally depending on the type of stakeholder needing to be addressed.

Option Six that’s incorrect the type of information to be communicated is based on who the stakeholder is and that stakeholders role in the initiative. As a business analyst, the method you use to communicate business analyzed information is critical. Match the descriptions to the guidelines and techniques used to communicate business analyzed information. Here you have the options specifies communication frequency and how it may be affected by the amount and locations of stakeholders.

Specifies the communication methods, where the information will be stored and who has access to it. It’s conducted with an individual to ensure understanding, elicited feedback and gain agreement is conducted in a group or with an individual and finally engages participants in group discussions and can include crossfunctional teams. And here you have the targets business analyzed approach information management approach interviews, reviews and workshop, and this is the answer for you to compare. The business analyzed approach specifies communication frequency and how it may be affected by the amount and location of stakeholders.

The business analyzed approach also provides guidance on the formality frequency and level of detail needed by stakeholders. Collaborating with various stakeholders across different time zones will need a formal approach. The information management approach specifies the communication methods, where the information will be stored and who has access to it.

It also specifies how the information will be packed and the communication methods used to ensure stakeholder agreement. Interviews are conducted with an individual to ensure understanding, illicit feedback and gain agreement. During an interview, it is imperative for the business analyst to ensure that the individual’s understanding before the individual can confirm agreement to a solution. Reviews are conducted in a group or with an individual’s. Reviews are typically formal and make use of a checklist and a list of questions.

This results in feedback and possible agreement on the content. Workshops engage participants in group discussions and can include crossfunctional teams. Workshops are a facilitated approach that can help in communicating how other groups are impacted by the solution. As a business analyst, you will need to communicate business analyze information to various stakeholders. When is business analyzed information considered communicated? Here we have the options when stakeholders understand the content, when stakeholders understand its implications, when stakeholders receive an email, or when stakeholders disagree on the communication type. And here you have the answer.

Option one that’s obviously correct information is considered communicated when a stakeholder understands the content, the business analyst will know the stakeholder has understood the content when the stakeholder agrees with or accepts the business analyst explanation. Option Two that’s correct business analysis information is considered communicated when stakeholders understand its implications. Stakeholders will then also understand the impact the solution will have on departments and will have an opportunity to raise additional concerns. Option Three that’s incorrect in addition to receiving an email, a stakeholder will need to acknowledge an understanding of the content in order for the information to be considered communicated. Option Four that’s incorrect this agreement does not mean that a stakeholder understands the communication itself, which is essential in having the information be considered communicated.

As a business analyst, how you communicate business analyze information depends on the stakeholder and their various levels and needs. Match the description of how the business analysis team works when communicating business analyzes information to the appropriate stakeholders. Here we have the options validates the business analyzes information and needs information specific to their particular domain uses requirements and designs to implement the solution. Requires understanding in order to create test cases, requires communication to explain what form the change will take and finally requires communication at the appropriate time to help them adjust to the change and prepare for the new solution. Here we have the targets domain subject Matter expert implementation subject matter Expert tester customer and end user.

 The domain subject matter expert validates the business, analyzes information, and needs information specific to their particular domain. The domain subject matter expert will also require information about goals and objectives of the business in order to ensure that their needs are aligned to the business goals. The implementation subject matter expert uses requirements and designs to implement the solution and may have needs that will result in requirements such as data integration and non functional requirements.

The tester requires understanding in order to create the test cases and is also an excellent source for information needed to create testable requirements. The customer requires communication to explain what form the change will take. The end users require communication at the appropriate time to adjust to the change and prepare for the new solution. Communicating with the end users at the appropriate time assist in the adoption of the new solution and a quicker realization of the return on investment around productivity.