Personal Kanban Week 7

Kanbanfor1

I had run across nomad8’s Kanbanfor1 physical boards at an Agile conference during the previous

year. While one part of my brain looked at them and thought, "Wow, they are really charging a lot (about $28) for something I could put together myself on a chalkboard, whiteboard or refrigerator for $0. It was difficult for this part of my brain to get a message through edge-wise because the other part of my brain was drowning it out. The other part of my brain apparently thinks if I amass a certain volume of apps designed to “improve” my productivity I will somehow magically be transformed into some hyper productive version of myself that can work a 16 hour day, spend several hours of quality time with my wife and daughter at night and still manage to get something called “a full night’s rest”.  That part of my brain was shouting BUY THAT NOW NOW NOW NOW NOW!"

Fortunately, I was able to talk myself down… probably by spending the same insane amount of money on a book I haven’t read.

When I found the app for the iPad though… I really compelled to test it out. And, it is very pretty to look at. I used it for several weeks… or rather, I tried to, did I mention it is very pretty to look at? This posting will concern it self with my review of the app. (Next week I’ll talk about what happened in between my attempts to get my world sorted with Kanbanfor1.)

The app has updated since I began testing it, so some of my concerns may have gone addressed already. I also think it is important to state up front that the issues I had with the application are not really problems with the application, they are problems with my approach to work.

The Basics

Kanbanfor1 is laid out in a very clean, basic way. You get boxes for the following:

• Things to Do
• Next
• Doing
• Waiting
• Done
• Notes

You also get a trashcan where you put the notes when they reach a state of whatever comes after done… ascended maybe?

The app is about as basic and simple to use as it could possibly be. There is a box with a “+” sign in the top left of the screen. Click it, and you get a New Task pop-up. You enter the task description, select from one of 6 colors for your task and click Done.  The task shows up in the Things to Do column. You can move it across the board. That’s it. That is all it does. I love that. It is what made me want to try it. ... (Once I came to grips with the fact that if there is a Kanban app that allows for online/offline access with sync. I am unable to locate it.)

I placed a task of each color in the notes field and used the names from the swim lanes on my physical board. I then replicated all the tasks from my board into Kanbanfor1. As far as I know, there is  no capacity for WIP limits in this app… it is bare bones, but kind of elegant in its’ simplicity.

(And did I mention it is pretty?)

While I knew this was going to be an issue, I underestimated how annoying it would become.  What I store on my iPad is only available on the iPad. This is great when I’m teaching a class or sitting on the couch, with my iPad. This is completely useless when I am trudging through an airport with a ridiculous amount of luggage. So, in those moments, I’m back to Things…, which I then re-enter into Kanbanfor1.

This lack of constant access didn’t seem to me like it should be a big deal. In practice though, I noticed that rather than updating as I go, which I do with the physical board, I was just not doing that with the app on my iPad. I ended up just capturing things at the end of the day. A subtle difference, but it meant that when I was posting the updates, I was having to look through all the tasks, figure out which ones I had completed and move them from Things to Do into Done. I lost the value that comes from the staged movement, and I lost the boost from moving it into Done when I completed it.

What was a more significant issue for me was the fact that there is no ability to change the size of the

board. Sure, you can pinch and zoom, but it just makes the stickies larger too. If you have 10-20 things to do, this board is great. If your backlog has 30-40 things in it, this board is tough to work with. At least if you are going for that whole big, visible information radiator thing. In order to get all my tasks on the board I had to create stacks. So, in "Things to Do" I have a stack of things I have to do for work. There may be 10 things in there, I have to just stack them up, maintaining priority is not easy – you have to unstack the tasks one by one, and then restack them. (If you happen to suffer from something in the neighborhood of OCD, you are looking forward to hours spend restacking tasks in priority every time you want to work in a new item.)

So what I end up with (sans the WIP limits) is stacks in each of the boxes. While I love the simplicity and I think the way the app is designed makes a lot of sense, for someone who is carrying a lot of tasks, this board will simply not work. I think if there were some capacity to manage the height of the boxes, or the size of the tasks, it may work better. Unfortunately, at least while I was testing it, this was not the case. If, however, I had a more manageable set of Things to Do, and I was always going to have my iPad with me (the way I do my phone), I think this app would be a perfectly fine solution… even without the syncing.

