A - acceptance critera to Agilometer | B - backlog to business case | C - change authority to customer subject matter expert | D - definition of 'done' to Dynamic Systems Development Method | E - early adopter to experiment | F - G - feature to Glad! Sad! Mad! | H - I - higlight report to issue | K - Kaizen to Kano | L - lead time to Little's Law | M - manage by exception to MoSCoW | P - Plan-Do-Check-Act to push system | Q - quality assurance to quality tolerance | R - RACI to risk register | S - SAFe to supplier subject matter expert | T - team dynamics to transparency | U - V - user story to visioning | W - Waterfall method to workshop
lead time/cycle time
Interpreted differently by many in the Kanban community (some see these two terms as representing different things) but in simple terms it refers to how long a work item takes to go through the system or timebox.
Lean
An approach that focuses on improving processes by maximizing value through eliminating waste (such as wasted time and wasted effort).
lean start-up
Originally an approach to creating and managing start-up companies, but now applied to any business, to help them deliver products to customers quickly.
lessons report
A report that documents any lessons that can be usefully applied to other projects. The purpose of the report is to provoke action so that the positive lessons from a project become embedded in the organization's way of working and the organization is able to avoid the negative lessons on future projects.
level of quality
The overall quality level of a product as defined by the project product description (customer's quality expectations and acceptance criteria).
Little's Law
L = λW
In simple terms – the average number of items in a system: L is equal to the average arrival rate, λ, multiplied by the average time an item spends in the system, W (assuming that this is over a long enough period of time and the system is stable).
Copyright © AXELOS Limited 2012. All rights reserved. Material is reproduced with the permission of AXELOS