Zum Inhalt springen
A-Ops

All playbooks

Starting Agile Transformation

The first 90 days of an agile transformationThe first 90 days of an agile transformationThe first 90 days of an agile transformationThe first 90 days of an agile transformation

8 to 12 weeks · 6 steps

Goal

An agile transformation doesn't start with tools, but with understanding and conviction. This playbook guides you through the critical first 90 days: from an honest as-is analysis through winning sponsors to the first pilot team. With a clear focus on quick wins and a realistic scaling plan.

Steps over the weeks

  1. Weeks 1 to 2About 10 working days

    Carrying out an as-is analysis

    Assess the organization's current maturity with regard to agility. Take stock: Which agile practices already exist? Where is there resistance? What structural obstacles are there? Document everything honestly and without sugarcoating.

    Results

    • Agility maturity assessment
    • Stakeholder map with supporters and skeptics
    • Structural obstacles and dependencies
    • Documentation of the current state

    Tips

    • Use anonymous surveys to get more honest feedback.
    • Look for agile islands that already exist in the organization.
    • Distinguish between real obstacles and pretexts.

  2. Weeks 3 to 4About 7 working days

    Building vision and sponsorship

    Develop a clear vision for the transformation and secure the support of the leadership level. The vision must answer: Why agile? What will get better? The sponsor must be willing to actively stand up for the transformation and clear obstacles out of the way.

    Results

    • Transformation vision (one-pager)
    • Executive sponsor with formal commitment
    • Communication plan for the organization
    • FAQ document for common questions and concerns

    Tips

    • Phrase the vision in business outcomes, not in agile buzzwords.
    • The sponsor should be seen backing the transformation regularly.
    • Prepare answers to the typical objections.

  3. Weeks 4 to 5About 5 working days

    Putting together the pilot team

    Select a team for the pilot. Ideally a team that is motivated and has a manageable workload. Make sure the team brings all the necessary skills and is supported by an experienced agile coach.

    Results

    • Selected pilot team with a team charter
    • Agile coach (internal or external) appointed
    • Workspace and tools for the pilot team
    • Clear success criteria for the pilot

    Tips

    • Choose volunteers, not conscripts. Motivation is decisive.
    • The pilot team should be cross-functional.
    • Protect the pilot team from disruptions coming from the line organization.

  4. Weeks 5 to 6About 5 working days

    Choosing and adapting the method

    Choose the agile method that suits your context. Scrum, Kanban or a hybrid model: the choice depends on the type of work, the team size and the organizational culture. Adapt the framework to your reality instead of squeezing the organization into a framework.

    Results

    • Selected method with rationale
    • Adapted framework handbook for the pilot team
    • Role definitions (Product Owner, Scrum Master, etc.)
    • Meeting cadences and artifacts

    Tips

    • Lean towards starting with Kanban if your team has a lot of unplanned work.
    • Avoid too many ceremonies at first and start with the minimum.
    • Document deliberate deviations from the standard framework with a rationale.

  5. Weeks 6 to 9About 15 working days

    Delivering quick wins

    Identify and deliver visible improvements within the first 30 days of the pilot. Quick wins create credibility and momentum for the transformation. Actively communicate successes to the organization.

    Results

    • At least 3 documented quick wins
    • Before/after comparison with metrics
    • Success stories for internal communication
    • Feedback summary from the pilot team

    Tips

    • Choose quick wins that are visible and understandable to outsiders as well.
    • Measure before and after the change to quantify the effect.
    • Let the pilot team report on its experiences itself.

  6. Weeks 9 to 10About 7 working days

    Developing a scaling plan

    Based on the pilot team's experience, develop a plan for scaling to further teams. Define the order, pace and support structures. Take into account organizational dependencies and cultural differences between departments.

    Results

    • Scaling plan with schedule and order
    • Capacity planning for agile coaches
    • Training concept for further teams
    • Adapted framework based on pilot learnings

    Tips

    • Don't scale too fast. One team per month is a good pace.
    • Use members of the pilot team as multipliers in new teams.
    • Schedule regular community of practice meetings for all agile teams.