Help Wanted

If anyone who reads this can recommend an app that offers online and offline access with a sync to reconcile changes, that is available on IOS, please let me know. I have been researching them, but so far, it is all about the cloud. I think the cloud is great, but when I’m stuck in the actual clouds for several hours at a time, I need to be able to enter new items and make updates.

Personal Kanban Week 2

Up Jumped the Devil

Robert Johnson

I been studyin' the rain and
I'm 'on drive my blues away
  Robert Johnson "Preachin Blues (Up Jumped the Devil)"

In the second week of this experiment I added a separate post it to the board with specific goals I had for the week. These are things that in some cases included other work elements on the board, but in some cases not. To me, this was bigger picture stuff I wanted to accomplish. Being as I was on vacation, these were 50% work related and 50% personal. I didn’t accomplish all the goals initially, but this was my first step towards that. (And hopefully someday soon I will finish learning to play that Robert Johnson song.)

One of the “benefits” of Agile is not that it makes things go faster, but that it makes things you might otherwise overlook much more obvious that you can’t avoid making a choice about them one way or another. For me, this whole process has involved learning a lot about how I (personally) get things done, what motivates me, and as I’ve already mentioned, some of the dysfunction I have built into my work routines.

I should also mention that, for better or worse, I don’t keep a very strict distinction between work life and personal life. I love what I do, so none of what I do is WORK in the sense that it’s stuff I don’t want to do, but there are things that provide me with greater personal satisfaction than others. And at the same time, there is also a kind of negative weight that gloms on to the work items are inherently pleasure-neutral, but become negative because they sit around too long. (This is something I’ll be coming back to in a few weeks when I start digging more into value.)
So, my top observations I have noted for week 2…

1. Prioritize the Personal - On the days when I did the things that provided personal satisfaction first, I was much happier. This is something I learned in mid-20s living in NYC. If I got up early enough to practice my guitar and hit the gym before going into work, I was pretty much okay with wherever the day took me. I’d seen to my personal stuff and that was not sitting around competing with work, waiting to be done. Understanding that this is important and actually doing it are very different things. I have found that I have to actually force myself to do (some of ) the personal stuff first. My tendency is to just dive right into the work because I perceive that need as being more important… which is not always the case.
2. Naps are good – In the grand scheme of things I’m definitely in the “I’ll sleep when I’m dead” camp. Generally I average about 4-5 hours a night. It is not a healthy way to live… but it is a choice I make happily each day. I don’t stay up because I have to, I stay up because there is just too much I want to do. There are, however, many negative side effects to living like this and if you make a choice to live functionally sleep deprived, you have to learn how to deal with it. For me, the mid afternoon has always been a dead zone… unless I find a way to sneak in a 20-minute nap in there somewhere. It’s like hitting CTRL-ALT-DELETE on your ability to focus.
   
   Also, on the sleep topic, I am finding that meditating for 20-30 minutes before going to sleep at night is having a massive impact on the quality of my sleep. The only hitch is I have to do this before I am too tired to meditate without drifting off to sleep.
3. Down Days – In tracking how I am working, I’m becoming more aware of something I have suspected for quite awhile… I have some days of very high productivity, but they are often followed by days of very low productivity. I’ve not tried to measure this, but I’m noticing, on average, I have about 1 day during the work-week where I am far less productive than the others. Typically, this happens after one of those days where I work into the wee hours and am amazed at my productivity. Since I’m not tracking it, I can’t say for certain, but it does seem like an ebb and flow kind of thing. I’m okay with that for now.

So the most important things I learned in the second week have nothing much to do with Kanban. As far as my practice of using the board, I’m getting better at not obsessing about the cards, but I am maintaining discipline with moving them. I’ve abandoned my attempts to keep them all color coordinated because it doesn’t seem to matter right now – a card is a card.

