Ryland Leyton recently released his book, The Agile Business Analyst: Moving from Waterfall to Agile. Over the years, Ryland has provided training and mentoring for events and individual members of the Greater Atlanta Chapter of IIBA, so I was thrilled to see him take pen to paper and share his insights through a medium with broader reach. Ryland agreed to provide some additional information and background on the thought process behind the book for Practical Analyst readers.
“Agile … is an attitude, not a technique with boundaries. An attitude has no boundaries, so we wouldn’t ask ‘can I use agile here’, but rather ‘how would I act in the agile way here?’ or ‘how agile can we be, here?’”
— Alistair Cockburn
I’d like to share one of my favorite agile quotes from Alistair Cockburn, because it summarizes my own perspective so well. In my observance, many fail to differentiate agile principles from agile methodologies, and end up with a prescriptive/dogmatic view of the correct way to do or be “agile” that misses the mark.
Whether you’re working in an “Agile” or traditional delivery environment, you can find ways to apply agile principles and keep a responsive mindset.
I recently bought, read, thoroughly enjoyed and am now recommending Atul Gawande’s book, “The Checklist Manifesto“. In “the manifesto”, Gawande pulls examples from the medical field, construction, aviation and others to show how simple checklists, coupled with timely and effective teamwork, can vastly improve the quality and effectiveness of what we do; in some cases, literally making the difference between life or death. I’m sharing some teaser quotes that I bookmarked during my read of “The Checklist Manifesto” because I think they are good at conveying some of the underlying principles that solution delivery professionals will find interesting, but mostly […]
Here are just a few impressions I’ve jotted down over the past few weeks that may never evolve into full blog posts, but that I wanted to share just the same. Please feel free to chime in with your support or challenges to my list, or with your own observances.
This post is spurred by a few articles I’ve read recently which have only served to reinforce some similar thoughts I’ve been having for a while now on the constant, competitively toned comparisons between agile and traditional development methodologies.
As I read article after article extolling the wonders of these new methodologies against the weaknesses of the traditional methods, I begin to wonder if the emphasis isn’t too much on agile methodologies over agile principles.