AD_Topic_2

8/11/2019 AD_Topic_2

1/8

Topic 2 Approach and Principles Agile Development

V1.0 Visuals Handout Page 1

V1.0

Agile Development

Topic 2:

Approach and Principles

Approach and Principles Topic 2 - 2.2

Topic 2 Coverage

This topic will cover:

The Agile Manifesto

What is DSDM Atern?

V1.0

The philosophy and principles of DSDM Atern

When to use DSDM Atern


The Agile Manifesto We are uncovering better ways of developingsoftware by doing it and helping others do it.

Through this work we have come to value:- Individuals and interactions over processes and

tools

-

V1.0

www.agilemanifesto.org (2001)

documentation

- Customer collaboration over contract negotiation

- Responding to ch ange over following a plan

That is, while there is value in the items on the right,

we value the items on the left more

8/11/2019 AD_Topic_2

2/8




What is DSDM Atern?

An Agile Project Delivery Framework that deliversthe right solution at the right time

- Any kind of project

-

V1.0

- On-time and in budget

- Quality and rigour

- Incremental

- Collaborative


DSDM The History 1994/5 Dynamic Systems Development Method

(DSDM) was written as a Framework for Business

Centred Development

Focus on delivering on time and in budget

V1.0

It brought together best practices from the

combined experience of DSDM Consortiummembers, including many blue-chip companies

It was vendor-independent and became a standard,

worldwide


The History of DSDMAgile Manifesto signed(DSDM = signatory)

DSDM aMembers Onlyapproach

DSDM opened upand madefree to view

free to use

V1.0

1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005

DSDM V1

DSDM V2

DSDM V3

DSDM V4

DSDM V4.1

DSDM V4.2

Launched24 04 07

2006 2007 2008

V1 V2

8/11/2019 AD_Topic_2

3/8




The Structure of Atern

V1.0


The Philosophy of Atern - 1

Any project

V1.0

must be aligned to clearly defined strategic goals

must focus upon early delivery of real benefits to thebusiness


The Philosophy of Atern - 2This is best achieved when key stakeholders

understandthe

business

objectivesare empowered

to an appropriatelevel

collaborateto converge on the best

i l l i i

V1.0

i l l i , iagreed timescale,

according businessprioritiesare prepared to

deliver a

fit for purposesolution

accept thatchange isinevitable

8/11/2019 AD_Topic_2

4/8




Not just software!

V1.0


The Benefits of Atern

User ownership of the system is more likely

Reduced risk of building the wrong system

The final system is more likely to meet the users

V1.0

real business requirements

Users will be better trained Deployment is more likely to go smoothly


The 80/20 Approach

80%

100%

Level of

Functionality

Fundamental Assumption:Nothing is built perfectly first time,

but 80% of the solution can be producedin 20% of the time it would take to produce

the total solution.

V1.0

0%

20%

40%

60%

20% 40% 60% 80% 100%

Development Time

8/11/2019 AD_Topic_2

5/8




A Question of Balance

V1.0

JDI Heavyweight

Methods

Heavyweight

MethodsATERN


Components of a Business Solution

Business

Objectives

V1.0

People Process Technology


Flexing Requirements

Features Cost Time

Fixed

Traditional Approaches DSDM Atern

Fixed

V1.0

Cost Time

Quality?Quality

Features

Variable Variable

8/11/2019 AD_Topic_2

6/8




Prioritisation

MMust haveO

SShould haveCC

WWMM

V1.0

CCould haveO

WWont have this time

MM


The 8 Principles of Atern

Deliver on time Develop iteratively

Build incrementally

from firm foundations

Focus on the

business need

V1.0

Collaborate

Never compromise

qualityDemonstrate control

Communicate continuously

and clearly

DSDM Consortium 2007


Atern 5 Key Techniques MoSCoW Prioritisation

Modelling

MM

SS

CCWWMM

V1.0

Facilitated Workshops

Iterative Development

Timeboxing

8/11/2019 AD_Topic_2

7/8




Instrumental Success Factors (ISFs)

1. Acceptance of the Atern

philosophy before starting

work

2. Appropriate empowerment

of the Solution

Development team

5. Access by Solution Development Team

to business roles

6. Solution Development Team

stability


V1.0

3. Commitment of senior

business management

to provide the necessary

business roles

involvement

4. Incremental delivery

skill


size

9. A supportive commercial relationship

RISK!


What Kind of Projects?

Visible Functionality Clearly defined user group

Time constrained Requirements are nottoo detailed or fixedProject

V1.0

Not computationally complex

or complexity can be

decomposed or isolated

Iflarge, can be

broken down into

smaller componentsRequirements

can be prioritised

Questionnaire


Summary of DSDM Atern Atern is an Agile Project Delivery Framework that

delivers the right solution at the right time.

The right business solution is delivered because:

- The Project team and other significant stakeholders remain

focused on the business outcome

V1.0

-reduced risk

- All people involved with the project work collaboratively to

deliver the optimum solution

- Work is prioritised according to business need and the ability

of users to accommodate changes

- Atern does not compromise quality

8/11/2019 AD_Topic_2

8/8




Topic 2 Approach and Principles

NCC Education LimitedV1.0

Any Questions?

Documents

AD_Topic_2