Glossary Terms Flashcards
Define the term “Agilometer”
• Tool to assess risk level of using Agile with P2
• Should evolve to suit needs of the organisation
Define a “Burn chart”
A technique for showing progress
- Work completed and to do
- updated regularly
Define a “Burn-down chart”
- Progress chart
- Run chart of outstanding work
Define a “Burn-up” chart
• Progress chart
• Run chart of completed work
Define a “checkpoint report”
• Progress report at a checkpoint from a TM/team to a PM
• Includes data defined in the work package
Define a “Customer Subject Matter Expert”
• Within delivery team
• Representing customer stakeholders
• Responsible for ensuring project product is understood and correct at detail level
Define the “Definition of Done”
• Set of criteria used to determine if a piece of work is completed.
> Something is either ‘done’ or is ‘not done’
Define the “Definition of Ready”
• A set of criteria used to determine if a piece of work is ready to be started
Define an “EPIC”
• High level requirement not fully refined/understood
• Eventually broken down into user stories/requirements
Define a “Gantt Chart”
• 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
Define “Gap Analysis” -
• Compares 2 sets of data and identifies differences
• Commonly used to compare a set of requirements with actual delivery
Define “Kaizen”
• Japanese philosophy
• Means “good change”
• Understood to refer to continual improvement.
- Everyone contributing regularly for small beneficial changes to improve efficiency
Define “Kano”
• A model to help understand customer preferences
• Considers product/service attributes grouped like “Basic Factors” “Excitement Factors” “Performance Factors”
Define “Manage by Exception”
• A technique by which variances from a plan exceed a pre-set control limit are escalated for action
Define a “planning horizon”
-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
-
Define a “Product Description”
• Products: Purpose, composition, derivation & quality criteria
• Created during planning stage, straight after product need is identified
Define a “Project Brief”
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
Define a “ Project Product Description”
• Special type of product description
• Used to gain agreement from user on scope & requirements. Also to define quality criteria and acceptance criteria
Define a “retrospective”
• A regular event to look at improving the work process gradually
• In keeping with ‘Inspect and adapt’
Define “Spiking”
• Temporary piece of work to understand more of a given situation
• eg prototype or research
• Reduces uncertainty
Define “Sprint Zero”
• Sprint at the beginning to address upfront activities like forming a team, visioning, defining the architecture.
• Within IP stage including the development team
Define a “stand-up meeting
• Short meeting by development team to assess progress
• 15mins max
• Work completed, to be done and problems envountered
Define “velocity”
• Description of the rate of progress a team is making
Eg. 20 user stories per week
Define “visioning”
• 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?
Define “Work in Progress” WIP
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
What is a “Safe-To-Fail” experiment?
• Designed to have a limited impact on the system or plan in the event of failure.
• Not suitable for large failures
Define : Lead time (cycle time)
• Commonly used in Kanban
• How long it takes a work item to go through the system