One issue I do have is that I’m still depending on Things and I’m still working items I enter into Things that I don’t have on my board. This should not be necessary, but I see three main reasons for it:

1. My Kanban board is not always with me, my iPhone (with Things) is.
2. Over the past few years, Things has become a deeply ingrained part of how I work. I’m habitually and emotionally invested in it – as much as Evernote.
3. I’m still afraid things will slip through the cracks. Things is part of how I mitigate that risk.

I’d like to break myself of the Things habit and just do Kanban, but I’m going to have to find a way to do it that is as simple as my use of Things.

I am reprioritizing my board every morning and every afternoon. This is probably overkill, but I am still becoming familiar with the work.

I have accomplished some major work items that were not on the board or in my goals. I would like to become better at making sure everything is on the board.

There is one other major change I have noticed since I began using the board. I added a post it last week to remind myself to spend time playing Dungeons and Dragons with my daughter each day. At first, that seemed horrible to me – what kind of crap father must I be if I have to make a task card to play with my kid. But you know what… since I’ve put that card up there. She and I have played every day for 1-2 hours. And it’s awesome. We spend time together, having creative fun, I’m not working and she’d not lost in some video game. So, while my original goal of taking Personal Kanban on was to get better at managing the things I have to do at work, what I’m finding is that it is helping me get better at managing the things I have to do that are not work. This is resulting in me enjoying my life more, making more time for the things I need to do keep sane and making time for my family. My expectation is that this will also have a much greater positive impact on my life as a knowledge worker than I would get from just having a better way to juggle too much at once.

Personal Kanban - Week 1

This Dysfunction Goes to Eleven

When this experiment started one of my goals for the first time box/iteration was just to see if I could actually give up my Things task list and follow the practice with a board. I had tried a number of other productivity frameworks and found that only pieces of them stuck. (Someday someone will write on a book on how to finish David Allen’s “Getting Things Done” book and I’ll actually get all the way through it.) And while I know that limiting work in progress is a cornerstone of this type of approach, and I did set WIP limits, I decided to be a little loose with the limits since I was just guessing at what they should be.

Because my larger plan is to test out different approaches to Personal Kanban, I wanted to start as simply as I could manage. I created a task board and began to fill it with post-its. The first lesson I learned was that I had far too much in my to do list to fit on my Kanban board. I decided to limit it to the things that seemed to be the most important at the time.

The Architect of my Own Demise

The most basic way to set up my board would have been to create three columns: On Deck, Doing and Done. I know this. However, when I sat down to work on it, I began struggling with how I would be able to visually understand the different types of things I had to do. My plan was to use this not just for work, but for my whole life. So, I made a decision to start with multiple swim-lanes. This is a choice I can’t say I was entirely comfortable with. It seems to violate (my current understanding of) one of the basic premises under which this system is designed to work.  But… (I bargain with myself) baby steps. I decided that this would be an okay thing to try while I am working on coming up with a better solution.

I started off by dividing my Backlog up into 5 swim-lanes, each feeding into it’s own On Deck and Doing columns (instead of having just one of each). I was able to limit myself to one column for Done though. The reason for this is that there were/are so many things I felt compelled to work on that I was afraid if I put them all in one box, without some kind of designation, I’d lose sight of something critical. (Yes, I realize this is a broken way to look at it.) There was also a part of me that was curious about how I would work through the prioritized items once they hit the On Deck boxes. The swim-lanes I set up were:

• Work-ish: Obviously for things somewhat related to work
• Reading (later changed to Reading and Research): self explanatory
• SA/IT2: for work/volunteering I do for the Scrum Alliance and IT2
• Personal Daily: These are things I do every day that I track
• Personal: Personal projects and tasks I need to take care of
• 
  

So here is my basic organizational system:

Even with the swim lanes I was still concerned about understanding the tasks on the board. Not so much from a priority standpoint, because I can handle that pretty easily with the On Deck backlogs. The desire for clarity is more about having a visual way to quickly understand that a given task is related to (work, personal, reading, etc.) This should have been easily handled by the swim-lanes, but there were sub groups I felt I needed to identify even within the lanes. So, I began with a variety of different sized and colored post-its, each one loosely designated to belong to some kind of additional detail on a task.

