# Agile Project Management

{% embed url="<https://marsdd-1.wistia.com/medias/9c0g82aho6>" %}
Fundamentals of Agile by Neda Tocheva
{% endembed %}

## Agile vs. Waterfall

**Waterfall:** A traditional project management approach where there are distinct stages of each phase of development. Usually the next stage cannot begin until the previous one is completed. This methodology allows for less flexibility but is predictable and can time box each member’s contributions.

**Agile:** An iterative and team-based approach that involves rapid construction and iteration across the development lifecycle. Agile works best when members of the development team are completely dedicated to the project and when they are located in the same space.

![Source: https://www.seguetech.com/waterfall-vs-agile-methodology/ ](/files/-Ll2NC6Olpl8VXaTzhUv)

Agile project management is most commonly used in software development; however, it can be used in social innovation lab processes. See below for more as inspiration or input for your lab.

## Examples and Resources

{% tabs %}
{% tab title="Agile Principles" %}
The following describes the fundamental principles of *agile methodology* (as it pertains to the software sector):

* Early and continuous delivery of valuable software
* Welcome change requirements even late in development
* Deliver working software frequently
* Business people and developers working together daily
* Build projects around motivated individuals and trust them to get the job done
* The most effect method of convening information is face-to-face conversation
* Working software is the primary measure of progress
* Sustainable development: maintain a constant pace indefinitely
* Continuous attention to technical excellence
* Simplicity: maximize the amount of work not done
* Teams self-organize
* Teams regularly reflect and adjust behaviour
  {% endtab %}

{% tab title="Sprint Planning " %}
The goal of *sprint planning* it to deliver value on a project, in specific chunks of time (eg. every two weeks).

This is followed by a reflection and a reorganization of upcoming sprints to account for team changes, task delays, and items that are ahead-of-schedule.

![Source: https://www.umassmed.edu/it/who-we-are/it-news/2014/september1/agilescrum-framework/ ](/files/-Ll2R8MxY3_4zPbIScUj)
{% endtab %}

{% tab title="Scrum Task Board" %}
Teams often choose to use a physical task board (ie. *scrum board*), tracking progress visual in the project room. Task boards can also be digital, to include remote working members and for easier sharing.

![Source: https://manifesto.co.uk/agile-concepts-scrum-task-board/](/files/-Ll2RBhbW8QnYymcPOt8)
{% endtab %}
{% endtabs %}

{% hint style="info" %}

### Additional Resources

Lotz, M. (2018). *Waterfall vs. Agile: Which is the Right Development Methodology for Your Project?* Segue Technologies. [https://www.seguetech.com/waterfall-vs-agile-methodology/
](<https://www.seguetech.com/waterfall-vs-agile-methodology/&#xD;&#xA;>)
{% endhint %}

###

###


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://mars-solutions-lab.gitbook.io/living-guide-to-social-innovation-labs/being/value-of-social-innovation-labs/agile-project-management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.