EC - Details Flashcards
Items to consider when determining the type of BA information to be discovered during elicitation
- business domain
- overall corporate culture and environment
- stakeholder locations
- stakeholders who are involved and their group dynamics
- expected outputs the elicitation activities will feed
- skills of the business analysis practitioner
- other elicitation activities planned to complement this one
- strategy or solution approach
- scope of future solution
- possible sources of the BA information that might feed into the specific elicitation activity
Items to consider when selecting elicitation techniques
- desired outcomes
- cost and time constraints
- culture of the organization
- access to sources of BA information
- techniques commonly used in similar intiatives
- techniques specifically suited to the situation
- the tasks needed to prepare, execute, and complete each technique
Items to identify with regards to elicitation logistics
- the activity’s goals
- participants and their roles
- scheduled resources, including people, rooms, and tools
- locations
- communication channels
- techniques
- languages used by stakeholders (oral and written)
Three common types of elicitation
- collaborative
- research
- experiments
Ways stakeholders may collaborate in elicitation
- participating and interacting during the elicitation activity
- researching, studying, and providing feedback on documents, systems, models, and interfaces
Items considered by a BA when guiding an elicitation activity
- the elicitation activity goals and agenda
- scope of the change
- what forms of output the activity will generate
- what other representations the activity results will support
- how the output integrates into what is already known
- who provides the information
- who will use the information
- how the information will be used
Reasons for creating BA information packages (including, but not limited to)
- communication of requirements and designs to stakeholders
- early assessment of quality and planning
- evaluation of possible alternatives
- formal reviews and approvals
- inputs to solution design
- conformance to contractual and regulatory obligations
- maintenance for reuse
Questions asked by a BA to determine the best way to present requirements (as part of communicating BA information)
- who is the audience of the package?
- what will each type of stakeholder understand and need from the communication?
- what is each stakeholder’s preferred style fo communication or learning?
- what information is important to communicate?
- are the presentation and format of the package, and the information contained in the package, appropriate for the type of audience?
- how does the package support other activities?
- are there any regulatory or contractual constraints to conform to?
Possible forms for BA information packages
- formal documentation
- informal documentation
- presentations
Common communication platforms for BA information
- group collaboration
- individual collaboration
- e-mail or other non-verbal methods
Effects of poor relationships with stakeholders on business analysis
- failure to provide quality information
- strong negative reactions to setbacks and obstacles
- resistance to change
- lack of support for, and participation in, BA work
- BA information being ignored
BA’s actively manage relationships with stakeholders who do the following
- provide services to the BA, including inputs to BA tasks and other support activities
- depend on services provided by the BA, including outputs of BA tasks
- participate in the execution of BA tasks
Reasons BA’s monitor the participation and performance of stakeholders
(aka ways to monitor the engagement of stakeholders)
- to ensure the right SME’s and other stakeholders are participating effectively
- to ensure stakeholder attitudes and interest are staying constant or improving
- to ensure elicitation results are confirmed in a timely manner
- to ensure agreements and commitments are maintained
Types of risks BA’s continually monitor for (managing stakeholder collaboration)
- stakeholders being diverted to other work
- elicitation activities not providing the quality of BA information required
- delayed approvals
