Agile Methods‎ > ‎

Scrum Agile Experiences

Scrum Coach Experiences

A Scrum coach must explain and sell Scrum and convince people that Scrum is a successful approach when developing software application. Here some hints and links to often discuss aspects.
  • How is design and architecture done in a Scrum project. We suggest to read the articles of Martin Fowler such as 
    • Is Design Dead?
    • Does agility and TDD approach have an influence on the architecture of an application. We are convinced the answer is a sounding yes. See for example Inversion of Control - IoC is for us the evolution of the service locator implemented in our company and open source project apparatus services in 1994 and MDA framework (java) and .NET MDA framework in 2001 -, or Mocks approach and the discussion how they affect design decisions,
    • Does agility and TDD approach have an influence on how the team develop software. The answer is yes. See for example continuous integration and the statement "Nightly builds are for wimps" and how to develop and check-in
    • Scrum versus over methodologies? and the new methodology. Important for the discussion is to show people that some of these articles were almost written in the last millennium. This discussion is not new and hundreds of companies and projects have already successfully solved these problems.
A Scrum coach should also promote Scrum and his experiences through articles and conferences. See activities and speeches.

You can find information on web sites and blogs. Below a list of links.

Scrum Master Experiences

To be written

Product Owner Experiences

To be written

Scrum of Scrums

MedTech Company

To be written

GIS Company

This Swiss company started with the introduction of Scrum framework in their GIS configuration and tailoring applications. Later the company framework development was also moved to Scrum. The development teams were very positive with Scrum and enjoyed 
  • Working together, in the same office, on the same days to solve a problem and deliver an application. Before Scrum quite often individuals were realizing functions in the application without any interaction with other involved in the project. Additionally the senior project manager made all decisions without involving the team. These managers were experienced and did a very good job but the team members had no reasons to commit themselves to the project goals and milestones
  • Being able to use current approaches such as "Defect Driven Development", "Test Driven Development", pair programming, clean code, etc,
  • Team members can influence technical decisions, decide the detailed planning inside a sprint and provide feedback how to improve the project plan or the realized application
  • Filling the flow and having fun to work together to reach a goal. The realization that engineers can daily work with peers and do not have to write big documents tremendously increased the motivation of the team members
Once a critical mass of Scrum projects were underway the pressure on the higher management to adopt Scrum rules grew exponentially. The management wisely realized the situation and started an initiative to introduce Scrum of Scrums in the company. The duration between the start of the first Scrum project and the start of the Scrum of Scrums initiative is one year.

Telecom Company

To be written

Software Services Company

This Swiss software services company made the transition from a plain RUP/USDP process to an agile Scrum approach.
Enterprise Scrum
To be written

TDD in Projects

To be written