SHARING MEANS CARING – knowledge is growing when it’s shared

Video: Scrum does not equal AGILE (Aino Corry)

tldr: Instead of looking only at these 4,  have a look at the 12 principles.

In this video, Aino Corry points out that all the great ideas behind the Agile Manifesto, which was written in 2001 at a snow/ski resort in the mountains of Utah (AgileManifesto.org) and that most of the time these good ideas got reduced to the 4  which leads to so many misunderstandings. In both directions.

 

This talk resonates with me so badly, how often did I hear these: „Barbara, we are so sorry but we are not agile, because we do planning“. Or, the other way around: „No, we don’t have sprint goals, cause we don’t work with deadlines“

 

Manifesto for Agile Software Development

 

 

12 principles behind the Agile Manifesto:

# 1 Our highest priority is to satisfy the customer through the early and continuous delivery of valuable software.

# 2 Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.

# 3 Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

# 4 Business people and developers must work together daily throughout the project.

# 5 Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

# 6 The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

# 7 Working software is the primary measure of progress.

# 8 Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

# 9 Continuous attention to technical excellence and good design enhances agility.

# 10 Simplicity–the art of maximizing the amount of work not done–is essential.

# 11 The best architectures, requirements, and designs emerge from self-organizing teams.

# 12 At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.

 

I don’t want to spoil more…. just watch the video yourself:

Kommentare

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert