About my blog

Why I created my blog: As a colleague, extended team member, and friend of mine recently said to me, “I need a relief valve for my occasional inner ‘geek rage'”. Through the impressive thinking of this revered IT architect, Jack-[not]in-the-box, I was inspired to [finally] pull the trigger and create this blog as my own relief valve. The ‘pressure’ has been building over the years as I’ve steeped myself in study, training, apprenticeship and application of real-life Agile-Lean development practices, team dynamics, business management, and solutions delivery. The misapplication of metrics, misuse of terms & references, imbalanced focus on the technology versus sociology, the vast diversity in understanding and application, have all stirred-up my own inner geek-rage (if you will) about Agile-Lean mindsets & methods, values & actions, principles & practices, beliefs & behaviors. Now I must include my anx about what many organizations and teams are doing and calling it Scrum or Agile!

While there is an understandably significant amount of attention on the “What” being produced as business solutions, I believe there is much more importance in the “How” and “Why” than is generally attributed. The quality and effectiveness of the solutions delivered will reflect greatly on the “Hows” and “Whys” that enabled the great “Whats’ contributing to business success. The “Whos”, “Wheres” and “Whens” will be a derivative of the “Hows” and “Whys”.

This blog forum then is spawned as a venue for opening constructive discussion with other students of their craft; for growing in knowledge, understanding and wisdom; for dispelling myths and madness surrounding the “Hows” and “Whys” behind the “Whats” that need done; for helping the “Whats” get delivered with a little more value, quality, frequency, AND FUN!  And in the end, 🙂 I hope to ultimately relieve some of my own inner “geek-rage” about “being Agile”. In doing so, I will stretch the application of Agile and Lean ‘beliefs and behaviors’ from software development to not only product development, but to personal development and interpersonal relationships. Thank you for joining me for a probing journey of thought leadership and learning while exploring the vast realm of “being Agile”.

12/7/2012 – Blog title updated to: “Grains of Rice”, as suggested by my wonderfully supportive colleagues at Manifest Solutions.

Advertisements

Recent Posts

Much needed; great timing; thanks Ken!

Ken Schwaber's Blog: Telling It Like It Is

Organizations usually don’t adopt Scrum because they like its name. Instead, they have heard that software development is better if they use Scrum – quicker, cheaper, higher quality, more satisfied customers and employees. Sometimes things are so bad in software development that they try Scrum just because it wasn’t what they were doing before.

However, adopting Scrum, becoming more agile and improving software development, costs money. It requires training, tooling, coaching. These are all investments. Scrum does not come with a set of tools for managing these investments, measuring the resultant benefits, and optimizing return on investment.

For the last several years, I’ve been developing a framework for managing this investment. It is called the Continuous Improvement Framework (CIF, yes, another acronym). CIF provides a set of management tools for continuously improving an organization and becoming more agile. Your agility is measured by metrics that reflect business value. The value…

View original post 140 more words

  1. Defend the Scrum Master role 10 Replies
  2. Is “overimprovement” possible? Leave a reply
  3. “While you were out…” 2 Replies
  4. Scrum Master or Agile Coach, and other coaching categorizations. Leave a reply
  5. Principles and/or Practices? Leave a reply
  6. Agile “Best” practices: Really? 2 Replies
  7. Agile adoption and adapting Leave a reply
  8. Holy Agile! Leave a reply
  9. This is not just my drum!! Leave a reply