Kanban Archive

1

What is Agile, anyway?

The parable

Ever heard the story about the blind men and an elephant?  In various versions of the tale, a group of blind men touch an elephant. Each man feels a different part, but only one part, such as the leg, the tail, or the trunk.  They then compare notes and learn that they are in complete disagreement.

Agile, my friends, is an elephant.

The first blind man

I just completed an initial engagement with a client, for LitheSpeed.  Some of the people I interacted with were newly minted Certified ScrumMasters, some experienced developers, and some executive management.  In the mix, I met UX designers, architects, and more functional roles than this blog post should list.  The catalyst of this post happened on the first day of the engagement.  To set the stage, the organization was very clear the team is to “do” Scrum.  Due to user stories not being quite ready, the team pushed back at Sprint Planning and refused to estimate or commit to the work to be done.  I recommended the group visualize the workflow and maturation of user stories by way of a Kanban. I’ve made this recommendation before and it worked out quite well.  The response from one of the newly minted ScrumMasters was, “That sounds like waterfall!”  When I corrected him, confirming that it was not a waterfall approach,  he came back with an even better response.  ”Well, it’s not Scrum.  If it’s not Scrum, it’s not Agile”.

If it’s not Scrum, it’s not Agile

A few days ago, I read a really great post by Joel Bancroft-Connors titled A Gorilla Primer: What the heck is Agile? Maybe this question is more common than I initially thought!  What I liked about Joel’s post was it exposed the fact that Agile is different for so many people.  When asked what Agile is, I tend answer the question with a question.  Are you being Agile or doing Agile?  If you are being Agile, then how?  If you are doing Agile, then how?  Before I even attempt to answer the question, I want to know your perspective.  Why?  Because as with the parable and also reality, it’s going to depend on your touch points.

Go read Joel’s post.  I think you’ll enjoy it.  When you’re done, I’m sure you’ll agree that if it’s not Scrum, it can still be Agile.

Image Source: Pictofigo (Go get one. They’re free)

2

Epics, User Stories and Tasks

I was working with a client this last week and I overheard one team member trying to explain the difference between Epics, User Stories, and Tasks.  He finally offered an analogy.

The Analogy

Epics are to User Stories are to Tasks as Rocks are to Pebbles are to Sand.

I thought it was a clever description of comparing relative size and complexity of work. But would it pass muster with the Agile Community? I figured I would send it out to the Twitter-verse and see if any conversations would result.

The result was an excellent conversation with David Koontz.

The Conversation

Though I will admit there are some challenges in communicating in 140 characters or less, it really forced me to think about what I was trying to say.  David did a really great job of challenging me to explain what I was thinking.  In tweet responses, David stated if it can fit in a Sprint, he calls it a User Story.  If it is too big to fit in a Sprint, it is called an Epic.  I have to say, if we all followed that model, it certainly would simplify things.

I find customers asking if they can call them sub-stories, major stories, and craziness like that. Customers take a stab at breaking down work to manageable chunks but when the team estimates the work, it’s still too big to fit into a sprint.  To restate David’s identifying criteria, too big equals epic; small enough equals user story.

David then asked me,

does Epic == collection of stories? Or some stories and some waste we should never do?

My response was,

I believe epic != collection of stories. I believe epic == placeholder of a goal or idea. Stories may result but no guarantee

The Clarification

To clarify my beliefs, I believe a User Story as merely a placeholder for a conversation.  I believe an Epic is a placeholder for a goal or an idea.  Along the way, there will be resulting value delivered and waste.

Though you should be able to map all of your User Stories (and waste) back to Epics, that’s not the goal.  You don’t just do tasks and then look for a bucket of stories or epics to group your efforts.

I won’t say having something small enough to fit in a Sprint is automatically called a User Story.  What if you don’t leverage Scrum?  What if you are leveraging Kanban?  In either case, we refer back to the conversations.  As long as your work meets your definition of Ready, I don’t care what you call it.

Thank you, David, for an excellent conversation.  I hope others will join in.

5

PMI Agile CoP Transparency

Back in December, the PMI Agile Community of Practice (CoP) leadership agreed we’d take steps to provide some transparency into what we are doing.  If you are curious about what we’re up to, I invite you to follow the link below.

