People spend a lot of time looking at why startups fail, and why projects fail. Requirements gathering is a different beast, though: it's a product failure. It happens during the project lifecycle, usually pretty early on, but it's the first step towards product failure, even if the project is a complete success.
This is frm a story you should read. It is at Stevey's Blog Rants.
It is definitely one side of a story. If you have a response I'm looking forward to reading it below.
28 September 2008
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 ...

1 comments: