iTWire reports a dozen common or critical failure modes for an agile implementation, lifted from Agile Australia 2009. It's interesting to see the angle mainstream IT press in Australia has on this theme.
The last point in the article is one close to my heart. Falling back to traditional appproaches when it all gets too hard. As the agile point man at my current engagement, I definitely know that feeling.
On the other hand, we ran our second round of UAT last week and in both it and the first round we only came across one bug of moderate significance. This is a pretty fantastic result, especially from a team who's previous release didn't even run on day one of UAT, and that's not even considering the huge schedule differences.
It seems a process that enables, rather than tries to force particular agendas can really make a difference. Once the product is more mature we might see if we can turn out a white paper on the topic.
18 October 2009
Subscribe to:
Post Comments (Atom)
Popular Posts
-
I have been having a bit of a discussion over at the IIBA blog with Kevin (VP BOK) and Julian (Chief architect.) It’s migrated over to ...
-
Due to popular demand I have aggregated some information on User Stories and created a simple template. If you feel this would be useful to...
-
Better Projects Templates I am uploading a couple of project document templates to Google Docs. As I add more I'll post them up here. You...
-
You've heard many reasons why project fail. Here is a discussion hosted by BCS on why projects work. The discussion covers four dimensio...
-
The Precedence Diagramming Method ( PDM ) was developed in the early 1960s by H.B. Zachry in cooperation with IBM. It has largely repla...
-
In the below video some of the #10yrsagile participants discuss the role of the Business Analyst. A question for you; Do you agree or di...
-
This is a guest post by Jeff Hobbs. Jeff is a project manager at ActiveState Software who provide pm and collaboration software. Email, ...
-
In one of the Carnivals of Business Analysts the theme was “ Requirements Analysis ." I searched the web far and wide and came up with a n...
-
The definition of a stakeholder is controversial. For example, project team members are generally not considered stakeholders, but in virtua...
-
I have written about the V-Model across several posts. The V model is a testing focused expansion of the software development lifecycle. In ...

0 comments:
Post a Comment