Project Management Central

Please login or join to subscribe to this thread

Topics: Agile, Business Analysis/Requirements Management, Outsourcing
Was the original Agile Manifesto really drafted by programmers and not project managers?
Network:811



It seems there was a Cold War that existed between programmers and project managers, with regards to communications with business owners when delivering applications.. Can anyone shed more light on this?
Sort By:
Network:14704



It's one of those urban legends, just like the story that it was all done together in one meeting, when in fact it was a series of meetings and communications that produced the manifesto. The important fact was not how it was created, but the fact it was created.
Network:1680



First of all, there is not a cold war between programmers and project managers. Second, I worked with most of the manifesto authors when we worked together at OOSPLA and mainly with Arie Van Bennekum when I was part of the group of authors of DSDM versions 1 and 2. Manifesto´s authors (by the way, Manifesto is the application of Agile to software and the word software is used into it for a reason) were project managers leading important projects inside organizations like Crysler, NASA, etc. In fact, inside Manifesto Principles you will find the word project.
Network:1151



Stanley -

the content of the Manifesto was not a rebuttal of PMs or project management but rather a wake up call for everyone involved in developing and delivering solutions.

Kiron
Network:620



They were consultants, not project managers. All had software development background and most had their own (Agile) framework.
In my opinion the authors were development managers (old style), a role that required a lot of project management skills in top of technical skills specific to software development.
Network:620



The manifesto does not mention roles. It is a collection of values and best practices called principles.
Some of the frameworks in use at the time (i.e. XP) had the role of Project Manager.
There is a big confusion regarding the 'Developer' role defined in Scrum. Developer doesn't mean coder (programmer) but anyone who contributes to the development of a product. Maybe some developers won't know but the PM has a huge contribution to the delivery of a project. A product increment (release) is always a project even when it's not formally defined as such. It has a scope, a defined timeframe and the budget to do it.
Network:620



The idea that there is a 'cold war' between programmers and PMs is ridiculous. Most programmers will become PMs as the next step after Team Lead of Dev Manager.
Network:620



BTW. Business Owner is a Project Management role. It doesn't need to be related to a software product.
Network:811



Thank you Sergio, Sante, Kiron and Stellian. Please would you be kind enough to look up this video by Bob Martin, discussing the future of programming, as he does a flash back, recalling being one of the authors of the original Agile Manifesto and what he says about the invasion of the project managers?

https://www.youtube.com/watch?v=ecIWPzGEbFc&t=3626s

Please login or join to reply

Content ID:
ADVERTISEMENTS

"In opera, there is always too much singing."

- Claude Debussy

ADVERTISEMENT

Sponsors

Vendor Events

See all Vendor Events