Agile Pm Intro

8/19/2019 Agile Pm Intro

1/15

Agile: approach of building products or services by

EMPOWERING and TRUSTING people, acknowledging CHANGE

AS A NORM, and promoting CONSTANT FEEDBACK

Agile is a PHILOOPH! that uses organi"ational models based on

people, collaboration and !are" #al$e#

Agile uses rolling %a#e plannin&$ iterati#e and incre'ental

"eli#er($ rapid and %e&ible response to change$ and open

communication between teams, stakeholders, and customers#

Agile is a MINDSET established through ' )A*UES, grounded by

() PRINCIP*ES * manifested through many DIFFERENT

PRACTICES


2/15

Agile is and isn+t

A&ile I+• A set of principles * practices

based on the Agile -anifesto

• A disciplined pro.ectmanagement approach

•

/usiness * delivery focused,welcoming change

• Agile is a general concept$crum and 0P are speci1cimplementations of Agile

• Incremental framework, fre2uent

delivery * continuousfeedback loops

• An empirical process 3 fre2uentinspect and adapt cycles thatminimi"e waste

A&ile I Not+• 4nplanned

• 5haotic

• 4npredictable

• Open 6nded

• 4ndocumented

• A methodology

• 4nconstrained

• A 7/est8 Practice

• 9ithout its challenges


3/15

9hy Agile

Accelerate time tomarket

-anaging changepriorities

/etter alignI;


4/15


5/15

• ;ime3bo&ing• =etrospective• pike olution• Planning Poker•

/acklogPrioriti"ation• Progress

6laboration

• Limit 9ork inProgressJ9IPK

• hort

Iterations• print Boals• ervant

Leader• elf

3organi"ation• ;eam

Agreements

• PairProgramming

• ace to ace5onversation

•

;est @riven@evelopmentJ;@@K

• Melocity• 4nit ;esting• ##

Numerous Agile Practices


6/15

;raditional Pro.ect Phases

=e2uirementsAnalysis

@esign

5oding

Integration

;esting

@eployment

Operations and-aintenance

Final So.t%are O$t

T

i ' e


7/15

Agile Incremental @elivery

Final So.t%are O$t

ProductIncrement

s

ProductIncrement

s

ProductIncrement

s

Agile adapts to fre2uent feedback by delivering workingtested code

eedback Loops=eview and Ad.ustInspect * Adapt

Analysis@esign5odeIntegrat

e ;est@eploy

Analysis@esign5odeIntegrat

e ;est@eploy

Ti'e


8/15

Agile Incremental @elivery

•

Agile team produces deployablesoftware every week#

• In each iteration, the team analy"es,designs, codes, tests, and deploys asubset of features#

• ;he team gets feedback much morefre2uently#

• ;he tight feedback loop also allowsAgile teams to improve their plans2uickly#


9/15

9hat+s @iEerent

;raditional Agile

@e1ned process: 5ontrol and 5oordinated 6mpirical process: Inspect and Adapt

9ork is organi"e around the team ;eam organi"e around work

9ork is assigned or push to the team 9ork is store in 2ueue and team pull the tasks

Plan all in advance Plan as you go

9ork breakdown structure eature breakdown structure

unctional specs 4ser storiesBantt chart =elease plan

tatus report Information radiators


10/15

Operating -odel of an Agile ;eam

• ;eam organi"ed around the work• 6mpowered•

elf organi"e < elf managed• ;eam pulls the task from 2ueue


11/15

Malue @elivery

Malue@elivery=isk ofailure

Ti'e Ti'e

Tra"itional A&ile


12/15

() Principles of Agile

• Our highest priority is to satisfy the customer through early and

continuous delivery of valuable software#• 9elcome changing re2uirements, even late in development#

Agile processes harness change for the customer>s competitiveadvantage#

• @eliver working software fre2uently, from a couple of weeks to

a couple of months, with a preference to the shorter timescale#• /usiness people and developers must work together daily

throughout the pro.ect#

• /uild pro.ects around motivated individuals# Bive them theenvironment and support they need, and trust them to get the

.ob done#• ;he most eDcient and eEective method of conveying

information to and within a development team is face3to3faceconversation#


13/15

() Principles of Agile

• 9orking software is the primary measure of progress#

• Agile processes promote sustainable development# ;he sponsors, developers, and users should be ableto maintain a constant pace inde1nitely#

• 5ontinuous attention to technical e&cellence and

good design enhances agility#• implicity 3the art of ma&imi"ing the amount of work

not done 3is essential#

• ;he best architectures, re2uirements, and designs

emerge from self3organi"ing teams#• At regular intervals, the team re%ects on how to

become more eEective, then tunes and ad.usts itsbehavior accordingly#


14/15

;rue or alse Answers

( Agile recommend incremental * iterative delivery ;rue

) Agile recommend big upfront design J/4@K alse

? Agile has de1ned change management process alse

' Agile recommends directive teams alse

Agile measures progress by working software ;rue

C Agile does not recommend any documentation in thepro.ect

alse

F Agile recommends face to face interaction ;rue

G Agile recommends accepting change during iteration alse

Agile teams make their own decisions ;rue


15/15

High Level Process -ap

Iteration n

Iteration /

Iteration -

Feaibilit(

Pro.ectMisioning

Initiation Releae Plannin&

Iteration ,

Cloe O$t

NPM, I==, =OI

/usiness 5asewith High level6stimates

Pro.ect5harter

Product

/acklog

High levelestimating usingaDnity

Product=oadmap

6pic

tories

tories

6stimating4sing PlanningPoker

;heme

L-

0L

=eleasePlan

inalProductIncreme

nt

• ;estingAgreement

• ;eam6nvironment

•

Architectureapproach

• @ependencies• =isks

Iteration

/acklog

;ask /oard

Bo back to =elease Planningfor another release, or if1nal release, go to pro.ectcloseout

/acklogTo DoIn Pro&reDone

Iteration

Planning

=elease

@aily stand3up,@evelopment, ;esting,

deployment, etc#

=etrospective

=eview

/urnup

Agile Pm Intro

Documents