Agile and Process


Agile manifesto explicitly states that agile values individual and interactions over process and tool.

 

What does it really mean? Does it mean…

…do not be a slave to the process, or

…it is not necessary to have a clearly defined way of working, or

…every individual can choose to work in his own way, or

…every team should decide their own way of working, or

…within the guiding framework of the methodology adopted, the team should tailor it to suit its liking.

What is a Process?

  • Daily stand-up meeting?
  • Daily build?
  • Code peer review?
  • Writing regression test?
  • Retrospective meeting?
  • Source version management?

I can go on and on with this list but the point is if you have decided to adopt some of them would you allow a team member to not follow it?

Would you allow one team to drop the practice?

More Reading

Comments
3 Responses to “Agile and Process”
  1. Gene Hughson says:

    If Agile cannot be tailored to its circumstance, how can it claim to be “agile”? I think the dogmatic instances that can be found say more about the practitioners than the practice.

Trackbacks
Check out what others are saying...


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: