ANYTHING BUT AGILE
Agile Project Plan Template Authored by: by: Christophe Le Coent
From envisioning to close out
1. Contents 2.
Project Chartering............................................................................................2 Lift o planning................................................................................................... 2 Purpose............................................................................................................... 2 Alignment........................................................................................................... 2 Conte!t............................................................................................................... "
".
#verall direction.............................................................................................. "
Timeline summary.............................................................................................. " $.
%ilestones and milestone management.........................................................." Project %ilestones..............................................................................................." %ilestone trac&ing.............................................................................................. ' (!ample.............................................................................................................. )
'.
*is& and +ssue management...........................................................................) (!ample.............................................................................................................. )
).
Assumption management...............................................................................,
,.
-ependency management..............................................................................,
.
Communication plan....................................................................................... %inutes of meetings...........................................................................................
/.
0uality Plan..................................................................................................... 1ser tories........................................................................................................ -e3nition of -one 4-o-5.................................................................................... / Creation of the -o-......................................................................................... / *evie6 of the -o-........................................................................................... / (!ample.......................................................................................................... / -esign................................................................................................................ /
78.
Test trategy..............................................................................................78
The $ 9uadrants............................................................................................... 78 The pyramid of tests.........................................................................................78 77.
oft6are frame6or&...................................................................................77
72.
*elease %anagement.................................................................................77
7".
-efect %anagement...................................................................................77
7$.
*oles and *esponsibilities..........................................................................77
7'.
*esource %anagement and Planning.........................................................7"
7).
udget........................................................................................................7"
People............................................................................................................... 7" oft6are........................................................................................................... 7" ;ard6are.......................................................................................................... 7" Trainings........................................................................................................... 7$ Travels.............................................................................................................. 7$ %iscellaneous................................................................................................... 7$ ummary.......................................................................................................... 7$ 7,.
Team %aturity...................................................................................................7$ %etrics.............................................................................................................. 7$ 7.
Compliance constraints..............................................................................7$
7/.
*eference...................................................................................................7$
Note from author: an agile project plan is a high level view on how the project will be managed and it should never contrevine the Agile Manifesto and principles. This document should remain lightweight and only use as guidelines to drive the project to deliver valuable working software in short iterations to the customers.
2. Project Chartering Lift o !anning This document=s value is in the lift o session >'? 6here sta&eholders@ team members@ product o6ners@ scrum masters and project managers 6ill create or consolidate the project chartering: purpose of the project@ alignment of the team around the project and conte!t of the project. +nitially@ the Product #6ner should draft the purpose of the product and the conte!t. Project chartering 6ill be an output of the lift o session.
P"rose • • •
hat is the visionB alue to Attain hat is the missionB *esult to Accomplish hat are the mission testsB Criteria for uccess
A!ign#ent • • •
alues D Principles E eliefs D +deals about or& or&ing Agreements E #perational uidelines Core Team E CrossEfunctional group 6ith a common purpose
Conte$t • • •
Committed *esources E #rganiGation upport oundaries D +nteractions E eeing the ystems Prospective Analysis E +nitial Projections
%. &'era!! (irection For the 3rst user story implemented@ 6e 6ill deploy this feature to live. HThere is only value if features are delivered to the customersI. 0uality is not only for the code and test code@ this is also about the 9uality of the user stories@ acceptance criteria@ meetings@ etc To align the design of the solution 6ith the user stories@ 6e 6ill use domain driven design ideas and &eep the design readable by the product o6ner of the product.
Ti#e!ine s"##ar) (!ternal *eleases: +nternal milestone
*el ase pecula (nvis on te Lift o Plan in print 7 print 2 print " . sprint ) . print n Closure g 7st release
2nd release
%P
Final release
4%inimum iable Product5
T7 T2
T"
T".
T".
T$ T'
peculate D Adapt
Potentially hippable +ncrements at the end of each sprint as per -o-
*. +i!estones an( #i!estone #anage#ent Project +i!estones +i!estones B"(get aro'e( for
Gate
,e-nition
Phase
*esource is assigned for +nitiation phase to be completed
(nvision
P!anne ( (ate
T)e Trac&ing
ec"!atio n hase Initia! ro("ct /ac0!og co#!ete En'ision hase Co#!ete Tshirt si3ing (one
B"(get aro'e( for co#!etion of the roject High Le'e! Architect"r e agree( Non f"nctiona! re4"ire#en ts 56PIs7 (e-ne( Test trateg) (e-ne( 8eso"rce !an agree( ec"!ate hase co#!ete Lift & session co#!ete
,e-nition
TG1
TG2
(pics are de3ned including architecture and nonEfunctional re9uirements at high level ta&eholders approve goEahead to +nitiation phase ;igh level estimate is done 4!$ for uncertainty5 for budgeting purpose of the product bac&log 4at epics level5 udget is estimated and agreed
(nvision
Trac&ing
(nvision
oJKo o
+ncluding and ; architecture@ using -->,? Performance@ monitoring@ load@ reliability@ stability@ usability@ ecurity@ other HilitiesI ;igh level test strategy
*esource plan agreed for the duration of the project #verall scope is de3ned and estimated@ *esource available@ team can start detailing the plans Team is aligned 6ith a clear purpose and understand the conte!t of the project. Team has de3ned their 6or&ing HrulesI. Project chartering is live 0uality standards are
peculat e
Trac&ing
peculat e
Trac&ing
peculat e
Trac&ing
peculat e
Trac&ing
peculat e
Trac&ing
peculat e
Trac&ing
peculat e
oJKo o
peculat e
Trac&ing
*elease
Trac&ing
of ,one create( /) the tea# Pro("ct /ac0!og is ,EEP 8e!ease P!anning co#!ete
En( of rint 1 En( of rint % En( of rint 9 ta/!e 'e!ocit)
set
TG%
TG%. 1 TG%. 2
:irst re!ease to c"sto#ers econ( re!ease to c"sto#ers +;P< +ini#"# ;ia/!e Pro("ct :ina! re!ease to c"sto#ers ec"!ate = A(at hase co#!ete C!os"re hase co#!ete
T o J Ko o Trac&ing
TG*
TG>
Product bac&log has been estimated and prioritised There is a high level plan covering the ne!t " sprints Team is ready to sprint starting 6ith print Planning for sprint 7
*evie6 product progress to sta&eholders *evie6 product progress to sta&eholders hen velocity is &no6n and can be used for planning purposes First e!ternal release@ not for commercial use: &ey features are: M econd e!ternal release@ not for commercial use: &ey features are: M Product that has enough features it can be deployed to end customers: &ey features are: M Final release@ product is ready to go into maintenance mode Last sprint is completeN project can be close
Project can be closeN all pending actions are close
Planning
*elease Planning *elease Planning
Trac&ing
oJKo o
(!plore D Adapt (!plore D Adapt (!plore D Adapt (!plore D Adapt
Trac&ing
(!plore D Adapt
Trac&ing
(!plore D Adapt
Trac&ing
(!plore D Adapt
Trac&ing
oJKo o oJKo o Trac&ing
(!plore D Adapt
oJKo o
(!plore D Adapt
oJKo o
Close out
oJKo o
Tollgate 4formal milestone for decision ma&ing5 Formal revie6 meetingsN dates 6ill be trac&ed %ilestones 6ill be trac&ed only i.e. no decision re9uired
+i!estone trac0ing H%ilestone lip chartI tool >2? 6ill be used to trac& milestones mar&ed 6ith O= on a 6ee&ly or sprint based depending on the phase of the project 46ee&ly for all e!cept (!plore and Adapt: at the end of each sprint5
E$a#!e "Eun "EunE8,
2"Eun
7"Eul
2EAug
22EAug
77Eep
#bli9ue
(nvision phase complete 4T75
*elease Planning complete 4T"5
Lift o complete
First release to e!ternal customers
econd release to customers
T".7: oJKo o 4sprint "5
T".2: oJKo go 4sprint )5
Final release to customers
peculate D Adapt phase complete 4T$5
2"EunE8, peculate phase complete 4T25
7"EulE8, +nitial performance testing
2EAugE8, %inimum iable Product
22EAugE8, T".": oJKo go 4sprint /5
77EepE8, Closure phase complete 4T'5
>. 8is0 an( Iss"e #anage#ent *is&s and +ssues 6ill be updated on a 6ee&ly basis and shared 6ith all sta&eholders *is& and +ssue trac&ing tool >"? 6ill be used.
E$a#!e
8I6 ANALYI ' $ " 2 7 8
IUE ANALYI ' $ " 2 7 8
9. Ass"#tion #anage#ent The project team members must identify and document all of the assumptions being made during the project planning process@ and then on a one by one basis@ identify the ris&s that e!ist as a result of each assumption to the project based on the potential inaccuracies or inconsistencies that the assumption may e!hibit. Assumptions 6ill be managed as *is&s using *is& and Trac&ing tool >"?
?. ,een(enc) #anage#ent *elease planning sessions@ sprint planning meetings and during sprints 6ill reveal dependencies.
*elease planning 6ith other teams as 6ell as scrum of scrums 6ill help negotiate such dependencies 4due date@ type@ urgency@ etc5 #ther dependencies 6ill be managed in the table belo6:
,escrition Contin"o"s ,e!i'er) En'iron#ent
@hen /) From sprint 7
ta/!e !atfor#
From sprint 7
Co##ents8is0s Lac& of an eective Continuous -elivery environment 6ill slo6 do6n development and prevent us from having stable velocity 1nstable platform 6ill mean more time to identify issues and 6ill slo6 do6n the team
%r( art)
. Co##"nication !an @hat Li'e (e#o of Dor0ing softDare
rint reorts
To!! Gates
,escrition -emo of 6hat has been delivered according to the de3nition of -one at the end of the sprint elocity *elease burnE do6n chart *is&s and issues Test results 1nit test coverage Kumber of defects 4inQo6 and outQo65 Technical debt For each gate@ a meeting 6ill be hold including last sprint report 4if applicable5 and a revie6 of the business case. -ecision to
@hen:re4"enc) At the end of each sprint
@ho to< All
At the end of each sprint
ta&eholders
ee T dates and %P date
ta&eholders
8is0s an( Iss"es +i!estone Trac0ing cr"# of scr"#s
continue 4o5 or cancel 4Ko o5 the project can be made at these meetings *is&s and +ssues on the project (stimated milestone dates *otating team members
ee&ly At the end of each sprint T6ice a 6ee&
ta&eholders ta&eholders #ther team members from scrum teams
+in"tes of #eetings For meetings 6ith sta&eholders@ meeting minutes 6ill be recorded using H(asy %inutesI >)?
. F"a!it) P!an User tories 1ser stories 6ill: •
• • •
•
Follo6 the +K(T %odel 4+ndependent@ Kegotiable@ aluable@ (stimable@ iGed appropriately and Testable5 ;ave personas ;ave conditions of satisfaction ;ave acceptance criteria using speci3cation by e!ample 4ivenJhenJThen5 (tc
This is not about matching the criteria above that ma&es a good user story@ this is the 9uality and appropriate level of information. ;ence 6e 6ill also maintain a -((P product bac&log 4-etailed Appropriately@ (stimated@ (mergent and Prioritised5.
,e-nition of ,one 5,o,7 Creation of the ,o, Team creates their H-e3nition of -oneI for: E E E E
1ser stories prints *elease 4to production5 The -o- is approved by the P# and display on the 6all
8e'ieD of the ,o, The team 6ill revie6 their -o- at the end of each sprint
E$a#!e
,esign an( Testing -esign and testing are aligned 6ith the user stories of the product bac&log as per >,?
1.
Test trateg)
The * 4"a(rants For test planning@ 6e 6ill base our planning on Agile Testing 0uadrants >/? and &eeping in mind the success of the project relies on a very collaboration bet6een all members of the team. Testing is the responsibility of the team@ not only to test engineers 6or&ing in the team.
The )ra#i( of tests From 1+ Tests 4hard to maintain@ long to run5 to 1nit Tests 4(asy to maintain@ 9uic& to run5 >?.
UI
:"nctiona!
11.
oftDare fra#eDor0 Unit tests
e 6ill be using crum 6ith 4as a summary5: E E E E
print Planning -aily standEups print revie6 *etrospectives
prints 6ill be 6ee&s long. (ach sprint 6ill 3nish on ednesdays 78am.
12.
8e!ease +anage#ent
print cycle and release cycle 6ill be decoupled giving the team the opportunity to release soft6are any time. +n general@ a release 6ill be made at the end of each sprint 6here integration issues 6ill be addressed.
1%.
,efect +anage#ent
-efects 6ill be adding to the product bac&log 4if they are not 3!ed 6ithin the sprint5. -efects 6ill be estimated in story points and prioritised among other defects and user stories. Ko points 6ill be given for 3!ing defects. Points are only for estimation purpose and 6ill not be added to the velocity.
1*.
8o!es an( 8esonsi/i!ities
*AC+ %atri!
(nsure consistency of scrum practices across teams Provide vision and goal for the product Provide resource 6ith right s&ills and mindset PrioritiGe and manage the product bac&log *emove impediments %anage the implementation of the project plan %a&e sure scrum practices are used and improved 6ithin the team Create@ apply and continuously improve the -e3nition of -one #n time reporting to management -e3ne acceptance criteria
Functional %anager4s 5 +
crum %aster
Product crum #6ner Team
Project %anager
C
C
+
*JA
+
+
*JA
+
+
*JA
+
+
CJ+
C
+
F
*JA
C
F
*
*
*JA
*
*
+
+
C
C
*JA
*
*JA
C
*
F
C
F
*
*JA
F
+
F
*JA
+
F
+
F
*JA
C
F
rite acceptance tests
+
F
C
*JA
F
(nsure 9uality of the product %anage *is&s
*
*
*JA
*
*
C
C
*JA
C
*
Approve user stories 4user stories meet the acceptance criteria5 -ecide on release date and goal
+
F
*JA
C
F
+
+
*JA
+
+
Kote: 7. The above *AC+ matri! doesn=t cover all the activities 6ithin the scrum frame6or&N therefore al6ays chec& the responsibilities for e ach role. 2. The *AC+ matri! may dier per project due to structural andJor organiGational constraints. *esponsible R Those 6ho do the 6or& to achieve the tas&. There is typically one role 6ith a participation type of responsible@ although others can be delegated to assist in the 6or& re9uired Accountable R The one ultimately ans6erable for the correct and thorough completion of the deliverable or tas&@ and the one from 6hom responsible is delegated the 6or&. +n other 6ords@ an accountable must sign o 4approve5 on 6or& that responsible provides. There #"st be only one accountable speci3ed for each tas& or deliverable. Consulted R Those 6hose opinions are sought@ typically subject matter e!pertsN and 6ith 6hom there is t6oE6ay communication. +nformed R Those 6ho are &ept upEtoEdate on progress@ often only on completion of the tas& or deliverableN and 6ith 6hom there is just oneE6ay communication. Facilitator R ;elps teams and individuals to continuously improve and understand their roles 6ithin the crum frame6or&. They help team members change their behaviour and act as a coach and a change agent.
1>.
8eso"rce +anage#ent an( P!anning
S time allocated and phase
19.
B"(get
Peo!e Phase duration 46ee&s5 Total FT( J $ 6ee&s 4per month5: 7$).' manJ6ee&s R ", manJmonths Cost per team member: '8& Total cost R '8", R 7'8&
oftDare Har(Dare ;ard6are ystem re9uirements 6ill be captured under >7?. The cost 6ill be provided:
Trainings
Tra'e!s +isce!!aneo"s "##ar) T)e Peo!e oftDare Har(Dare Trainings Tra'e!s +isce!!aneo" s Tota!
Esti#ate( Cost 507 7'8
1?.
6PIs 5Project7
Tea# +at"rit) e 6ill update the chec&list >$? on a monthly basis.
+etrics elocity 6ill be recorded on a sprint basis
1.
Co#!iance constraints
1.
8eference
,escrition Har(Dare )ste# 8e4"ire#ents
I, >7?
Lin0:i!e
; ystems *e9uirements v8.2.d
+i!estone !i Chart too!
>2? Agile %ilestone Trac&er -emo v'.$,.
8is0 an( Iss"e +anage#ent too!
>"? (!ample E *is&sE+ ssues log.!lsm
cr"# Chec0!ist
>$? crumchec&list.!ls!
Lifto< La"nching Agi!e Tea#s = Projects Eas) +in"tes too!
>'?
Lin&: here
>)?
5chec0 Dhere to store A((In te#!ates Dith )o"r 'ersion of @in(oDs +icrosoft7
(asy%inutesAddE+n v).7.dot
A!igning "ser storiesJ (esign an( testing
>,?
The forgotten !a)er of the test a"to#ation )ra#i(
>?
Agi!e Test P!anning
>/?
Agile 12 --- :-$.jpg
theEforgottenElayerEofE theEtestEautomationE pyramid Agile Testing Planning lin&
