Last week I followed an APMG ATO / trainer briefing regarding Agile digital Services.
This agile framework, developed by Agile Business Consortium, focusses on building and delivery of digital services. The AgileDS framework will help organizations to develop a consistent agile approach, a common language and a skilled workforce regarding digital services. It uses the same terminology as other agile frameworks. It is based on the GDS lifecycle (Government Digital Service, UK), themes and responsibilities have evolved from the roles and responsibilities in AgilePM and its agile practices come from other existing frameworks (e.g. WSJF from SAFe).
To create this quick reference Card I used the handbook that is available for feedback (beta phase). To download the QRC: AgileDS (QRC, 180718) v1.0
Generic and governance principles
The ten generic principles are:
- Start with needs
- Do less
- Design with data
- Do the hard work to make it simple
- Then iterate again
- This is for everyone
- Understand context
- Build digital services, not websites
- Be consistent, not uniform
- Make things open: it makes things better
The six governance principles are:
- Don’t slow down delivery
- Decisions when they’re needed, at the right level
- Do it with the right people
- Go see for yourself (GEMBA)
- Only do it if it adds value
- Trust and verify
There are five phases discovery, alpha, beta (privat and public), life and service retirement which can be tailored to meet the needs of different organizations. The aim is to deliver incrementally within each phase with a significant delivery at the end of a phase.
The following products are described (purpose, when created, updated, needed): Terms of Reference, Business Case, Backlog, Roadmap, Service Architecture Definition, Development Approach Definition, Management Approach Definition, Delivery Plan, Service Lifecycle Transition Report.
Themes and responsibilities
AgileDS defines a set of responsibilities that are collected into simple themes. All responsibilities must be covered and it’s vital that the team acts as a collaborative and effective whole, with clarity about individual responsibilities. Within the Service Delivery Team the following responsibilities must be covered: service ownership, delivery management, product management, business analysis, service development, user research, technical design, service assurance, service design and service deployment.
When needed specialist guidance should be available: assisted digital guidance, accessibility guidance, performance analysis and agile coaching.
Within Steering and Leadership we encounter the following responsibilities: business sponsorship, service ownership, technical leadership and change coordination (in case of multiple service delivery teams).
Several techniques are explained: Kano method, relative prioritization, stack ranking, MoSCow prioritization, WSJF, iterative development and incremental delivery, MVP and MMP, requirements and user stories, user research and personas, timeboxes and sprints.
Where AgilePM is there for the delivery of a product or service (temporary agile project, using a project lifcycle), AgileDS is there for the delivery and the continuous operations, support and maintenance of that service (permanent agile delivery team, using the product/service lifecycle). There will be a foundation and a practitioner certification in line with other APMG certifications.
In the next picture I have positioned AgileDS.