ACP-520 flashcards
ACP-520 · 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 value: working software
- The first Agile value pair states that working software is valued over comprehensive documentation, meaning documentation still has value but delivered functionality takes priority when the two compete.
- Responding to change
- An Agile value stating that responding to change is valued over following a plan; planning remains useful, but plans are adjusted as new information arrives.
- Simplicity principle
- The Agile principle that simplicity, defined as maximizing the amount of work not done, is essential; it directs teams to avoid building unneeded features.
- Self-organizing team principle
- The Agile principle that the best architectures, requirements, and designs emerge from self-organizing teams, which decide how to organize their own work.
- Twelve Agile principles
- The set of guiding principles behind the Agile Manifesto, covering continuous delivery, welcoming change, frequent delivery, daily collaboration, motivated individuals, and regular reflection.
- Scrum three accountabilities
- Scrum defines Product Owner, Scrum Master, and Developers; together they form one cross-functional Scrum Team of typically ten or fewer people.
- Five Scrum events
- Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective; the Sprint is the container event in which the other four occur.
- Scrum artifact commitments
- Each Scrum artifact has a commitment: the Product Backlog is committed to the Product Goal, the Sprint Backlog to the Sprint Goal, and the Increment to the Definition of Done.
- Kanban WIP limit
- A cap on the number of items allowed in a workflow column or state at one time, used to expose bottlenecks and encourage finishing work before starting more.
- Extreme Programming practices
- XP practices include pair programming, test-driven development, continuous integration, small releases, refactoring, simple design, and collective code ownership, aimed at technical excellence.
- PI Planning in SAFe
- A recurring cadence event where an Agile Release Train aligns teams on a shared set of objectives for the coming Program Increment, typically held every eight to twelve weeks.
- Daily Scrum purpose
- A 15-minute event for Developers, held at the same time and place each working day, to inspect progress toward the Sprint Goal and adapt the Sprint Backlog.
- Product Owner accountability
- The Product Owner maximizes product value and is accountable for effective Product Backlog management, including ordering items and ensuring the backlog is transparent and understood.
- Scrum Master accountability
- The Scrum Master is accountable for the Scrum Team's effectiveness, coaching the team and organization, facilitating events as needed, and removing impediments; the role holds no command authority.
- Developers in Scrum
- The team members committed to creating any aspect of a usable Increment each Sprint; they self-manage and decide how to convert backlog items into value.
- Servant leadership
- A leadership style in which the leader's primary focus is removing impediments, enabling the team, and shielding it from interference rather than assigning and directing tasks.
- RACI matrix rule
- A responsibility chart assigning Responsible, Accountable, Consulted, and Informed roles; each row should have exactly one Accountable party to avoid conflicting ownership.
- Scrum Team size
- A Scrum Team is cross-functional and typically ten or fewer people; it contains no sub-teams or hierarchies, though it may organize work across members.
- Story points
- A unitless relative estimate of effort, complexity, and uncertainty for a backlog item; values are team-specific and are not convertible to hours.
- Velocity formula
- Velocity equals the sum of story points of items completed to the Definition of Done in a Sprint; average several Sprints before using it for forecasting.
- Sprints remaining forecast
- Expected Sprints to finish remaining work equals remaining story points divided by average velocity; the result is a forecast, not a commitment.
- Planning poker
- A consensus estimation technique in which each participant privately selects a card from a modified Fibonacci scale, then outliers are discussed until the team converges.
- Sprint Goal
- A single objective for the Sprint that gives the team focus; Sprint Backlog scope may be negotiated with the Product Owner as more is learned.
- Definition of Done
- A shared, explicit checklist that an Increment must satisfy; a backlog item is not counted as complete until it meets every criterion.
- Test-driven development cycle
- A three-step loop: write a failing test for the next behavior, write the minimum code to make it pass, then refactor while keeping all tests green.
- Continuous integration
- A practice in which developers merge to a shared mainline frequently, with an automated build and test run on each merge to detect integration problems early.
- Spike
- A short, timeboxed investigation used to reduce technical or requirements uncertainty before the team estimates or builds the related work.
- Sprint Review purpose
- A working session with stakeholders to inspect the Increment and adapt the Product Backlog; it is not merely a demo or a status report.
- Information radiator
- A publicly displayed chart or board, such as a burndown chart or Kanban board, that lets anyone see project status without asking the team.
- Stakeholder influence-interest map
- A grid plotting stakeholders by influence and interest, used to decide who needs close collaboration versus periodic updates.
- Burndown versus burnup
- A burndown plots remaining work over time within a Sprint; a burnup plots completed work and total scope, making scope changes visible.
- Little's Law
- Average work in progress equals arrival rate multiplied by average cycle time; it links WIP, throughput, and cycle time in a stable workflow.