Posts tagged process

The Agile Manifesto:

• Prefer Individuals and Interactions over process and tools
• Prefer Working Software over comprehensive documentation
• Prefer Customer Collaboration over contract negotiation
• Prefer Responding to change over following a plan

I do admire Agile practice but here’s my take:

• People and Process has to be equal.  You can’t let people go autocephalus.  You need some sort of control, no matter what, and no matter hove heavy or light it is, to make sense of anything.  So I give these two the equal treatment.  Interaction will have to happen as mandated by the process and as a normal behavior from the people.  Tools will also serve as force multiplier.
• I agree with this.  You don’t need comprehensive documentation.  A simple set of leading documents and API interface documentation will do.  Developers is almost always capable in efficiently digesting code through minimum but informative set of information.
• Depends on where you stand… Do you do this in an open source pro-bono environment?  In-house coding?  Consulting?  Product Development?
• Just as my take on the first, there has to be some sort of a plan and this should be followed.  Of course, the plan should cater to exception mechanisms.