One of my challenges was (and continues to be) defining “value”. I believe the multi-colored, multi-sized post-its are part of trying to define that. There are tasks that obviously provide direct value to customers, like send Client X a demo license. There are items which provide indirect value to my ability to do my job: Read the new book by Diana Larsen book, “Liftoff: Launching Agile Teams and Projects”. There is work I do volunteering for organizations which provides value for others: Review submissions for Scrum Gathering. But there are other things I do which appear to be valuable only from the perspective of their impact on my body, brain or mood. How to capture this value in relationship to other items in the list continues to be a struggle and is one of the reasons for the multiple swim-lanes in my board. (How for example do I quantify and prioritize based on value if what I am comparing is the value of sending a client a demo license, compared to the mental health boost I get from meditating each day, or maybe just sitting back to read a comic book for fun.

It would be easy to argue that the non-work items do not provide value to a client and do not need to go on the board. But that seems to me to be a pretty thin definition of value. My goal was to try to put everything on the board. The problem was, it didn’t all fit. . One of the most important things I learned that week was that if I don’t put it on the board, it isn’t going to happen. So, I needed a kind of backlog nursery, where I could dump ideas and then periodically replenish the backlog on the board from that nursery.

I decided to hold a little personal retrospective at the end of each week to evaluate how things are going. The first week was really difficult for me, not because following the process was hard – that was actually pretty easy. The hard part was that Nigel Tufnel stopped by to crank the volume on my “obsessive tendencies” up to 11. Here are the important (and painful) things I learned about myself during week 1.

• While some of the PK books will tell you to plan to do the unpleasant work first and then work your way towards the stuff you want to do, I found that if I don’t force myself to do the things I want to do, that I cram every possible minute full of the not-fun work and never get around to the enjoyable, recharge-oriented items on my list. (Remember, this is my vacation too.) I actually had to block out time to stop being productive and just sit around and read a book or play my guitar for fun.
• I was so focused on getting the items across my board as efficiently and quickly as possible that I actually spent a few nights tossing and turning in a restless series of dreams about the board, the tasks and how to move them. (The last time I had dreams like this was during my brief, but disturbing addiction to playing Doom and Quake. Unfortunately, this time I didn’t get to wake up and grab the BFG to kill off some monsters.)
• In my crowning moment of idiocy that week, I climbed off the treadmill halfway through a long workout because I realized I had not moved the card into the doing column. I was unable to continue the workout until I had the car in the right column. (Yes, I have issues.)
• Throughout the week I found I was still using Things. As eager as I was to embrace the new system, I was still afraid to let go of the method I had developed in order to keep things from slipping through the cracks.

At the end of the first week, I know I have a long way to go. I’m nowhere near ready to deal with WIP, the waste I am creating or finding a better way of doing this. But, it’s a start. And, by the end of the week I was able to start talking myself down off the ledge of obsessing about moving the cards....

But, they say admitting you have a problem is the first step to recovery.

Here is a snapshot of my board as I got ready to start on the 2nd week.

The Drunken PM meets Personal Kanban

For the past 18 years I have been developing my skills at helping people manage the work they have to do into a state of ninja-like perfection-ish. As I have progressed in my career I have had the good fortune to work on projects of varying size, duration and cost. Some have been successful, but more have not – and that is okay because those are the ones where I’ve learned the most. To demonstrate my proficiency in my chosen profession I have obtained multiple certifications to prove I know how to manage work in both a traditional approach and an Agile approach. I’ve even spent years teaching others how to get those same certifications. Along the way I also got an MBA to demonstrate… whatever it is an MBA is actually supposed to demonstrate beyond that I am willing to be in debt until I go to my grave.   And I’ve given up thousands of hours of personal time leading volunteer organizations that focus in managing work and teaching people how to get better at it.

After all that, I feel it is fair to say I am fairly well versed in how to manage projects and I’m pretty good at it.  My experiences have taught me many things… most of them the hard way. And with this, I have found only one single truth that spans all of it:

Being skilled at helping others manage their work is no guarantee you will demonstrate any level of skill at managing your own.

In fact, I think it is fair to say I pretty much suck at managing my own work. I’m not saying I am not good at getting things done. I get stuff done all day long, and usually, it is the most important stuff. But I’m not good at managing it.

When I started working in project management, this was not a problem. It was 1995. I did not have a cell phone. I had one email account and I could log into AOL from home or work via my 14.4 modem. There was literally only so much information I could access in a day. Compared to now, the information overhead I faced on a daily basis was pretty light. My weekly to do list usually looked something like this:

This is a sheet of notebook paper folded in half 3 times, so that each side contains 8 boxes just like the one above. When the section of the paper got too crowded, I’d copy the open items to a new section and start again. A single sheet of paper torn from a notebook could usually take care of my list of to-dos for 2-3 weeks. (This was how we did things back in the olden days before the Palm III.)

And now, as I am writing this, blog posting about having too much to do, Things has 170 items in it waiting for me to get to. Granted, they aren’t all due today but it is so many that even trying to manage what I am not going to do has become pretty much impossible. I’ve tried many different approaches and finally reached a point where I thought I had it sorted. At that point, my goal, with any single piece of information, was to get it out of my head and into something more responsible as fast as possible. For me, this means put it in Things if it is an action I have to take care of, in Evernote if it does not go in Things and on those occasions where I am not able to access electronics, I have my overpriced Field Notes notebook and one of those weird sticks that ink comes out of. With this I have gotten very good at making sure I capture everything worth capturing. But dealing with it after… that is where things get wonky.

This past December I found myself in the bizarre position of having to take a whole month off from work. It was that or lose the vacation time. While I’d expect this would sound like a truly wonderful opportunity to most people, it scared the crap out of me. The problem was, I had so many things I wanted to do during my vacation that I was pretty sure I’d end up just curling up in a ball on the couch and watching all 10 seasons of MI-5 again just to avoid having to pick which thing I was going to take on first.

As much as I love MI-5, I didn’t think I’d be able to cope with losing Tom, Zoey and Danny again, so I decided to do something about it. And, since one of the main things I do for a living is teaching Agile, I decided to practice what I preach and started getting set up to give Personal Kanban a try.

I’m writing this after 5 weeks of my own attempt at Personal Kanban. I've been holding a retrospective once a week and keeping a journal on how it is going.  My current plan is to keep working with it and experimenting with different practices to see what works for me and what doesn’t. I’ll be posting back to this blog about once every two weeks with updates on what I’ve learned and what I’m going to try next.

A friend of mine once told me that when he met with new clients about Agile Transformation, he tried to focus on making sure they understood that Agile was not going to make them faster, but it would make the broken ugly things so obvious that they’d have no choice but to deal with them. I’ve seen that happen over and over in my own work. I am happy (and totally annoyed) to report that the exact same thing happens when you apply the practices at a personal level. 

If you are interested in learning more about how to apply Kanban to managing your personal work, you might try Personal Kanban by Jim Benson and Tonianne DeMaria Barry.

GTD and Project Management, two great taste that... um... maybe

For about a year now I've been trying to find different ways to blend the old timey PMBOK approach with some of the tools of agile. I'm doing this because after years of suffering the after effects of a "bad experience" with extreme programming, I ended up on a gig at a company for whom the waterfall/pmbok approach was entirely useless. Their business was so wide in scope and in such a constant state of flux that an agile approach was actually the only viable option.

Cue the Scrum intro music...

And as I've mentioned in previous posts, this resulted in something of a shift in my job responsibilities. Which leads to my new project-ish idea.

The new thing I've started working on is how to incorporate GTD into my project management. I have been trying to use it to try to maintain the tidal wave of stuff I have to keep track of each day, but lately I've been wondering how those same principals could be applied to a larger venue - beyond personal productivity to actual project and program management.

I'll post updates as I work through this, but if anyone has comments or suggestions, they'd be most welcome.