1

The Agile Manifesto• We are uncovering better ways of developing software by doing it and helping

others do it. Through this work we have come to value:

• Individuals and interactions over Processes and tools• Working software over Comprehensive documentation

• Customer collaboration over Contract negotiation• Responding to change over Following a plan

• That is, while there is value in the items on the right, we value the items on the left more

• © 2001 Kent Beck, James Grenning, Robert C. Martin, Mike Beedle, Jim Highsmith, Steve Mellor,• Arie van Bennekum, Andrew Hunt, Ken Schwaber, Alistair Cockburn, Ron Jeffries, Jeff Sutherland,

• Ward Cunningham, Jon Kern, Dave Thomas, Martin Fowler, Brian Marick

Agile principles

1. Customer satisfaction by rapid delivery of useful software2. Welcome changing

requirements, even late in development

3. Working software is delivered frequently (weeks rather than months)

4. Working software is the principal measure of progress

5. Sustainable development, able to maintain a constant pace

6. Close, daily cooperation between business people and developers

7. Face-to-face conversation is the best form of communication (co-location)

8. Projects are built around motivated individuals, who should be trusted

9. Continuous attention to technical excellence and good design

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

11. Self-organising teams

Customer satisfaction by rapid delivery of useful software

Working software is delivered frequently

12. Regular adaptation to changing circumstances

Working software is deliveredfrequently, and is the principle measure of progress

4

5

6

7

8

9

10

11

Know thy user…

12

Know thy user…

13

...and you are not thy userArnie Lund ”Know thy user…“

14

Your Digital Thing

15

Your Digital Thing

16

A Digita

l ThingObjectives

17

A Digita

l Thing Requirements

Objectives

18

A Digita

l Thing Requirements

Objectives

What is the problem?

19

A Digita

l Thing Requirements

Objectives

What is the problem?

Who is it for?

20

A Digita

l Thing Requirements

Objectives

What is the problem?

Who is it for?

What does success look like?

21

22

23

DSS?BUGGER

24

“ ”

Tenderers must demonstrate how they will

comply with the Digital Service Standard

25

A Digita

l Thing

Objectives

26

A Digita

l Thing

Objectives

● Vision● Distilled goals● Prototype

(alpha)● MVP (beta)

27

A Digita

l Thing

Co-creation

Objectives

● Vision● Distilled goals● Prototype

(alpha)● MVP (beta)

28

A Digita

l Thing

Businessowners Specialists Your users

Co-creation

Objectives

● Vision● Distilled goals● Prototype

(alpha)● MVP (beta)

A Digital Thing

Discovery Validation Discovery Validation

Objectives

● Vision● Distilled goals● Prototype

(alpha)● MVP (beta)

30

31

Discovery

The life of the project

32

Research Validation

Design and IA

HTML and Prototyping

Solution

The life of the project

33

Discovery

Research Validation

Design and IA

HTML and Prototyping

Solution

Research - TypesPoint in time:

Desktop

Interviews

Workshops

Surveys

Analytics

34

Research across time:

Analytics

Ongoing research

Research - ReportingBusiness objectives & strategies

Content strategy

KPI’s & assessing success

Branding restrictions

Technical restrictions - actual

User groups

Personas

Demographics

User journeys 35

Discovery

The life of the project

36

Research Validation

Design and IA

HTML and Prototyping

Solution

Validation - Design and IAInterviews

Workshops

White sites

Analytics

Digital tracking

Heatmaps

Eye tracking

37

Validation - HTML and PrototypingSurveys

Interviews

Digital tracking

Heatmaps

Eye tracking

38

Discovery

The life of the projectWhat is it?

We have finished, right?

39

Discovery Validation

Design and IA

HTML and Prototyping

Solution

NO

40

Discovery

41

Research

Validation

Design and IA

HTML and Prototyping

Solution

42