Glossary

Question 1

80:20 rule

What is another name for the 80:20 rule?

Answer 1

80% of consequences stem from 20% of causes; focus on the 20% that matters.

Pareto Principle.

Question 2

What is the Agile Manifesto?

Answer 2

Defines the Agile approach, created 2001

Question 3

Benefits Assessment

Answer 3

A PRODUCT: describes how the benefits have actually accrued after a period of use in live operation.

Question 4

Business Case

Answer 4

A PRODUCT: baselined at the end of Foundations to provide vision and justification for the product from a business perspective

Question 5

Bottom Up

Answer 5

ESTIMATING TECHNIQUE: components are estimated individually and then added together

Question 6

Burn Down Chart

Answer 6

A chart counting the no. of features remaining [work remaining] or time left to complete [time remaining] for the current increment or timebox.

Question 7

Team members subtract time from Burn Down Charts. True or false?

Answer 7

False - they always re-estimate time remaining.

Question 8

Re Burn Down Charts:

Time remaining is used at which level?

Work remaining is used at which level?

Answer 8

Time = timebox level

Work = increment level

Question 9

What are Burn Down Charts used to predict?

Answer 9

When the work will be completed.

Question 10

Burn Up Chart

Answer 10

A chart showing features/requirements completed and the value earned so far.

Question 11

Team Board / Big Visible Chart (BVC) / Information Radiator / Kanban Board

Answer 11

A graphical representation of project/timebox information in a public place (transparency). Can be hand drawn or digital.

Question 12

Delivery Plan

Answer 12

A PRODUCT: provides high-level schedule of Increments for the project and the timeboxes that make up the first/imminent increment.

Question 13

Development Approach Definition (DAD)

Answer 13

A PRODUCT: baselined at the end of Foundations, it define the tools, techniques, practices and standards that will be applied in Evol. Dev.

Question 14

Development timebox (or just ‘timebox’)

Answer 14

A period of time in Evol. Dev. where solution development and testing takes place.

Question 15

Evolving Solution

What does this include? (5)

Answer 15

A PRODUCT: made up of all components of the ultimate solution together with any intermediate deliverables. These components may either be complete or a work in progress, depending on the time.

Models, prototypes, supporting materials, testing and review materials

Question 16

Feasibility Assessment

Answer 16

A PRODUCT: a snapshot of the evolving business solution and management products as they exist at the end of Feasibility.

Question 17

Foundations Summary

Answer 17

A PRODUCT: a snapshot of the evolving business solution and management products as they exist at the end of Foundations.

Question 18

Function / feature / requirement / User Story

Answer 18

Something the ultimate solution needs to have or be able to do.

Question 19

Increment Timebox

Answer 19

Timebox at the Increment (life cycle) level. Calculated by adding together that Development Timeboxes for the Increment.

Question 20

MoSCoW

Answer 20

A prioritisation technique, mainly used on requirements.

Question 21

Management Approach Definition (MAD)

Answer 21

A PRODUCT: baselined at the end of Foundations, it reflects the approach to management for the project, i.e. how it will be organised and planned, how stakeholders will be engaged, how progress will be demonstrated and reported.

Question 22

Management by Exception

Answer 22

A management approach where the SDT are empowered to evolve the detail of the solution. If they get stuck, they refer to the project-level roles.

Question 23

Minimum Usable Subset (MUST)

Answer 23

The minimum set of requirements needed to deliver a viable solution.

Question 24

Planning Poker

Answer 24

ESTIMATING TECHNIQUE: consensus-based using numbered cards. Used to estimate effort or relative size of user stories.

Question 25

Post-project

Answer 25

Lifecycle phase used to assess the business value delivered by the project.

Question 26

Pre-project

Answer 26

Lifecycle phase where the initial imperative is formalised in order to initiate a project.

Question 27

Prioritised Requirements List (PRL)

Answer 27

A PRODUCT: baselined at the end of Foundations, it describes the requirements the project needs to address and indicates their priority relatives to the project's objectives and the business need.

Question 28

Project Approach Questionnaire (PAQ)

Answer 28

A questionnaire based on the instrumental success factors (ISFs) which helps flags potential risks for a DSDM project.

Question 29

Project Governance Authority

Answer 29

A panel of corporate decisionmakers who decide whether a project should proceed or not.

Question 30

Project Review Report

Answer 30

A PRODUCT: updated at the end of each Increment (lifecycle phase), it captures feedback re what has been delivered and what has not, learning points and business value that should now accrue.

Question 31

Project timebox

Answer 31

Timebox at the project level, comprised of the sum of the Increment Timeboxes

Question 32

RACI

Answer 32

A responsibility assignment matrix, describing participation by roles. ``` R = Responsible A = accountable C = Consulted I = Informed ```

Question 33

Release

Answer 33

A collection of features being deployed into operational use. May comprise one or more Increments (i.e. timeboxes' worth of work)

Question 34

Solution Architecture Definition (SAD)

Answer 34

A PRODUCT: baselined at the end of Foundations, it provides the design framework for the solution.

Question 35

Scope

Answer 35

A description of what the solution will do and what it will not an/or which business areas will be included, i.e. the breadth.

Question 36

Servant-Leader

Answer 36

A leader that shares power, puts the needs of others first and helps people develop and perform as highly as possible.

Question 37

Story Points

Answer 37

A unit of size used for estimating, planning or tracking an Agile project.

Question 38

Test Driven Development (TDD)

Answer 38

An approach whereby the test is developed BEFORE the solution. The solution is built to pass the tests.

Question 39

Terms of Reference (ToR)

Answer 39

A PRODUCT: high-level definition of the over-arching business drivers for, and top-level objectives of, the project.

Question 40

Timebox plan

Answer 40

A PRODUCT: created for each Development Timebox, elaborating on the objectives, deliverables, the activities to be done and the resources needed. Created by the SDT and displayed on the team board.

Question 41

Timebox Review Record

Answer 41

A PRODUCT: created for each Development Timebox, capturing feedback from review. Describes what has been achieved and points for moving forward.

Question 42

Top-Down

Answer 42

ESTIMATING TECHNIQUE: uses approximate sizings and groupings, e.g. 10 components take 2 days. Groupings are then summed to give an estimate for the solution. Used when low-level detail is still unknown.

Question 43

Total Cost of Ownership (TCO)

Answer 43

The cost of the whole life of a project/solution, not just development costs, e.g. maintenance, repair etc.

Question 44

User Story What is the format?

Answer 44

A requirement expressed from the point of a user and with associated acceptance criteria. As a I need so that .

Question 45

Velocity

Answer 45

The rate at which the team delivers business value. Initially estimated but then validated by the team's track record. Used for planning.

Question 46

What are Functional Requirements (FRs)?

Answer 46

Those that define a function or feature, i.e. WHAT is required.

Question 47

What are Non-Functional Requirements (NFRs)?

Answer 47

Those that describe solution attributes/behaviour, i.e. HOW it will be achieved. Attributes also known as '-ilities', e.g. reliability