Glossary Terms

Question 1

Define the term “Agilometer”

Answer 1

• Tool to assess risk level of using Agile with P2
• Should evolve to suit needs of the organisation

Question 2

Define a “Burn chart”

Answer 2

A technique for showing progress
- Work completed and to do
- updated regularly

Question 3

Define a “Burn-down chart”

Answer 3

• Progress chart
• Run chart of outstanding work

Question 4

Define a “Burn-up” chart

Answer 4

• Progress chart
• Run chart of completed work

Question 5

Define a “checkpoint report”

Answer 5

• Progress report at a checkpoint from a TM/team to a PM
• Includes data defined in the work package

Question 6

Define a “Customer Subject Matter Expert”

Answer 6

• Within delivery team
• Representing customer stakeholders
• Responsible for ensuring project product is understood and correct at detail level

Question 7

Define the “Definition of Done”

Answer 7

• Set of criteria used to determine if a piece of work is completed.
> Something is either ‘done’ or is ‘not done’

Question 8

Define the “Definition of Ready”

Answer 8

• A set of criteria used to determine if a piece of work is ready to be started

Question 9

Define an “EPIC”

Answer 9

• High level requirement not fully refined/understood
• Eventually broken down into user stories/requirements

Question 10

Define a “Gantt Chart”

Answer 10

• Used for planning work activities against time using horizontal lines/bars showing when they start & end
• Further used to schedule dependencies between activities.
• More applicable in P. Management

Question 11

Define “Gap Analysis” -

Answer 11

• Compares 2 sets of data and identifies differences
• Commonly used to compare a set of requirements with actual delivery

Question 12

Define “Kaizen”

Answer 12

• Japanese philosophy
• Means “good change”
• Understood to refer to continual improvement.
- Everyone contributing regularly for small beneficial changes to improve efficiency

Question 13

Define “Kano”

Answer 13

• A model to help understand customer preferences
• Considers product/service attributes grouped like “Basic Factors” “Excitement Factors” “Performance Factors”

Question 14

Define “Manage by Exception”

Answer 14

• A technique by which variances from a plan exceed a pre-set control limit are escalated for action

Question 15

Define a “planning horizon”

Answer 15

-Period of time for which it is possible to plan accurately. Time close to current
- eg. A detailed plan for the next 2 weeks would be detailed
-

Question 16

Define a “Product Description”

Answer 16

• Products: Purpose, composition, derivation & quality criteria
• Created during planning stage, straight after product need is identified

Question 17

Define a “Project Brief”

Answer 17

A statement describing purpose, cost, time and performance requirements, and constraints for a project.

Created in SU, used during IP to create Project Initiation Document

Question 18

Define a “ Project Product Description”

Answer 18

• Special type of product description
• Used to gain agreement from user on scope & requirements. Also to define quality criteria and acceptance criteria

Question 19

Define a “retrospective”

Answer 19

• A regular event to look at improving the work process gradually
• In keeping with ‘Inspect and adapt’

Question 20

Define “Spiking”

Answer 20

• Temporary piece of work to understand more of a given situation
• eg prototype or research
• Reduces uncertainty

Question 21

Define “Sprint Zero”

Answer 21

• Sprint at the beginning to address upfront activities like forming a team, visioning, defining the architecture.
• Within IP stage including the development team

Question 22

Define a “stand-up meeting

Answer 22

• Short meeting by development team to assess progress
• 15mins max
• Work completed, to be done and problems envountered

Question 23

Define “velocity”

Answer 23

• Description of the rate of progress a team is making
Eg. 20 user stories per week

Question 24

Define “visioning”

Answer 24

• An exercise aiming to understand the overarching goal of a project.
• Answer key questions such as:
- Why is the work happening?
- Who is it for?
- What might it look like?

Question 25

Define “Work in Progress” WIP

Answer 25

Work started but not delivered from system/timebox- indicates problems, incidents, changes etc.

WIP limits used to restrict number if these in a given workstream

Question 26

What is a “Safe-To-Fail” experiment?

Answer 26

• Designed to have a limited impact on the system or plan in the event of failure.

• Not suitable for large failures

Question 27

Define : Lead time (cycle time)

Answer 27

• Commonly used in Kanban
• How long it takes a work item to go through the system