Introducing the Agile Manifesto for Development Cooperation

For many who work in the development cooperation field, there is a strong reason why they have chosen this field of work. There is something that motivates us and drives us to do it. Most commonly, it is the desire to change things in the world for the better. Whether it is improving education, reducing the risk of conflict, improving child healthcare, increasing democratic accountability, or something else, the underlying reason remains. Development cooperation is about making a positive impact on people and communities.However, development cooperation is not easy. It is full of ups and downs, joys and frustrations, and of feeling that we could do more and better.What if there were tools available to help us do things better? What can we alter in terms of how we work and understand our work to achieve greater impact? How do we create an environment where we think about impact and act on this with more focus? How do we reinvigorate this spirit of development?Becoming an agile organization could be the way. This means challenging some well-established bottlenecks and reflecting on what is really important that both donors and beneficiaries [1] start addressing. Working agile is far more than a management method; it is a combination of mutually supporting values and frameworks.

What is it that we want to change?

Just like at the beginning of the millennium with the start of the agile movement, identifying points of orientation is one of the most important elements in a change process. The points of orientation help us identify common challenges and pain points, which conversely help us define commitments about how to do things differently. The ‘original’ Agile Manifesto did just that in software development. It laid out the commitments through which teams and entire organizations working in the field have a guiding light explaining what is it that they are working towards. For example, the Agile Manifesto notes that working software takes precedence over documentation. This means that the focus of the team is ensuring that working software is produced. Documentation is however not unimportant, rather immaculate documentation does not in itself deliver value. Therefore having complete documentation on software that does not work is pointless. To build on this example, value is in the software that works, and that has its users.Inspired by the original Agile Manifesto, the Agile Manifesto for Development Cooperation is an attempt to focus on what is really important in development cooperation. In software development, the focus is on creating value. In development cooperation measuring financial benefit (or value) is often difficult, but also often not the direct aim of the discipline. Instead, the focus is on delivering development impact, which can lay the groundwork for sustainable economic growth. The value proposition behind the Agile Manifesto for Development Cooperation is, therefore, supporting organizations engaged at all levels of development cooperation in delivering impact for those groups and communities that are underrepresented, marginalized or discriminated in some way.The four points that the Agile Manifesto for Development Cooperation puts forward are as follows:

  1. Flexible scope enabling responding to change over immaculately planned projects
  2. Forming cross-cutting alliances over remaining in ‘my field’
  3. Fostering learning organizations over reporting project outcomes
  4. Building relationships over following procedures

In short, the first point, flexible scope enabling responding to change over immaculately planned projects, puts focus on having the ability to adapt to the environment we are in. It is not arguing that projects should not be planned; they should. But planning them in detail will not necessarily make them more impactful. Indeed, they are more likely to run into trouble because a plan from six months ago may not match today’s reality.The second point, forming cross-cutting alliances over remaining in ‘my field’, builds on the established idea of promoting integrated solutions in development cooperation. It also adds the idea that we can reach out to a broader audience with the work that we do. The point, however, is not to try becoming experts in everything.The third point, fostering learning organizations over reporting project outcomes, argues that organizations, just like individuals, improve their skills by learning. Reporting remains a part of the development cooperation cycle, but the focus should not be on writing a report at the end of a project cycle. Rather it should be on iterative learning about the field we are working in as well as improving as an organization.The fourth point of the Agile Manifesto for Development Cooperation is building relationships over following procedures. The focus here is on the challenges faced across the field that have a massive influence on the impact. For example, a challenge can sometimes be fulfilling huge administrative overheads to ensure donor compliance. This can make access to funds impossible for some organizations and initiatives, while not necessarily guaranteeing that funds will be spent as designated and real impact will be achieved. Instead, the focus should move away from developing and enforcing standardized procedures to building relationships, which will reduce administrative burden and also help in exchanging knowledge needed to ensure greater impact.

Is the Agile Manifesto for Development Cooperation worthwhile?

