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