A simple Google search on ‘agile’ will reveal lots of information about agile. The information in this section is designed to provide a high-level overview. Transformation teams are formed and led by a digital/business transformation manager who is experienced in working in an agile environment. Their role is to guide teams through the process.
What is agile?
Agile is not a software methodology, process, scrum, stand-ups, sprints, boards, post-its or sharpies. Agile is a collection of values, practices and behaviours enabling teams to build services (or things) iteratively, delivering early and often.
What happens in an agile environment?
In an agile environment, multi-disciplinary teams are co-located, self-sufficient, empowered and responsible for the delivery. Collectively they develop empathy for their users and continue to work with them until the user needs are met.
To help develop the prototype and then build the minimum viable product, the team will define a list of user stories which collectively form a product backlog. User stories are a way of organising user requirements into manageable chunks. Each week these user stories are prioritised and planned into the sprint and entered into the sprint backlog.
The agile operating model
During Discovery and Alpha phases, the team will operate on a one week time period known as a sprint. Beta can operate in either one week or two week sprint cycles. Throughout the sprint, the team will work through the following agile ceremonies.