The agile42 Approach

Best practice to introduce Scrum, Kanban & lean thinking

agile42 features a tailored approach changing your company to an agile and lean method of working.

We recognize that your organization and culture is unique, which implies a unique implementation of any new methodes like Scrum, Kanban and XP Practices like Testing, Pairprogramming etc..

Our efficient combination of management consulting, knowledge transfer, team training and coaching on the job and a practice based tool support will be the basis for your success as well as for many other international agile42 customers.


From the Sprint Planning Meeting to the Retrospective – A Scrum

Scrum Projects are divided into iterations, which are called Sprints. They usually have a Time Box of two or four weeks.

At the beginning of such a Sprint the Product Owner presents, at the Sprints Planning Meeting, the prioritized Product Backlog, a list of all the requirements or as the case may be User Stories. The team now needs to ask questions in order to find out what conceals behind the professional demands and estimates roughly the effort. In contrary to the classical projects, the Scrum Team is not told how many features they should realize in a certain amount of time, instead it chooses which functionalities can be permuted in one sprint and they commit themselves to realize these.

In the second part of the Sprint Planning Meetings only the Scrum Master and the team participate. There they split the User Stories into several tasks and record those in the Sprint Backlog. They are provided daily with the description of the remaining effort. From this description emerges the always current Burn-down Chart.

During the running iteration the Sprint Backlog won’t be expanded, in order to not jeopardize the completion of the arranged User Stories. More what is finished in the end, and finished by Scrum means tested and documented, can be taken by the Product Owner in the so called Review Meeting. Common statements as “I’m ready for 80%” don’t exist anymore.

During a sprint the team works concentrated and undisturbed on the tasks of the Sprint Backlog until they are done. It daily meets for a “timeboxed” Meeting of 15 minutes, the Daily Scrum Meeting. Here they usually talk about the following things:

  • What did I accomplish yesterday
  • What will I do and achieve today
  • Are there any problems

At the end of the sprint the team presents at the Sprint Review Meeting to the Product Owner the implemented functionalities. The Product Owner then decides whether he takes the delivery and if all the acceptance-criteria are fulfilled.

The Scrum Master takes care that during the entire process the rules are kept and that there do not appear any extraneous disturbances.

The Retrospective Meeting in the end serves as a reflection in respect of how good or bad everything worked and whether the process should be adjusted and what needs to be changed in the next Sprint.

Agilo™for Scrum

The next generation of Agilo for Scrum addresses the needs of each scrum role by providing an intuitive workflow that facilitates the ceremonies of the scrum process, and by exposing simple interfaces for managing the scrum artifacts.

Scrum Implementation

agile42 has helped a lot of companies to introduce Scrum successfully. Agilo is based on these experiences. More about our consulting and training approach and some references are available here:

Scrumtisch Berlin

The Scrumtisch Berlin is an official SCRUM USER GROUP. Every 4-6 weeks we meet, talk, discuss, to exchange information on experiences and of course have a lot of fun.

 Scrum User Group Berlin sponsored by agile42

You can find more information on the Scrumtisch Website