Q&A: Agile Vs. Formal Methodologies

My blog has moved. You can view this post at the following address: http://www.osherove.com/blog/2006/5/15/qampa-agile-vs-formal-methodologies.html
Published Monday, May 15, 2006 11:28 AM by RoyOsherove
Filed under:


Monday, May 15, 2006 8:14 AM by Pawel Pabich

# re: Q&A: Agile Vs. Formal Methodologies

Great questions, I'm looking forward to all answers.
Monday, May 15, 2006 9:04 AM by AndrewSeven

# re: Q&A: Agile Vs. Formal Methodologies

I wonder if its time to start using a different term for non-agile project types.

The agile methods have an informal feel to their activities, but they are still formal about what activities should (must) be undertaken.

Planned, formal plan, death march ;)
Monday, May 15, 2006 11:01 AM by Bob

# re: Q&A: Agile Vs. Formal Methodologies

I think a death march is more about unrealistic expectation than methodololgy.

I think the bigger competition is Agile or Formal Methodologies vs. cutting corners and putting out a less then quality product. At least in in-house projects. Its hard to convince developers to switch to unit testing from hardly any testing because there is no time. And I think its hard to get managers to switch because its easier to blame one of the programmers when the project fails than to adknowledge they over promissed or even worse they're boss over promissed.
Tuesday, May 16, 2006 4:30 AM by Matan Holtzer

# re: Q&A: Agile Vs. Formal Methodologies

"Unless you are working on a project with Fixed Price, Scope and Time, Agile is a good way to go." -
Every VSTS presentation I've been to starts with defining the "problems" that VSTS, by employing Agile methodologies, is adressing. These problems are, quite simply, never being able to end a project while keeping it On Time, On Budget and On Scope.
I thought that these are the problems that arise naturally when working on a project with "Fixed Price, Scope and Time"...

How can these two notions coexist?