---
# System prepended metadata

title: Agile with a Contract?

---

# Agile with a Contract?
12:00 Session at Productcampberlin.org


**bit.ly/PcAgileContracts**

Scenarios:
- project deadlines 
- marketing / sales | expectations / reality
- porject based enviroments
- customer expectations
- Agile vs X
- fixed price
- b2b customers / working with large companies
- competing for tenders
- interdepartment relations
- buzzwordification

![Uploading file..._eztpxjiiq]()




## Types of Agile Contracts
(Possible conflicts  in bold)

![](https://www.scaledagileframework.com/wp-content/uploads/2015/10/Fig-1-A-range-of-traditional-contract-types.png)
Source: https://www.scaledagileframework.com/agile-contracts/


## [12 Agile Principles](https://www.agilealliance.org/agile101/12-principles-behind-the-agile-manifesto/)
1
Our highest priority is to satisfy the customer through **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 behavior accordingly.