Here is the link to our board. https://pmiagilecop.leankitkanban.com

Anyone can access this Kanban (read only):
Username: AgileCOP@gmail.com
Password:  GoAgile

What do you think?  Is this enough transparency?

Image Source: Pictofigo

0

My Personal Kanban Birthday gift

I would like to publicly thank everyone who sent me birthday wishes.  Gotta love Facebook, Google+ and all of the other places that broadcast your birthday to the world.  It’s actually pretty cool to hear from people I haven’t talked to in a while.  Rather than go into details about how I ate durian fruit or how I was convinced my wife hired a belly dancer for our dinner date with friends, I’ll focus on the good stuff.

Not only did I score several containers of coffee, but I also got a physical copy of Personal Kanban from my parents. I have Jim and Tonianne’s Kindle version of Personal Kanban but sometimes when you really like something, you just have to have a physical copy.  I honestly didn’t think I was that sentimental.

My son and I also got matching white boards to help us navigate our lives.  So, if you’re thinking of a stocking stuffer this year, get that special person a copy of Personal Kanban and some post-its.  They’ll be glad you did.

Oh, and if you look in the background of the photo, you’ll see my wife has LeanKit Kanban up on her screen.  Ya, we’re a weird family.

3

LeanKit Kanban

LeanKit KanbanWhen the Agile Manifesto for Agile Software Development was written 10 years ago, it stated “We are uncovering better ways of developing software by doing it and helping others do it.”

The very first of four values listed within the Manifesto was “Individuals and interactions over processes and tools”

The Manifesto goes on to state “…while there is value in the items on the right, we value the items on the left more.”

Well, I am compelled to write about one of the items on the right.  I still believe the tool should be good enough that it helps you reach your goals.  But after that, it should not become a big process onto itself.  What I want to do is finish tasks and get some actual closure on them.

I recently read in the book Personal Kanban by Jim Benson and Tonianne DeMaria Barry, a phenomenon known as the “Zeigarnik Effect”.  It states that 90% of people remember uncompleted or interrupted tasks better than completed tasks.  Soviet psychologist Bluma Zeigarnic found that the human brain becomes preoccupied with things that are not closed.

Though I have leveraged Kanban with teams, it took me a while to realize that Visual Control Systems could be used to visualize and manage both personal and professional work.  I then found myself using a physical board at the office and an electronic version (web-based tool) at home.

What is visual control, exactly?

A visual control is a technique employed in many places where information is communicated by using visual signals instead of texts or other written instructions. The design is deliberate in allowing quick recognition of the information being communicated, in order to increase efficiency and clarity.

The real question is, can a process tool take the place of individuals and interactions?  Perhaps we need to stop and think about the reality of our world.  Is everyone in your company physically located in the same office space or are you geographically dispersed?  If you’re not all sitting there together in an open workspace, you need to find a tool that will bridge that physical gap and then stay out of the way. Bandit Software’s  LeanKit Kanban does that.  Let me tell you what puts LeanKit in the lead of the Kanban tool race.  It’s called mobile computing.

I seem to carry my iPad with me everywhere. (I’ll be getting an iPhone as soon as my contract is up).  Though the LeanKit iPhone/iPod interface could use a little work, the iPad interface is completely awesome.  The image above is actually a screen print from my iPad.  The design is simple; it’s lightweight; it’s functional.  It helps me visualize my work and it helps control my work in process.  Merge LeanKit Kanban and an iPad and you will have an amazing user experience, as it allows individuals to interact wherever they see fit.  I’m happy because I can access half a dozen different boards with tap of my finger and my wife is happy because I didn’t cover the walls of my home office with whiteboards and sticky notes.

If you’re thinking about using a web-based Kanban tool for yourself, your team, or your organization, all of the vendors out there have relatively similar features.  See which one fits your budget.  If you or your teams are using mobile devices like iPhones, iPods, or iPads (in addition to desktops or laptops), you need to go to iTunes and download this app.  Though you need to have an existing LeanKit account to make the Apple App versions work, you can get a personal account for free!

After you see how well it works for your personal life, I don’t doubt you’ll be using it in the office in the not-too-distant future.

 

HT: Wikipedia
HT: LeanKit
HT: Personal Kanban