It’s worth asking whether the original Agile Manifesto made a difference. The short answer is yes. It has become a reference point for many organizations looking to understand how they can be more effective and focused in what they do. The ‘problem’ with the original Agile Manifesto is, however, that it only really makes sense in one particular field, which is software development, and that it is only a manifesto.Development cooperation is an entirely different beast and consequently has very different pain points that being agile can address. This desire to provide a guiding light on how to create more impact in development cooperation has been an inspiration for developing the Agile Manifesto for Development Cooperation. But the manifesto still only remains a manifesto. This takes us back to the beginning of the blog, where mutually supporting values and frameworks are mentioned as a way of working and being agile. The manifesto in this sense presents a vision of where we want to be. Agile methods, like Scrum, on the other hand, provide the building materials for the road that can take you there.[1] Donor and Beneficiary are terms used without prejudice to the geographical location of the legal subject. They are merely there to describe the flow of funds in development cooperation.

Change
Soziale Innovation
Tihomir Vollmann-Popovic
June 26, 2019

Table of content

Diesen Beitrag teilen

Das könnte auch interessant sein:

Agile Coach
Agile Management
Agile Organization
Agile Prinzipien
Agile Toolbox

FRAGE: Warum macht ihr eigentlich kein SAFe?

Agile Management
Agile Organization
Agile Prinzipien
Agile Toolbox
Transformation

FRAGE: Was kostet eine agile Transformation?

Agile Management
Agile Organization
Agile Toolbox
Leadership
Agiles Lernen

FRAGE: Welche Rolle spielt Training?

Agile Coach
Agile Management
Agile Organization
Agile Prinzipien
Agile Toolbox

FRAGE: Wer sind die Top 10 agilen Unternehmensberatungen?

Agile Management
Agile Organization
Agile Tools
Agiles Management
Leadership

FRAGE: Wie viel bringt die Investition? Was ist der Business Case dahinter?

Agile Management
Agile Organization
Agile Prinzipien
Agile Toolbox
Führung

FRAGE: Welche sind häufige Herausforderungen, die ihr beim Kunden löst?

Agile Management
Agile Organization

FRAGE: Warum sollten wir mit borisgloger arbeiten?

Agile Management
Agile Organization
Agiles Management
Transformation

FRAGE: Wie viel kostet eine Beratung und ist es wirklich rentabel bei borisgloger?

Agile Prinzipien
Agile Toolbox
Projektmanagement

The Lie Behind the Parable of the Golf Balls and the Jar

Video
Change
Digitale Transformation
Hardware
Agile Organization

Agile in Industrial Automation: The Digital Transformation of Yokogawa

Versicherung
Neues Arbeiten
Führung
Agile Prinzipien
Kundenfokus

Kundenzentrierte Versicherung: Kann ein agiles Projekt die Organisation retten?

Versicherung
Change
Digitale Transformation
Agile Prinzipien
Kundenfokus

Agilität in den Vertrieb bringen – für Versicherer sinnvoll

Versicherung
Agile Prinzipien
Kundenfokus
Agile Toolbox
Produktentwicklung

BizDevOps in der Versicherungsbranche – Wie multidisziplinäre Teams wirklich besetzt sein sollten

Versicherung
Agile Prinzipien
Kundenfokus
Neues Arbeiten
Meetings

Undercover Agile für Versicherer: 5 agile Praktiken für Ihr klassisches IT-Projekt

Versicherung
Change
Digitale Transformation
Agile Prinzipien
Kundenfokus

IT-Projekte in der Versicherungsbranche – Das Rennen um die Time-to-Market

Team
Neues Arbeiten
Agile Prinzipien
Selbstorganisation
Social Skills

Umgang mit Fehlern & Diversität – Erfolgreiche agile Teams #2

Team
Neues Arbeiten
Agile Toolbox
Produktentwicklung

Das Geheimrezept von High-Performance-Teams

Team
Arbeiten bei borisgloger consulting
Agile Prinzipien
Freiwilligkeit
Selbstorganisation

