Upload
john-morse
View
5.932
Download
0
Embed Size (px)
DESCRIPTION
brief overview on running projects with both agile and waterfall methodologies combined
Citation preview
Challenges of running a combined waterfall and agile project
or
Why neither is best
Firstly
What does "agile" and "waterfall" mean?
"Agile leaders lead teamsNone-agile ones manage tasks"
http://www.lifehack.org/articles/polls/we-ask-you-answer-your-quirky-system.html
Waterfall
• Manage activities• Granular • Sequential process • Requirements, design, build, test, release
(maintain)....then fix • Highly structured• Well documented• Best suited to situations where
change is uncommon?
http://en.wikipedia.org/wiki/Waterfall_(M._C._Escher)
Agile
• Manage time• Highly collaborative• Customer is involved in the process• Regular delivery of 'products'• Flexible• Continuous Improvement
o to both producto and process
http://www.alistapart.com/articles/gettingrealaboutagiledesign/
Agile manefesto
http://shouldbereading.wordpress.com/2010/03/11/certified-bookworm/
"Individuals and interactions over processes and tools.Working software over comprehensive documentation.
Customer collaboration over contract negotiation.Responding to change over following a plan."
Bringing the two together
Agile methodologies generally promote a project management process that encourages stakeholder
involvement, feedback, objective metrics and effective controls.
http://thebardofburlesque.blogspot.com/2009/01/working-for-good-of-whole.html
Bringing the two together
Waterfall methodologies rely more on a defined set of requirements and tasks that cascade through the stages of the project to a 'neatly controlled' end.
http://blog.media-freaks.com/slinky-etch-sketch/
So what are the 'challenges' ?
http://cozymurders.blogspot.com/2009/01/suck-at-challenges-challenge.html
Challenges
• Reporting o Structured reports v Timeboxed daily standups and end
sprint meetings
• Financial managemento Fixed costs v time and materialso Spending what we have wisely
• Time / resource managemento Understanding what is achievable with what you have
Challenges
• Change o Formal change management as opposed to change as
part of the processo Not being afraid of change!
• Managing customer expectationso Customer is part of the team not just a point of deliveryo Delivering (not nesc deploying) products after each cycleo Customer understanding that they have a part to play in
planning and re-planning each delivery
Challenges
• Managing business expectationso We need to be paid, when will this happen (T&M v's fixed
cost)
• Communicating the 'plan'o A defined set of task against time as opposed to ...not?
OR
What can we do in the amount of time and resource we have?
as opposed to
We have to get this done in this much time
Soooo...
http://www.fotolibra.com/gallery/35001/chalk-and-cheese-illustration/
Chalk and cheese....right?
Maybe not
• Define long term but not short term goals and integrate into a longer term plan o iterations within a defined period of time
• Mini waterfalls with agile processes within them
• Highlight reports = end sprint report
• Be flexibleo Waterfall - Plan, Release, Documentation processeso Agile - Development
• Prince2 can be / is agile (ish)
Finally
It all depends on the customer, project, environment, team ...
if it really is a challenge ....
(as opposed to an opportunity)
don't do it
http://drstephaniesmith.files.wordpress.com/2010/10/stress.jpg
Like good a good UI
If you are aware of the challenges with the method you are using to run the project, you're doing it wrong
because
If you find yourself working all day maintaining the methodology....
who's taking care of business?