How we deliver digital change, written down.
CoreMethods™, in a little more detail.
CoreMethods™ is our ISO 9001-certified methodology — a curated collection of the knowledge, experience and refined approaches we use to deliver digital change. It brings together best-practice methods across project management, agile delivery, software DevOps, IT architecture, design thinking and lean change management.
The Playbook is the framework that brings the right methods together in a structured way to deliver results for ourselves and our customers. It defines a consistent way of working — aligned to our quality standards — that applies to every project we are involved with, whether or not we own the outcome.
Four principles behind every engagement.
They guide what we deliver for our customers and keep us consistent with each other — and with them — on every project.
People + Design
Value + Pace
Accountable + Agile
Transparent + Engaging
An industry-standard set of phases, mapped to how we deliver.
Each phase has a specific objective and set of deliverables. Together they give project teams a systematic, controlled progression through the lifecycle.
The methods that feature on most projects.
A short introduction to some of our most-used methods — mandatory in the PMF, or simply hard to avoid. Open one for the full write-up, rubric and template.
A tool used to capture a description of a software feature from an end-user perspective. User stories describe the type of user, what they want, and their expectation.
A structured, holistic human-centred design approach for planning and organising the interaction and interoperability between the people, technology and processes that deliver a service.
A timeboxed period in which the team works to achieve a Sprint Goal. For our projects a Sprint is two weeks, and follows immediately on from the last with no downtime in between.
To estimate the effort a project requires, each unit of work — captured as a User Story — is sized relative to the others using story points rather than absolute time.
A shared understanding between the team and stakeholders of what it means for a unit of work to be considered complete. Agreed up front, with everyone, so there is no ambiguity.
A tool derived from lean manufacturing, associated with the Lean software development branch of agile practices. Like a task board, it visualises work in progress and limits it to expose bottlenecks and smooth flow.