The Artima Developer Community
Sponsored Link

Agile Buzz Forum
XPDAY7: Why do Agile projects fail?

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Simon Baker

Posts: 1022
Nickname: sjb140470
Registered: Jan, 2006

Simon Baker is an independent consultant, agile coach and scrum master
XPDAY7: Why do Agile projects fail? Posted: Nov 25, 2007 5:32 PM
Reply to this message Reply

This post originated from an RSS feed registered with Agile Buzz by Simon Baker.
Original Post: XPDAY7: Why do Agile projects fail?
Feed Title: Agile In Action
Feed URL: http://feeds.feedburner.com/AgileInAction
Feed Description: Energized Work's blog.
Latest Agile Buzz Posts
Latest Agile Buzz Posts by Simon Baker
Latest Posts From Agile In Action

Advertisement
At XPDay 7, Joseph Pelrine and Jiri Lundak asked why do Agile projects fail?


A project is an iceberg
Originally uploaded by sjb140470
With the wind blowing in one direction, an iceberg moves in the opposite direction. Why is that? The wind only affects the tip of the iceberg visible above the water. The iceberg's direction is influenced by what you can't easily see. The majority of the iceberg lies beneath the water and is affected by the currents moving in a different direction to the wind. Your project is the iceberg. Your visible controls - time, cost, quality, scope and resources - only affect the tip of the iceberg. There's a lot more going on beneath the surface where the project is massively influenced by emotion, culture, learning through reflection, improving through adaptation, and sharing knowledge and building a sense of team through collaboration.

They described 4 failure modes:
  1. Inspect and adapt gone wrong. People don't apply before inspecting and adapting. The cycle should be apply - inspect - adapt. When you learn to drive you learn lots of different techniques - how to turn, starting on a hill, reversing around a corner, parallel parking, etc - because they all work together and are known as 'driving' and you will draw on them every time you venture out and drive your car. Omitting practices is akin to "Oh when I learned to drive, I never got that whole left turn thing, so I just drive straight ahead now".

  2. "You can't handle the truth". People are often not able to deal with the results of the process. Everything becomes visible, good and bad.

  3. Using the wrong tools to solve problems.

  4. Interpersonal team dynamics (communication and grouping). A team operates within a socially complex domain where cause and effect cannot be predicted. It's not possible to anticipate what will influence the 'system' and, because people are non-deterministic, it's not possible to know how the 'system' will react. Only with retrospective coherence, can we look back and, knowing how things evolved, have things make sense. You're unlikely to achieve success if you focus on predicting what's above the water.
Listen to Joseph talk at CINCOMSmalltalk about the process of software development and some of the issues that come up.

Tags: , ,

Read: XPDAY7: Why do Agile projects fail?

Topic: Windows on the Road Previous Topic   Next Topic Topic: A local remote person

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use