A Methodology Question

19 Oct 2006 /

Let’s say your software development methodology tells you to do A, then B, then C, then D, and so on, until you get to Z, at which point, you’re done.

And let’s say you do A, then B, then C, then D, and you notice that your project is not going according to plan for reasons that appear to be related to the methodology.

What do you do?

Do you forge ahead with E, F and G, even though that now looks like the wrong thing to do? If you’re committed to the methodology, you have to, right?

Or — do you fall back on the knowledge and experience of the project manager and the project team, and rely on them to do the right thing?

And if you can rely on the knowledge and experience of the project team now, what was the point of the methodology in the first place?


No Comments on A Methodology Question »

Why not be first?

TrackBack URI

RSS feed for comments on this post

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>