SeminarAgileScience

8/7/2019 SeminarAgileScience

1/42


2/42

2TELEFNICA I+D

2008 Telefnica Investigacin y Desarrollo, S.A. Unipersonal

01 The Problem02 Agile Response

03 Scrum

04 eXtreme Programming

05 Agile Scientific Research

06 Conclusions

Index


3/42

3TELEFNICA I+D


3

Agile MethodsThe Problem


4/42


5/42

5TELEFNICA I+D


The ProblemTechnologyEnvironment

01

Changes Requirements Scope

Technology

New Paradigm Technology

R e q u i r e m e n t s

known unknown

stable

unstable

simple

chaos

complexity

Requirements

Cost Date

Cost Date

Features

Plan DrivenPlan Driven Value DrivenValue Driven

FIX

ESTIMATE

TRADITIONAL AGILE


6/42

6TELEFNICA I+D


The ProblemSummary

The market demands and expects

innovative

high-quality software that meets its needs

and soon

01


7/427

TELEFNICA I+D


7

Agile MethodsThe Response


8/428

TELEFNICA I+D


Agile ResponseMarket Needs

EMBRACINGEMBRACING CHANGECHANGETraditionalAgile

Time

C o s

t

o f

C h a n g e

02


9/42

9TELEFNICA I+D


Agile ResponseWhat is software development?

MentalCreative

Human

Is a process of knowledge transformation

SoftwareProblem

Need Software Developer

Caso de Uso Clases An lisis Clases de Dise o C digo Componentes Ejecutables Librerias

Traceability

Knowledge Transformation

02


10/42

10TELEFNICA I+D


What is Agile?

Agile processes are iterativeprocesses that use specific project

management and softwareengineering practices to sustain the

delivery of new software

functionality every one to fourweeks

02


11/42

11TELEFNICA I+D 2008 Telefnica Investigacin y Desarrollo, S.A. Unipersonal

Agile Manifesto

More ImportantImportant

individuals and interactionsprocesses and tools

working softwarecomprehensivedocumentation

customer collaborationcontract negotiation

responding to changefollowing a planwww.agilemanifesto.org

That is, while there is value in the items on the left, wevalue the items on the right more.

We are uncovering better ways of developing software bydoing it and helping others do it. Through this work wehave come to value:

02


12/42


Agile Manifesto

More ImportantImportantindividuals and interactionsprocesses and tools

working softwarecomprehensivedocumentationcustomer collaborationcontract negotiation

responding to changefollowing a plan

www.agilemanifesto.org

That is, while there is value in the items on the left, wevalue the items on the right more.

We are uncovering better ways of developing software bydoing it and helping others do it. Through this work wehave come to value:

AGILAGILEE:

Only codeCreating and responding to change

02


13/42


Agile Methods

Scrum

eXtreme Programming (XP)

Crystal

Feature Driven DevelopmentDynamic Systems Development Method

Adaptive Software Development

Lean Development

Pragmatic Programming

Inclusive

Rules

GenerativeRules

02


14/42


Iterative vsWaterfall

Soft-NOT-aware

Software

Requirements

Analysis&Design

Implementation

Testing

DeploymentArchitectureRequirements

SoftwareSoftware

Paperware

Iteration1 Iteration2 Iteration3Release1Release2

Release3

Focus In Executable Software

You can't knoweverything atthe beginning

You learnas youwork

W A T E R F A L L

W A T E R F A L L

A G I L E

A G I L E

02


15/42


Iterative vs. Waterfall

Soft-NOT-aware

Software

Requirements

Analysis&Design

Implementation

Testing

DeploymentArchitectureRequirements

Software

Software

Paperware

Iteration1 Iteration2 Iteration3Release1Release2

Release3

Focus In Executable Software

You can'tknow

everything atthe

beginning

You learnas youwork

W A T E R F A L L

W A T E R F A L L

A G I L E

A G I L E AdaptiveManagement

PredictiveManagement

what method fits mebest?

02


16/42


Why Iterative Development?

knowledgeRisk

Iterations help acquiring knowledge

Of both theproblem and the

solution

Estimation Error

Short term is easierto predict and

estimate rather thanlong term

Time

Iterations

02


17/42


What makes a development process Agile ?

Each iteration delivers working software .

The phases in each iteration arenearly concurrent .

Team uses specific engineering practices to keep the code base fresh and flexible .

Teams are self-managing .

Lean principles and techniques eliminatewaste whenever possible.

02


18/42


Why adopt Agile processes?

Reduced time-to-market.

Increased innovation.

Business alignment.

Increased quality.

Reduces product and process waste.

High visibility and control over the project progress.

Empowered, motivated and self organizing Teams.

02


19/42


What kind of change is required toadopt Agile?

Larger teams must be broken into smaller ones.Functional silos have to be broken down, or at leastweakened.

Specialists have to pick up new skills.

Teams must learn to self-manage, and managers mustlearn to let them.

Routine activities have to be automated.

02


20/42


Where is Agile most suitable?

Projects with some degree of uncertainty aroundrequirements or technology.

Projects that arent too big or too small.

