Agile Practitioners Aren’t Supposed to Use Flamethrowers – Are They?

Have you ever been in a flamethrower war? I sincerely hope you have never been in one like the picture, but if you have been there serving for the US armed forces, then thank you for what you did for our country! Most of us have not been in a literal flamethrower war, but some of us have been in our share of them in the virtual world. I may be showing my age, but we used to have a phrase for arguments on message boards: flame wars or flaming. They were all the rage when a social network was really a Usenet newsgroup. Now we’ve grown up to using fancy mailing lists from Google and Yahoo and we still have the same core issues around disagreements. People will make statements in a message that they would never make in a face-to-face environment.

There were arguments about agile even before the Manifesto for Agile Software Development was created in 2001 by 17 brave individuals (some of whom I’m honored to be able to call friends). Lately, I’ve come to realize that the world of arguing around agile hasn’t changed in the past 10+ years at all. The players have changed, but not the fact that we can’t all get along. In the past year I’ve seen “discuss-ments” (give me credit if you use my made up word!) around all of the following issues: [Read more...]

Your Agile isn’t my Agile!

Have you ever had the feeling someone REALLY didn’t get it?  I had that feeling recently when reading this article about the supposed weaknesses of agile.  Some of the 10 points make a bit of sense, but what seems to be missing is what happens in a non-agile scenario with the same limitations?  I decided to write this blog entry to show what I think would occur and to do a bit of a bake-off between agile and non-agile teams for each point raised by the writer of the article.  So, without further ado – drum roll please – welcome to… Your Agile Isn’t My Agile. [Read more...]

New to agile? Learn how to fail well

Is success or failure really a choice?  I don’t think it is at all.  Pretty much no one chooses to fail.  Unfortunately, we can’t just choose to be successful either.  What we CAN choose is to try to make a success out of a failure!  The old saying “Make lemonade out of lemons” really is a good way of looking at things, especially for agile teams.

Agile teams will have times when they “fail.”  I know a lot of people dislike using the words “fail” and “failure” when talking about team results.  I’m actually pretty tired of that argument because I don’t think it helps anyone.  I’d rather call a “poor result” a “failure” and acknowledge we can and will strive to do better next time.  As I say during workshops I facilitate, “I am blunt and reality based. Sometimes that means I will say things which you won’t like to hear.”  I don’t call teams “failures” or anything like that.  That would be namecalling and that is never appropriate.  However, calling results a failure is correct and leaves no room for interpretation.  I find being blunt in those situations to be more useful because teams then must face the reality and not try to sugar coat it as “not being all that bad…” [Read more...]

Agile antipattern: Target fixation

Have you ever been so focused on something that the rest of the world seemed to disappear for a while?  This can be great under certain circumstances, but in other cases it can be extremely harmful.  When someone focuses on a target and doesn’t see anything but the target we call it “target fixation.”  This can have dire negative effects!  For example, a fighter pilot can become so fixated on a target that they forget to avoid the target and run right into it.  The same can happen as we go through a curve in a moving vehicle.

Unfortunately, a variation of this can also occur to agile teams!  When it starts happening to agile teams it can be very difficult to detect and correct because everyone thinks they are doing the right thing.  It isn’t until much later when most teams finally determine this was the problem. [Read more...]

I’m a Certified Scrum Trainer (CST) – so what?

This is a companion post to last year’s “I’m a Certified Scrum Coach (CSC) – so what?” post.  In that post I spoke about the advantage of using Certified Scrum Coaches over non-certified coaches for agile or Scrum training.  I also wrote a post called “Agile Ponderings: Certification – useful or not?” where I explored what were then the current certifications available from the Scrum Alliance.  In that one I wrote that I was probably going to pursue becoming a Certified Scrum Trainer (CST) but I had some misgivings about it because of the cost and also the way the application process worked.  Apparently other people had problems with the process as well, AND the Scrum Alliance listened to the complaints.  A beta process was created and I was asked to be one of the first five applicants to use the new process.  I’m writing this blog entry to detail my experiences with the new process, but also to make people aware of how using a Certified Scrum Trainer could help their organization achieve better results. [Read more...]

