Drunken PM

by
Drunken Boxing for Project Managers “The main feature of the drunkard boxing is to hide combative hits in drunkard-like, unsteady movements and actions so as to confuse the opponent. The secret of this style of boxing is maintaining a clear mind while giving a drunken appearance.” Yeah... just like that… but with network diagrams and burndown charts… and a wee bit less vodka.
Agile | Agile 2010 | agile 2015 | Agile Alliance | agile transformation | agile2015 | AgileThinking | AOW4PM | apple | art of war | Bas De Baar | body language | branding | Brian Bozzuto | capacity | certified scrum trainer | Chris Li | cloud | cloud worker | commitment | Corkulous | CSM for PMP | cst | Dave Prior | David Bland | Digital PM | digitalpm | Docs to Go | Don Kim | dpm | dpm2013 | EMEA | emotional intelligence | Essential Scrum | facebook | field guide | FIRM REPORT | Flipboard | Global Economics | Greg Balestrero | GTD | Howard Sublett | Idea Wallets | IOS4 | iPad | iPad 2 | iPad2 | iPhone | IT&T SIG | Jesse Fewell | jim benson | kanban | Kathy Compton | Ken Schwaber | Kuala Lumpur | lacey | Leadership Meeting | LeadingAgile | lean | LeanKit | Livescribe | Livescribe Pulse | Mac | MacWorld | Macworld 2011 | Malaysia | Marshall Rosenberg | mashup | MDEC | Merlin | Mike Cohn | Mike Sutton | Mike Vizdos | mitch lacey | MITPM | modus cooperandi | Non-violent communication | Notes Plus | NVC | off shore | Offshore | Olaf Lewitz | Oredev | Øredev | overcommitment | Panda Transport | Papershow | personal branding | personal kanban | personal productivity | PMI | PMI Portugal | Product Owner | productivity | Project | project management | project manaqement | project planning | Project Potion | Projects At Work | projectshrink | ProjectWizards | pulse | Ricardo Vargas | Robyn Meredith | Scrum | Scrum Alliance | scrum but | scrum field guide | Scrum Gathering | ScrumFest | Shane Hastie | SK Khor | social media | sprint planning | SXSW | telecom | Thierry Holoweck | Things | Thushara | Tobias Mayer | Tom Perry | troy magennis | twitter | value | VCP | video conferencing | Vivek Angiras | vocal technique | waste | What We Say Matters | Wijewardena | WIzewerks | show all posts

About this Blog

RSS

Recent Posts

Certified Agile Leadership Training with Olaf

Don Kim - I Think, Therefore I Plan

Agile Coach to Agile Gamer - Peter Saddington

Scrum in School - A Case Study of Grandview Prep's Transformation

Forecasting Tools Based on Team Performance with Troy Magennis

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.

Posted on: March 04, 2013 11:18 AM | Permalink | Comments (0)

Individual Capacity Calculator

Note: The link to the file has been updated. It can be found here. (3-4-13)

(This is an update to my 10/28/12 post on How to Avoid Overcommitment During Sprint Planning. )

 

For awhile now I have been using an excel spreadsheet I put together to work out the calculations I detailed in the post on avoiding overcommitment. I have also been sharing it with the students in my CSM classes. I recently updated it so that the times allocated for the different Scrum meetings is in sync with the current version of the Scrum Guide and I thought it would be a good idea to post here just in case it can be of help to anyone.

 

In case you missed the earlier post, the intention of this calculator is to help individual team members on a Scrum Team gain a better (more true) understanding of the amount of time the can realistically commit/forecast to be able to contribute to the work the team will do during a Sprint. I have found this to be very helpful for teams who are struggling with understanding their capacity.

 

An example of how this could be used in s Sprint Planning is...

 

1. Once a Scrum Team has forecasted the amount of Story Points it can expect to get through during a given Sprint based on average historical velocity.

 

2. And defined tasks for all the stories.

 

3. And estimated the ideal engineering hours required to complete each individual task.

 

4. And totalled up the collective ideal engineering hours required to complete all the work they are forecasting to complete in the Sprint.

 

5. Each team member can use this calculator to determine how much time he/she can expect to be able to contribute in the Sprint.

 

6. Once each team member has come up with his/her number, you would total those up to get the total amount of ideal engineering hours the Team expects to be able to working during the Sprint.

 

7. If the value resulting from Step 4 is greater than the value from Step 6, then you may need to reconsider the amount of work your team is forecasting to complete in the Sprint, or modify the scope (and tasks) for one of the stories.

 

8. If the value resulting from Step 4 is significantly less than the value resulting from Step 6, you may need to consider adding some additional stories/work into what is being forecasted for the Sprint.

 

* Some teams I have worked with have taken the additional step of applying this technique by work type within a Sprint, i.e. Development, QA, UX, etc.

 

Here is the file

 

This work is licensed under Dave Prior is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.">Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License

Posted on: February 19, 2013 02:31 AM | Permalink | Comments (3)
ADVERTISEMENTS

"The only difference between me and a madman is that I am not mad."

- Salvador Dali

ADVERTISEMENT

Sponsors