When you are part of a new agile team, it can be hard to get started and see what to focus on. This simplified model suggests next steps for agile teams.
Where to start: read through the steps to understand at which level your team is roughly. Do not skip any steps that your team does not yet meet.
How to use: consider the next tree steps, and discuss in your team which one makes most sense for your team to try to achieve.
| Level | Step | Details |
|---|---|---|
| 0 | People have been brought together to act as a team. | An agile team is usually larger than 3 people, and smaller than 10 people. |
| 1 | Organise a Daily Scrum. | Plan to meet together Daily: for 15 minutes, on the same time, at the same place, with the full team. Use this time to plan the coming 24 hours of work together. Questions that can be utilised are:
|
| 2 | Visualise work in progress. | Collect all the work that the team is currently working on, and make it visible (either on a physical wall everyone has access to, or in a tool like Jira). An item should at least have a title, an assignee, and a requester. |
| 3 | Close items done with information to requester. | Make sure that any item of work that is completed, is marked as "closed" (on the wall or in the system) and that the person who requested the work is informed, so they can make use of the deliverable. |
| 4 | Visualise work requested. | Collect all the work that is requested from the team nearby the work in progress, to create a Product Backlog. Anyone is allowed to create a Product Backlog Item, but is required to connect with the team to make sure the item is seen & understood. |
| 5 | Appoint a person to prioritise work. | A team has a limited capacity to take up new work, so it is vital to pick up work that is most valuable at a moment. To achieve this, the Product Backlog should be organised with the most valuable items on top. This is done by the "Product Owner" in scrum, and the "Service Delivery Manager" in Kanban. |
| 6 | Escalate early. | When you need others who don't respond, when you lack input or system access, immediately share with your team and ask advice how to resolve this. If the problem is related to work, mark it with an impediment (Jira: "add flag with comment"). |
| 7 | ||
| 8 | ||
| 9 | ||
| 10 | ||
| 11 | ||
| 12 | ||
| 13 | ||
| 14 | ||
| 15 | ||
Working agreement in team Retrospective Working agreement cross team Working agreement cross train SLA Refinement Business case Acceptance criteria Story points Business value (Sprint) planning Testing Validation Definition of ready Definition of done Release procedure Project approval Stakeholder input Stakeholder presence Demo Peer review "spill over" Sprint goal Predictability Roadmap / quarterly planning | ||
| 100 |
Overview
Content Tools