1
Q
A systematic problem-solving process that collects pertinent information on a single A3-size sheet of paper.
A
A3?
2
Q
A method of collaboratively creating acceptance test criteria, used to build acceptance tests before delivery begins.
A
Acceptance Test-Driven Development (ATDD)?
3
Q
A term used to describe a mindset of values and principles, as set forth in the Agile Manifesto.
A
Agile
4
Q
An individual with knowledge and experience in agile who can train, mentor, and guide organisations and teams through their transformation.
A
Agile Coach?
5
Q
An approach that is both iterative and incremental to refine work items and deliver frequently.
A
Agile Life Cycle?
6
Q
The original and official definition of agile values and principles, formalised in 2001.
A
the Agile Manifesto
7
Q
A way of thinking and behaving underpinned by the four values and twelve principles of the Agile Manifesto.
A
Agile Mindset?
8
Q
A person embracing the agile mindset who collaborates with like-minded colleagues in cross-functional teams.
A
Agile Practitioner (Agilist)
9
Q
The twelve principles of agile project delivery as embodied in the Agile Manifesto.
A
Agile Principles?
10
Q
A simplistic and understandable approach to developing business application software using agile techniques and concepts, simplified from the Rational Unified Process (RUP).
A
Agile Unified Process (AgileUP)?
11
Q
A known, flawed pattern of work that is not advisable.
A
an Anti-Pattern?
12
Q
The scripted testing of code base for bugs and vulnerabilities.
A
Automated Code Quality Analysis?
13
Q
See Product Backlog.
A
Backlog?
14
Q
The team works together regularly to review, update, and improve project requirements as they learn more, so they can meet the customer’s needs.
A
Backlog Refinement?
15
Q
A system design and validation practice that uses test-first principles and English-like scripts.
A
Behaviour-Driven Development (BDD)?
16
Q
Two or more agile frameworks, methods, elements, or practices used together (e.g., Scrum combined with XP and Kanban Method).
A
Blended Agile?
17
Q
See Impediment.
A
a Blocker?
18
Q
Refers to a person with various depths of specialisation in multiple skills required by the team. Also known as Paint Drip. See also T-shaped and I-shaped.
A
a Broken Comb?
19
Q
A graphical representation of the work remaining versus the time left in a timebox.
A
a Burndown Chart?
20
Q
A graphical representation of the work completed towards the release of a product.
A
a Burnup Chart?
21
Q
A listing of all requirements for a specific project.
A
Business Requirement Documents (BRD)?
22
Q
A rhythm of execution, often a fixed period of time. See also Timebox.
A
Cadence?
23
Q
A project acceleration and collaboration technique where any team member is authorised to modify any project work product or deliverable, emphasising team-wide ownership.
A
Collective Code Ownership?
24
Q
The practice of delivering feature increments immediately to customers, often using small batches and automation.
A
Continuous Delivery?
25
A practice in which each team member’s work products are frequently integrated and validated with one another.
Continuous Integration?
26
A team that includes practitioners with all the skills necessary to deliver valuable product increments independently.
a Cross-Functional Team?
27
A collection of lightweight agile software development methods focused on adaptability to a particular circumstance, scaling based on project size and criticality.
the Crystal Family of Methodologies?
28
A brief, daily collaboration meeting where the team reviews progress, declares intentions, and highlights obstacles. Also known as daily standup.
a Daily Scrum?
29
A team’s checklist of all criteria required for a deliverable to be considered ready for customer use.
the Definition of Done (DoD)?
30
A team’s checklist for a user-centric requirement that contains all information needed for the team to begin work.
the Definition of Ready (DoR)?
31
A collection of practices for creating a smooth flow of delivery by improving collaboration between development and operations staff.
DevOps?
32
A process decision framework that enables simplified process decisions around incremental and iterative solution delivery.
Disciplined Agile (DA)?
33
A process that challenges underlying values and assumptions to better elaborate root causes and devise improved countermeasures, rather than just addressing symptoms.
Double Loop Learning?
34
An agile project delivery framework known for its emphasis on constraint-driven delivery (fixed cost, quality, time, variable scope).
Dynamic Systems Development Method (DSDM)?
35
A measure of the value of work completed in terms of the planned budget.
Earned Value (EV)?
36
An agile method focused on delivering multiple measurable value requirements to stakeholders.
Evolutionary Value Delivery (EVO)?
37
An agile software development method based on frequent cycles and a holistic set of practices (e.g., pair programming, test-first).
eXtreme Programming (XP)?
38
A lightweight agile software development method driven from the perspective of features valued by clients, organised around five iterative processes.
Feature-Driven Development (FDD)?
39
A product that is suitable for its intended purpose.
Fit for Purpose
40
A product that is usable in its current form to achieve its intended purpose.
Fit for Use
41
The coach for a team and service request manager working in a continuous flow or Kanban context; equivalent to a Scrum Master.
A Flow Master
42
A basic system or structure of ideas or facts that support an approach.
a Framework
43
A specific behaviour that a product or service should perform.
a Functional Requirement?
44
A specific function that a system or application is required to perform, typically documented.
a Functional Specification?
45
A strategy or policy deployment method.
Hoshin Kanri?
46
A combination of two or more agile and non-agile elements, potentially leading to a non-agile end result.
a Hybrid Approach?
47
An organisational improvement model named for its five phases: Initiating, Diagnosing, Establishing, Acting, and Learning.
IDEAL?
48
A strategic planning technique that acts as a roadmap for the organisation while building new products.
Impact Mapping?
49
An obstacle that prevents the team from achieving its objectives. Also known as a blocker.
an Impediment?
50
A functional, tested, and accepted deliverable that is a subset of the overall project outcome.
an Increment?
51
An approach that provides finished deliverables that the customer may be able to use immediately.
an Incremental Life Cycle?
52
A visible, physical display that provides information to the rest of the organisation, enabling up-to-the-minute knowledge sharing.
an Information Radiator?
53
Refers to a person with a single deep area of specialisation and limited interest or skill in other areas required by the team. See also T-shaped and Broken Comb.
I-shaped?
54
A timeboxed cycle of development on a product or deliverable during which all work needed to deliver value is performed.
an Iteration?
55
An approach that allows feedback for unfinished work to improve and modify that work through repetition.
an Iterative Life Cycle?
56
Events aimed at continuous improvement of a system or process.
e Kaizen Events?
57
A visualisation tool that enables improvements to the flow of work by making bottlenecks and work quantities visible, consisting of columns representing work states.
a Kanban Board?
58
An agile method inspired by the original Kanban inventory control system, used specifically for knowledge work, focusing on continuous flow and limiting work in progress.
the Kanban Method?
59
A framework for organising multiple development teams towards a common goal, extending the Scrum method while preserving its core elements.
Large Scale Scrum (LeSS)?
60
An adaptation of lean manufacturing principles and practices to software development, based on achieving quality, speed, and customer alignment.
Lean Software Development (LSD)?
61
The process through which a product is imagined, created, and put into use.
a Life Cycle?
62
A technique where multiple team members focus simultaneously and coordinate their contributions on a particular work item.
Mobbing?
63
The preferences of an organisation on a set of scales characterised by core values (e.g., exploration vs. execution, speed vs. stability).
Organizational Bias?
64
A comprehensive, cyclic, and structured approach for transitioning individuals, groups, and organisations from a current state to a future state with intended business benefits.
Organizational Change Management (OCM)?
65
See Broken Comb.
Paint-Drip?
66
See Pair Work.
Pairing?
67
A pair work technique specifically focused on programming.
Pair Programming?
68
A technique involving two team members working simultaneously on the same work item.
Pair Work?
69
An archetype user representing a set of similar end users, described with their goals, motivations, and personal characteristics.
e Personas?
70
A planned course correction designed to test a new hypothesis about the product or strategy.
a Pivot?
71
An iterative management method used to control and continually improve processes and products.
Plan-Do-Check-Act (PDCA)?
72
See Predictive Approach.
a Plan-Driven Approach?
73
An approach to work management that uses a work plan and manages it throughout a project's life cycle.
a Predictive Approach?
74
A more traditional approach with bulk planning upfront, followed by sequential execution in a single pass.
a Predictive Life Cycle?
75
An ordered list of user-centric requirements that a team maintains for a product.
a Product Backlog?
76
A person responsible for maximising the value of the product and ultimately accountable for the end product that is built. See also Service Request Manager.
a Product Owner?
77
The iterative process of increasing the level of detail in a project management plan as more information and accurate estimates become available.
Progressive Elaboration?
78
A management structure that standardises project-related governance processes and facilitates the sharing of resources, methodologies, tools, and techniques.
a Project Management Office (PMO)?
79
A product quality technique where the design of a product is improved by enhancing its maintainability and other attributes without altering its expected behaviour.
Refactoring?
80
A regularly occurring workshop where participants explore their work and results to improve both process and product.
a Retrospective?
81
An iterative planning technique where near-term work is planned in detail, while future work is planned at a higher level.
Rolling Wave Planning?
82
A knowledge base of integrated patterns for enterprise-scale lean-agile development.
the Scaled Agile Framework (SAFe®)?
83
An agile framework for developing and sustaining complex products, with specific roles, events, and artefacts (e.g., product owner, sprint, daily scrum).
Scrum?
84
A management framework emerging when teams use Scrum as their way of working and the Kanban Method to view, understand, and continuously improve their process.
Scrumban?
85
An information radiator used to manage product and sprint backlogs and visualise workflow and bottlenecks.
a Scrum Board?
86
The coach of the development team and process owner in the Scrum framework, responsible for removing obstacles and facilitating events. See also Flow Master.
a Scrum Master?
87
A technique to coordinate work when multiple Scrum teams work on the same product, facilitating discussions on interdependencies.
Scrum of Scrums (SoS)?
88
Describes the combination of development team, scrum master, and product owner used in Scrum.
a Scrum Team?
89
A cross-functional team where people fluidly assume leadership as needed to achieve objectives, often without direct managerial assignment of tasks.
a Self-Organising Team?
90
The practice of leading through service to the team, focusing on understanding and addressing team members' needs and development to enable high performance.
Servant Leadership?
91
The person responsible for ordering service requests to maximise value in a continuous flow or Kanban environment; equivalent to a Product Owner.
a Service Request Manager?
92
An organisation structured in a way that only manages to contribute a subset of the aspects required for delivering value to customers, often hindering cross-functional collaboration. For contrast, see Value Stream.
a Siloed Organisation?
93
The practice of attempting to solve problems by just using specific predefined methods, without challenging the methods in light of experience.
Single Loop Learning?
94
The practice of using a lightweight set of tests to ensure that the most important functions of the system under development work as intended.
Smoke Testing?
95
A collaborative approach to defining requirements and business-oriented functional tests using realistic examples.
Specification by Example (SBE)?
96
A short, fixed-length time interval within a project during which a team conducts research or prototypes an aspect of a solution to prove its viability.
a Spike?
97
Describes a timeboxed iteration in Scrum, typically 1 month or less.
a Sprint?
98
A list of work items identified by the Scrum team to be completed during the Scrum sprint.
a Sprint Backlog?
99
A collaborative event in Scrum where the Scrum team plans the work for the current sprint.
Sprint Planning?
100
A unit-less measure used in relative user story estimation techniques to rate work, risk, and complexity.
a Story Point?
101
A technique where multiple team members focus collectively on resolving a specific impediment.
Swarming?
102
The deferred cost of work not done at an earlier point in the product life cycle, often due to taking shortcuts.
Technical Debt?
103
A technique where tests are defined before work is begun, continuously validating work in progress to enable a zero-defect mindset.
Test-Driven Development (TDD)?
104
A fixed period of time (e.g., 1 week, 1 fortnight, 3 weeks, or 1 month) used to structure work. See also Iteration.
a Timebox?
105
Refers to a person with one deep area of specialisation and broad ability in the rest of the skills required by the team. See also I-Shaped and Broken Comb.
T-shaped?
106
A brief description of deliverable value for a specific user, serving as a promise for a conversation to clarify details.
a User Story?
107
A visual practice for organising work into a useful model to understand high-value features, identify backlog omissions, and plan value-delivering releases.
User Story Mapping?
108
The process of enhancing the user experience by focusing on improving usability and accessibility in the interaction between the user and the product.
UX Design?
109
An organisational construct that focuses on the flow of value to customers through the delivery of specific products or services.
a Value Stream?
110
A lean enterprise technique used to document, analyse, and improve the flow of information or materials needed to produce a product or service.
Value Stream Mapping?
111
In agile, the sum of the story point sizes for the features actually completed in an iteration, used to plan future capacity.
Velocity?
112
Constraints on the amount of work in each stage of a Kanban board to optimise flow and reduce bottlenecks.
Work In Progress (WIP) Limits?
Project management
flashcards
Decks in class (5)
# Cards
