As humans we learn by analogy, metaphor and simile, adding new knowledge by initially relating the new to our existing understanding of the world. When we try to explain the software development process to the initiated (translation business stake holders), we use all kinds of similes to help them understand the process. The problem with similes is that they argue that something is like something else and many times people confuse the similes with metaphor, thinking that one thing is another. Not only do people confuse simile with metaphor, but many of the similes we use in explaining software development are not appropriate because they can cause more harm than good and they are not very accurate in their explanation.
Thoughts on Agile Coaching
When I tell people I am an Agile Coach, unless they are in IT, I tend to get a lot of strange looks. Most of the time they will say something like, “I get the coaching part, but what the heck is Agile?” It is at this part of the conversation that they experience immediate regret as I launch into an endless barrage of commentary on Agile development.
Lately, however, I have begun to re-examine my own assumptions about what it the Coaching aspect of an Agile Coach is, especially now that there are so many professional coaches looking for work after the end of the regular NFL season.
Larry’s Top Ten Agile and Scrum Myths
I gave the Larry’s Top Ten Agile and Scrum Myths talk to the Java Users’ Group in Phoenix recently and people have asked me what the top 10 myths are. I have posted a copy of the powerpoint, but for quick reference, I have listed below.
- Myth #1 – Agile is a Framework/Methodology
- Myth#2 – Agile Means No Documentation
- Myth#3 – Agile is Less Disciplined / Easy
- Myth#4 – You Can Achieve Agility Without Organizational Change
- Myth#5 – Agile is Scrum
- Myth#6 – Scrum Will Lead to “Hyperperforming” Teams
- Myth #7 – You Must Get 100% of all Stories Complete or You’ve Failed
- Myth #8 – Scrum Master = Project Manager
- Myth #9 – We Can Do Scrum Without a Product Owner or Many P.O.s
- Myth #10 – With Scrum We Can Make Changes Whenever We Feel Like It
Now feel free to rip into these as you wish!
Larry’s Presentation to Java Users Group
Last night I had a wonderful experience presenting to the Phoenix Scrum Users Group on Larry’s Top Ten Agile and Scrum Myths. It was a very friendly audience and there were a great number of comments and questions from folks representing the whole Agile spectrum.
I have uploaded my PowerPoint file of the presentation for those who are interested.
Recent Agile Speaking Engagements
Boy it’s been some time since I have blogged! I have been busy with all things business, personal and have had a great number of recent speaking engagements with any free time I have been able to find. I am passionate about Agile and love the opportunity that speaking brings.
My most recent gigs included a bunch of talks when my body was suffering a annoying fall head cold.
Are You a Scrum Master? Be a Gardener.
I have recently been reading Jurgen Appelo’s book Management 3.0: Leading Agile Developers, Developing Agile Leaders. For those wondering what management’s role in an Agile organization should be then this is a good read.
In my current consulting gig I am coaching someone to replace me as a scrum master so we spend a great deal of time talking about Agile, Scrum and what it means to be a scrum master.
One of the things I have always used as a metaphor is the concept of Scrum Master (and managers) as gardeners. Though I may have heard it somewhere and forgot it or it may have reached my subconscious somehow, I came up with the metaphor of gardener because my in-laws live with me and are retired. They spend a great deal of time gardening. It is from their work bringing forth trees, flowers and mountains of vegetables that I took my cue.