Projects with buy-in from team members, businessstakeholders, and management.

Collocated project teams andbusiness customers.

Projects using modern languagesand tools.

02


21/42


How widely are Agile processesused?

02


22/42


How to use

Scrum Scrum/ XPCustom/ DSDM

XP Hybrid OtherHybrid

37%

23%

12% 9%

5%

The State of Agile Development. Julio 2007-Version One

7272%%

Pilotexperience in

Telefnica I+D

02


23/42


23

Agile MethodsScrum


24/42


SCRUM: Planning Iterations

Source mountaingoatsoftware.com

03


25/42


SCRUM: Planning Iterations

Iteration 1 Iteration 2 Iteration 3

Product Backlog

Assessment &Planning NextUse Cases

ImplementedRisk Addressed

03


26/42


SCRUM: Framework

3 ROLES3 ROLES Product Owner Team Scrum Master

33 BACKLOGS

Product Backlog Sprint Backlog Impediments Backlog

44 MEETINGS Sprint Planning Daily Meeting Sprint Review Retrospective

EMPIRICAL PROCESSCONTROL

Transparency

Inspect

Adapt

03


27/42


SprintSprintPlanningPlanning(I)(I)

SelectedSelectedProductProductBacklogBacklog

SprintSprintPlanningPlanning(II)(II)

IncrementIncrement

SprintSprintBacklogBacklog

RetrospectRetrospect

iveive

Sprint ReviewSprint Review

EstimationEstimationMeetingMeeting

VisionVision

SPRISPRINTNT 00

ImpedimentsImpedimentsBacklogBacklog

Daily MeetingDaily Meeting

H e c h o ? P e n d i e n t e ? T r a b a s ?

SPRISPRINTNT

ProductProd uctBacklogBacklog

SCRUM: Workflow03


28/42


SCRUM: Sprint Backlog

P R I O R I T I Y

P R I O R I T I Y

I MPEDED

What doesDONE mean?

03


29/42


SCRUM: Reports

Sprint Burndown ChartSprint Burndown Chart

R e m a

i n i n g

T i m e

R e m a

i n i n g

T i m e

daysdays

03


30/42


30

Agile MethodseXtreme Programming


31/42


Simple Design

Test-DrivenDevelopment

Pair Programming Refactoring

XP. Values & PracticesCOMMUNICATION SIMPLICITY

COURAGE FEEDBACK

Stub out codeWatch test fail Refactor

Repeat

Get test to pass

04


32/42


XP. Values & PracticesCOMMUNICATION SIMPLICITY

COURAGE FEEDBACK

Simple

Design

Test-DrivenDevelopmen

t

PairProgramming Refactoring

Open Workspace

CollectiveOwnership

ContinuousIntegration

Metaphor

SustainablePace

CodingStandard

Acceptance Tests

One Team

Iterations

Small Releases

Release Plan

Retrospective

User Stories

Onsite Customer

04


33/42


XP: Planning/Feedback Loop

Code

Pair Programming

Unit Test

Pair Negotiation

Stand Up Meeting

Acceptance Test

Iteration Plan

Release Plan

04


34/42


XP: Employment Practices

The State of Agile Development. July 2007-Version One

Agile Practices

04


35/42


3535

Agile MethodsAgile Scientific Research

05


36/42


36

Agile Scientific ResearchThe Scientific Process

05

05


37/42


Agile Scientific ResearchThe Scientific Process

What does the scientific method share with AgileMethodologies? Iterative

Fast-changing requirements

Test-driven (Hypothesis-driven)

Pair-programming (Peer review)

Simple Design (Occams Razor)

37

05

05


38/42


Agile Scientific ResearchPlanning iterations

Iteration 0: build up general hypothesis List of stories -> things we would like to say in our final

article Optionally, write the article itself in this first iteration

Every 1-2 weeks come up with a list of prioritized tasks List all possible tasks (ideally 1-2 day workload)

Measure interest of the task towards final goal

Measure cost in terms of predicted hours of work

List them in order of priority value (= interest cost) For ties, value more those that have less cost (Occams Razor)

In the iteration planning re-evaluate general hypothesis

38

05

05


39/42


Agile Scientific ResearchTest Driven Development

Plan stories and tasks by writing the tests first Use test as an executable hypothesis

If I can prove hypothesis H then it should happen that tests t1 and t2 shouldpass

Maintain collection of tests as a record of experiments

Use the red-green-refactor cycle Refactor to refine your theory while still being consistent to experimental data

39

05


40/42


4040

Agile MethodsConclusions

06


41/42


Conclusions

Scientific Research is an iterative process with fastchanging requirements It can be managed as an Agile project

Many of the Agile practices are applicable

Agile can help improve focus, performance, and helpresearchers accomplish goals in a timely fashion

41

To deliver high qualityhig h quality, runningrunning ,

testedtested storiesstories that meet the businessmeet the businessneed in a predictablepredictable, efficientefficient andcollaborativecollaborative manner on time, on

budget!

06


42/42

SeminarAgileScience

Documents

Transcript of SeminarAgileScience