Agile transition for teams

We start with training to introduce Scrum or Kanban to each team. We then support your team through their first change steps via feedback and coaching. Together with your teams, we develop a set of rules, structures and values ​​that support the sustainable and continuous improvement of agile practices.

Our Implementation Approach

We have successfully introduced Scrum into many organizations using the improuv process model.

Step 1  - Assessment Workshop

For the first step we propose a workshop where we introduce the principles of scrum, clarify open questions and identify implementation opportunities.

  • What is Scrum, how does it work, what are the advantages of Scrum?
  • What are the objectives and expectations and how do these connect the team with Scrum?
  • What is the impact of Scrum on teams and roles?

Participants of this workshop may be future Scrum Masters or Product Owners, in addition to other interested managers and stakeholders.

Step 2 - Scrum Implementation and Training

Before the start of the first sprint we help the team become familiar with the processes of Scrum, prepare the product backlog and define ways-of-working for the first sprint.

Through coaching and workshops:

  • Prepare the intial Product Backlog with the Product Owner
  • Create a team charter and definition of done with the team
  • Carry our initial rough estimation and grooming of the Product Backlog with the Product Owner and the team
  • Assist the Product Owner and Team reach a first prioritization of the Product Backlog

Step 3 - Start Sprint 1 - Coaching

The first Sprint begins with the Sprint Planning Meeting. During this meeting we support the Scrum Master, Product Owner and Team though moderation, advice, tools and tips. We then coach at the Daily meetings and support the team throughout the Sprint. At the end of the Sprint we help facilitate the Sprint Review and assume the moderation role in the first Sprint Retrospective.
It is important to note that this step requires the intensive support of the Product Owner, Scrum Master and team to ensure that all parties have a common understanding of Scrum from the start in order to ensure a successful implementation.

Step 4 - Coaching in the initial sprints

During this phase we provide continued coaching support in the Scrum Process, although normally at a lowering intensity as the team begin to build their fluency in Scrum. In this phase the Product Owner, Scrum Master and team often need coaching support during the key ceremonies such the Sprint Planning Meetings, Reviews or Retrospectives.

Step 5 - Health Check

At the of a “Test Period” we recommend a feedback round where the decision makers, Product Owner and team to discuss their experiences, identify important improvements and necessary changes to the process. Our Scrum Coach prepares, facilitates and provides follow-up to this meeting.
After the Test Period our Coach can take on the role of Interim Scrum Master or act as an internal Scrum Coach for a given period.

We are happy to discuss your needs and make a non-binding offer for the implementation of Scrum into your organization.

References: Scrum for the RMC Project, T-Systems