Mainstream Agile and Scrum in Software Development Projects Today -- Scrum Cartoon -- Mainstream Agile and Scrum in Software Development Projects Today

Hi. It’s been a while since posting something up here at

Over the years, I have shifted a lot of my internet interactions over to Twitter and Facebook (a few places).

And to think when this blog started, these things did not even exist.

Heck, the Apple iPad was not even around us two years ago. Time flies.

One of the things that has not really changed over the past six years (since I have been blogging out on are the tough conversations we have to have.


My fun cartoons and continuing to figure out how to bridge the gap between people and communications on a Scrum Team at work.

Side note: The original posting for this cartoon can be reviewed at

Let’s limit them to our professional lives (as sometimes these conversations do not apply to our personal lives [for some people!]).

Over the years, Scrum has become the leading technique out in our little Agile world. It has crossed the chasm and entered into the mainstream.

Scrum is leading the charge to organizational change — both small and large (and even enormous) — claiming “we’re going Agile.”

Here’s the thing.

It is both a curse and a great benefit to many.

For those that really “get” it (whatever “it” is… and this could lead to some great discussions) Scrum is a game changer.

Huge benefits.

Unfortunately, this is a pretty small percentage of people, teams, and organizations.

Of course, this is not stopping the even larger percentage of people, teams, and organizations who are claiming to be “Doing Agile” or “Trying Little Parts of Agile.”

Remember… Scrum does NOT equal Agile.

Scrum focuses mostly on interactions between people.

Not the technical bla-bla (this technical bla-bla is what your customers hear when their eyes are glazing over like that awesome covering on Dunkin Donuts [which BTW has been YEARS since I have had one yummmmmm]).

So what’s up with this posting?

Is it just another rant?



It may just be the reminder to start calling what you are doing today what it really is.

And. It is probably not Scrum.

It is probably not even Agile.

So. What the hell are you doing?

And. Does it matter?

I write (and talk) a LOT about Scrum and starting the tough conversations in software development.

Where can you start the conversation?

With who?

And why?

My next couple of  postings — AND comic strips — will talk about one of the most common conversations I have today when working with organizations who are trying to “Adopt Scrum.”

It’s a tough one, but one I have almost *daily* now with people all around the world.

I’ll share that with you — and be totally transparent — about this conversation and why it is SO important to have before you even get started with trying to “Adopt Scrum.”

Until then.. think about my challenge above.

Where, who, and why do you have to start having those difficult conversations?


  1. Ajeet Nayak says:

    I like the statement “Over the years, Scrum has become the leading technique out in our little Agile world. It has crossed the chasm and entered into the mainstream.”

    Mainstream means core businesses and that means even tougher conversations with the stakeholders. I wish it soon means more companies are now wanting to try Agile and hence it becomes a lot easier to have the tough conversation with stakeholders due to increasing mainstream case studies.

  2. Ajeet,

    The conversations are still tough. Now they just apen a lot more often. In an upcoming post I will reveal how one of those conversations sound. Until the, and even after that, it will be up to you and others to start having the tough conversations.

    Thanks again.


  3. We are coming up on the 1st anniversary since I began sprinting with my teams. It is becoming more and more clear to me (and my upper management) what a game changer this is.

    The transparency of the process is profound; managers are forced to make hard decisions and we are now conciously incompetent. This also means alot of friction and the “small process change” I implemented last year is spreading out from the teams into the organization.

    Now begins the difficult part I think. Motivating the change outwards, handle managers that are uncomfortable with the situation and keep improving on what we in the teams do.

    Thanks’ for the good texts and cartoons you post here.

  4. Congratulations on the year of doing this. I am sure you and the team and the stakeholders have learned a TON so far.

    Keep learning!

    - mike

  5. hey there: just popping in on your site. just some courtesy feedback. I was planning on subscribing then that awful intrusion popped up square in my face… eye-balled me. So if i was not a UI head I would not of subscribed. its AWFUL. It counters your cred built thru the tone of your cartoons. people will subscribe if they want to. trust your essence shines thru. just my view. cheers

  6. Hi,

    I totally appreciate your feedback (especially from the UI perspective). I hate it too (and have written that “when” the box pops up)… but I have learned that even if it does not make UI sense AND I personally hate those things (I *really* do) I have found that little pop-up box to be an effective way of subscribers to sign-up.

    Thanks for the feedback and I am continuing to monitor that.

    - mike vizdos


  1. [...] last posting discussed the implications of calling Agile the same thing as Scrum and well, we learned that [...]

  2. [...] it is hitting the mainstream people are thinking this Scrum stuff is the Silver [...]

Speak Your Mind