Konsent und offene Wahl: 2 Prinzipien aus der Soziokratie, die jedes agile Team gebrauchen kann

Team
Neues Arbeiten
Meetings
Social Skills

Der agile Adventkalender

Team
Agile Toolbox
Scrum
ScrumMaster-Praxistipps
Agile Prinzipien

Selbstorganisation der Teams fördern: Ask the team!

Team
Agile Toolbox
Design Thinking

Who Recognizes the Truly Good Ideas?

Team
Agile Organization
Transformation

Pizza Is Not Dead, and Neither Is Agility

Scrum4Schools
Neues Arbeiten
Führung
Life
Social Skills

Trauen wir unseren Kindern mehr zu – auch in der Schule!

Scrum4Schools
Change
Agiles Lernen
Neues Arbeiten
Remote Arbeiten

Eine Scrum4Schools-Projekt-Rückschau mit Physiklehrer Ivan Topic

Scrum4Schools
Mehr Formate
Interview
Nachhaltigkeit

Mit Scrum4Schools dem Weltraum auf der Spur

Scrum4Schools
Change
Agiles Lernen

Scrum4Schools - ein Projekt nimmt Fahrt auf

Scrum4Schools
Agile Schulentwicklung
Agile Toolbox

Technik im Alltag - Scrum4Schools zu Gast in Langenzersdorf

Projektmanagement
Agile Toolbox
Scrum
Scrum-Begriffe
ScrumMaster-Praxistipps

Sprechen Sie Agile? Den klassischen Projektplan in die agile Welt überführen

Projektmanagement
Agiles Management
Agile Toolbox
Scrum
Enterprise Scrum

Das Management in Scrum

Projektmanagement
Change
Digitale Transformation

Agilität in der Logistik oder: Liefern wie Amazon

Projektmanagement
Agile Toolbox
Scrum

Meilensteine und Scrum

Portfoliomanagement
Project management

Too many projects? Portfolio management simplified

Neues Arbeiten
Mehr Formate
Agile Toolbox
Scrum
Scrum Values

Wie agiles Arbeiten die Kommunikation aus der Selbstverständlichkeit holt

Neues Arbeiten
Change
Agiles Lernen
Mehr Formate
Audio

New Learning heute für das New Work von morgen – mit Angelika Weis

Neues Arbeiten
Change
Soziale Innovation

New Work Experience 2019 – ein Erfahrungsbericht

Neues Arbeiten
Audit
Change

Agil im Audit: das Starter-Kit

Neues Arbeiten
Agile Toolbox
Scrum
Scrum4Schools
Agile Prinzipien

Scrum4Schools: Lernen für die Zukunft

Neues Arbeiten
Agile Toolbox
Scrum
Scrum Meetings
Retrospektive

Arbeiten wir uns gesund!

Neues Arbeiten
Agile Toolbox
Scrum
ScrumMaster-Praxistipps

Who should be in (agile) HR?

Neues Arbeiten
Agile Toolbox
Scrum
Scrum Values

Glauben Sie an die Seele Ihrer Firma?

Neues Arbeiten
Agile Toolbox
Scrum
Product Owner
ScrumMaster-Praxistipps

Produktivität auf Irrwegen: "Führen wir schnell mal Scrum ein!"

Neues Arbeiten
Agile Prinzipien
Selbstorganisation
Social Skills
Team

Freiwilliges Teilen von Wissen – Erfolgreiche agile Teams #5

Neues Arbeiten
Agile Prinzipien
Selbstorganisation
Social Skills
Team

Doing vs. Being Agile – Erfolgreiche agile Teams #1

Neues Arbeiten
Agile Prinzipien
Selbstorganisation
Social Skills
Team

Freude bei der Arbeit & Sustainable Pace – Erfolgreiche agile Teams #3

Neues Arbeiten
Agile Prinzipien
Selbstorganisation
Social Skills
Team

Anpassungsfähigkeit & schonungslose Offenheit – Erfolgreiche agile Teams #4