Agile and Lean Service Management Fundamentals
Agile and Lean Service Management Fundamentals
Agile and Lean are the two intellectual roots of Agile Service Management, and this domain tests whether you can apply their principles to a service context rather than recite them.
Agile: values and principles applied to services
The Agile Manifesto's four values favour individuals and interactions, working software, customer collaboration and responding to change over their counterparts - while the statement insists the right-hand items still have value. The twelve principles add cadence, technical excellence, simplicity and self-organising teams. For services, 'working software' generalises to a working service: something a consumer can actually use to get value.
Lean: value, waste and flow
Lean starts from the customer's definition of value. Anything that does not change the form, fit or function of what the customer receives, or that the customer would not pay for, is waste (muda): waiting, handoffs, rework, over-processing, partially done work, motion, inventory and defects. Lean thinking also supplies flow (work moves without queues), pull (work starts because capacity is free, not because a schedule says so) and perfection (continuous improvement). Deming's PDCA and the Theory of Constraints - improve the bottleneck - are the standard improvement engines.
Services as value co-creation
A service is a means of delivering value by facilitating outcomes the customer wants, without the customer owning specific costs and risks. Value is co-created: the provider's outputs only become value when the consumer uses them. That is why service management assesses utility (fit for purpose) and warranty (fit for use) together.
Worked example
A team's standard change takes nine working days end to end, of which only two hours is actual work. The team proposes buying a faster tool. Reasoning: two hours of work inside roughly 72 hours of lead time is about 3% flow efficiency, so the constraint is queueing and approvals, not execution speed. A faster tool attacks a non-constraint and improves almost nothing. The Lean answer is to remove wait states and handoffs - pre-authorised standard changes, automated checks, parallel rather than serial approval - because that is where the nine days actually sits.
Traps that cost marks
Assuming Agile means no documentation or no controls; treating Lean as cost-cutting rather than waste removal; presenting Agile and Lean as alternatives rather than complements; and answering 'add people' or 'buy a tool' when the evidence points to queues.