EXIN BCS Agile BA Professional flashcards
EXIN BCS Agile BA Professional · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Agile Manifesto values
- Four value statements: individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; responding to change over following a plan.
- Cynefin framework
- A sense-making model with five domains: clear, complicated, complex, chaotic, and disorder. Each domain requires a different decision approach, such as probe-sense-respond in complex situations.
- BACCM
- Business Analysis Core Concept Model with six interrelated concepts: change, need, solution, stakeholder, value, and context. It provides a common language for business analysis work.
- Just in time analysis
- Elaborating requirements at the last responsible moment to avoid wasted effort and outdated detail. It balances sufficient understanding with the cost of change.
- Definition of Done
- A shared team agreement describing the quality criteria a product increment must meet to be considered complete. It applies to all backlog items and supports transparency.
- Value stream mapping
- A technique to visualize the flow of work from idea to customer, identifying value-adding and non-value-adding steps. It helps reduce lead time and waste.
- Agile BA role
- A business analyst working in an agile team who facilitates shared understanding, supports product ownership, and ensures analysis is just enough and timely, rather than acting as a gatekeeper.
- Empirical process control
- A process management approach based on transparency, inspection, and adaptation. It is suited to complex work where requirements and solutions emerge through experience.
- Stakeholder power/interest grid
- A matrix that maps stakeholders by influence and interest. High power and high interest require close management; low power and low interest require monitoring.
- Product Owner
- The agile role responsible for maximizing product value by ordering the backlog and making priority decisions. The Product Owner is the single voice for requirements.
- Scrum Master
- The agile role that facilitates Scrum events, coaches the team, and removes impediments. The Scrum Master serves the team and the organization, not a command-and-control manager.
- Daily stand-up
- A short daily team meeting, typically 15 minutes, to synchronize work and surface impediments. Each member answers what was done, what will be done, and any blockers.
- Sprint review
- A collaborative event at the end of a sprint where the team demonstrates a working increment and collects stakeholder feedback. It informs backlog adaptation.
- Retrospective
- A recurring team event to inspect processes and identify improvements. The team agrees on actions to adapt its way of working in the next iteration.
- Stakeholder engagement plan
- A living document that identifies stakeholders, analyzes their interests and influence, and defines communication and involvement approaches. It is reviewed as the project evolves.
- Collaboration over handoffs
- An agile principle favoring direct, ongoing conversation among team members and stakeholders instead of sequential document handoffs. It reduces misunderstanding and delay.
- Distributed team communication
- Using asynchronous channels for documentation and synchronous channels for complex problem-solving. Maintaining a single source of truth supports alignment across locations and time zones.
- Conflict resolution in agile
- Addressing task conflict constructively while resolving personal conflict privately. Focus on interests rather than positions to preserve team collaboration and psychological safety.
- User story format
- A requirement expressed as: As a <role>, I want <goal>, so that <benefit>. It captures who needs the functionality, what is needed, and why it matters.
- INVEST criteria
- A checklist for good user stories: Independent, Negotiable, Valuable, Estimable, Small, and Testable. It helps teams create stories suitable for iterative delivery.
- Backlog refinement
- An ongoing activity to add detail, estimate, and reorder backlog items. It typically consumes up to ten percent of team capacity and prepares items for future sprints.
- Definition of Ready
- A team checklist that a backlog item must satisfy before it can be selected for a sprint. It ensures clarity, testability, and appropriate size.
- Acceptance criteria
- Conditions that a product increment must meet to be accepted by the Product Owner. They define boundaries and are often written as rules or Given-When-Then scenarios.
- MoSCoW prioritization
- A prioritization technique classifying items as Must have, Should have, Could have, or Won't have this time. It helps manage scope within a fixed timebox.
- Story mapping
- A visual technique arranging user stories along a user journey horizontally and by priority or release vertically. It helps slice releases and see product scope.
- Velocity
- A planning metric based on the amount of work a team completed in past iterations. It is used to forecast future capacity, not to compare teams or pressure performance.
- Epic and theme
- An epic is a large user story that can be decomposed into smaller stories. A theme is a group of related stories that share a common goal or feature area.
- Given-When-Then
- A scenario structure stating a precondition (Given), an action (When), and an expected outcome (Then). It supports behavior-driven development and clear acceptance criteria.
- Example mapping
- A collaborative workshop to break a story into rules, examples, and questions using colored cards. It builds shared understanding before development starts.
- Impact mapping
- A visual technique linking a goal to actors, impacts, and deliverables. It helps teams avoid output-focused delivery and align work with business outcomes.
- MVP and MMF
- A minimum viable product validates learning with the least effort. A minimum marketable feature delivers enough value for a release. Both guide incremental delivery.
- Kano model
- A model classifying features as basic, performance, excitement, indifferent, or reverse. It helps prioritize features based on their effect on customer satisfaction.