Module 4: Business Analysis Frameworks Flashcards
Business Analysis
Activities performed to support the delivery of solutions that align with business objectives and provide continuous value to the organization
Functions of a Business Analyst
Strategic business analysis
Eliciting and analyzing requirements
Feasibility studies of new business opportunities
Scoping out an opportunity and identifying a solution
Preparation of a business case
Tailoring project methodology for business analysis activities
Monitoring changes in requirements
Requirement
A condition that is necessary in the resulting product or service that satisfies the business need
4 Types of Requirements
Business Requirement - high-level business need/goal
Stakeholder Requirement - needs of a stakeholder (usually through user stories)
Solution Requirement - describes the specific characteristics of a solution
Transition Requirement - describes how the solution is deployed and put into production
Requirement Management Plan
A plan describing how requirements will be analyzed, documented, and managed
Business Rules Catalog
A list of business rules
Definition Ready
A set of agreed-upon condition that ensure a user story is fully understood by the entire team before work begins
Glossary
A list of definitions for terms about a product
Product Backlog
A list of work need to develop and improve a product including items, requirements, features, and user stories
Use Case
A process model that narratively describes how a system interacts with users to achieve a specific goal. It helps identify and elaborate on requirements by outlining user actions, system responses, and possible outcomes
User Stories
A concise, informative description of a requirement from the perspective of the end user. It captures who the user is, what they need, and why it is important
4 Types of Stakeholder Groups
Management - project sponsors, senior managers
Business - governing bodies, users, SMEs
Project and Product Team - project manager, developers, transition teams, etc
External - government, vendors, customers, competitors
Stakeholder Analysis
A cyclical process to gather, analyze, and quantify information to determine whose interests should be taken into account throughout a project
Aspects of Stakeholders
Power - power to affect the project
Impact - impact on the project
Attitude - positive/negative view of the project
Beliefs - root convictions about a project
Expectations - vision that a stakeholder may have for a project
Influence - extent to what a stakeholder can choose to do with their power/impact
Proximity - degree to which a stakeholder’s role is associated with the project
Interest - interest in a project
RACI Chart
A project management tool used to clarify roles and responsibilities within a project or process. It helps define who is involved in each task and to what extent.
Responsible: the person who owns the project, task or work
Accountable: the person who will sign off on the work, judging its completion, and how it meets quality standards
Consulted: people who have the ability or knowledge needed to complete the work
Informed: people who must be kept informed of the work but are not necessarily consulted
Predictive Approach
A structured, plan-driven methodology where the project scope, timeline, and costs are defined upfront. This approach follows a linear sequence of phases—such as initiation, planning, execution, monitoring, and closure—where each phase must be completed before moving to the next.
Key characteristics of a predictive approach:
Fixed Scope: Requirements are well-defined at the beginning and changes are minimized.
Detailed Planning: A comprehensive project plan outlines tasks, schedules, and resources in advance.
Sequential Phases: Work progresses through predefined stages, such as requirements gathering, design, development, testing, and deployment.
Low Flexibility: Changes are difficult to incorporate once the project is underway.
Adaptive Approach
A flexible and iterative method that allows for evolving requirements and continuous improvements throughout the project lifecycle. Instead of following a rigid plan, this approach embraces change and focuses on delivering value incrementally.
Key Characteristics of an Adaptive Approach:
Flexible Scope: Requirements can evolve as the project progresses based on feedback and changing business needs.
Iterative Development: Work is completed in short cycles (iterations or sprints) to deliver value early and often.
Continuous Feedback: Stakeholders are actively involved, ensuring alignment with business goals.
Emphasis on Collaboration: Cross-functional teams work closely together to adapt to changes quickly.
Frequent Testing & Refinement: Regular reviews ensure that the product or solution meets user needs effectively.