Agile antipattern: Sizing or estimating bug fixes

Is the bug to the left a large bug or a small bug?  It looks HUGE to me!  Well, in reality it is probably between .5 and .75 inches long.  Not really a very big bug at all.  Why do we care? Because trying to size the fixing of software “bugs” is at least as hard as figuring out how big this bug is!

When I teach an Agile or Scrum course someone will almost always ask a question like “How do you handle bug fixes in iterations or sprints?”  When I ask “How do you want to handle them?” we get into a pretty interesting discussion.  Most people say something similar to “We should prioritize them with the user stories, size them like we do user stories and then see what fits into each iteration.”  I usually smile and ask any developers if they know ahead of time how long it will take to fix a defect.  They ALWAYS say “Sometimes.”  And THAT is the problem! [Read more...]

New to agile? Remember a user story is more than a card!

What’s wrong with the user story on the card?  It seems to have everything we need: a) short title, b) a size (in this case 2), and c) a well-written story using the standard “As a … I want … so that …” format.  So what’s wrong? Nothing!  Well, almost nothing.  The user story card is a great STARTING POINT, but it is not sufficient by itself.

In coaching Agile and Scrum teams I see many of them starting out with the assumption that the user story card contains all the information they need in order to create a high quality piece of software.  Forgive me for being harsh, but how stupid is that?  Assuming a single sentence can fully describe something which might take a few days to analyze, design, code and test seems pretty ambitious.  No, let me take that back.  It’s more than pretty ambitious, it is just not possible. So I ask again, what’s wrong with this story card? [Read more...]

What style of agile training works best?

Have you ever been in a class or training session which is so boring you felt like you might fall asleep?  Or maybe you are one of the people that DID fall asleep!  I know I’ve been there many times.  When I started facilitating sessions on agile and Scrum I knew I couldn’t do it if the sessions would put people to sleep.  I knew I had to have dynamic sessions that kept people involved and challenged them to exceed their own expectations.  I put together the best sessions I knew how and I was quite successful with it (see the bottom of the sidebar at www.agileforall.com for course results and quotes from evaluation forms).  Attendees were very happy with the results, but I knew I could do better.  Much better. I knew I could talk less and have the attendees do even more.  I knew I could better help the attendees if I could just figure out how to get information across in a different way.

Then something happened which changed my life and will help me change many lives going forward. [Read more...]

New to agile? Watch an Intro to Scrum video in about 8 minutes

My friend, Arif Gangji, and I created this video to help his customers understand why his company uses Scrum as their software development framework. I decided I really liked the video, so I’m posting it here as well. It isn’t perfect, but it is plenty good enough to get across the basic ideas of Scrum. Over time it will probably show up in a few more places on the main website, but for now, enjoy!

[youtube]http://www.youtube.com/watch?v=_QfFu-YQfK4[/youtube]

I’d love to make our next video even better so if you have suggestions please put them in the comments below.  Thanks!

Until next time I’ll be Making Agile a Reality® by pointing people to this video for some introductory information about Scrum.

Agile antipattern: Another burndown chart that lies!

sprintburndown6That burndown chart looks sweet doesn’t it?  The team finished the iteration on time.  What could possibly be wrong.  Well, a lot actually.  Notice that one day this team completed a tremendous amount of work.  Do you ever see teams really do that?  It certainly could be a symptom of allowing large stories and they just got completed that day.  But I’m not buying it.  When I see a chart like this I immediately think the team is hiding something.  Most of the time they are hiding that they changed the scope for the iteration.  They saw their trajectory and simply said we have to remove some scope in order to have a successful iteration.  DO NOT BE TEMPTED TO DO THIS!!!  There are far better ways to fail.  If a team starts to believe this is ok then they will use it as a fallback position too often.  How do I know this is the situation?  Easy, I look at the burnUP chart.

[Read more...]