In theory, practice is simple. But, is it simple to practice theory?

Theory vs. practicing the theory

Part 1: recap of the manifesto


This post on my first blog in the "agile space" talks about the theory of agile - the methodologies, frameworks etc. and discusses why it is difficult to practice what is suggested in theory. But first things first, let me tell you why am I obsessed with Agile!


I love Agile, primarily because of the fact that it stresses on keeping things simple & focuses primarily on "people" and the "people factors" influencing software development. 

If you look closely at the agile manifesto, below are some of the things you'll observe -

  • Two out of four manifesto items are people-related -
    • Individuals and interactions (over processes and tools)
    • Customer collaboration (over contract negotiation)
  • None of the items in the manifesto talk anything about processes to follow or "best practices", so to say!
  • The manifesto doesn't stress on what tools or methodologies to use for developing software
  • Last but not the least, while we strive to embrace change, the manifesto suggests that the only way to measure progress is by delivering working software; and not by the weight of the documentation created en route to the finished product.
'nuff said, over and over again; and by now you should have the manifesto in your blood cells. 
Stay tuned for part 2 of this post!


Best,
Jasdev Singh (PMI-ACP, CSM)


Comments

Popular posts from this blog

Increasing your Agile Team's Outcome Predictability

Stop starting, start finishing.

Mastering the Daily Scrum