Project Management – Eugene Eric Kim

I recently posted an entry at the Blue Oxen Associates blog on Obama, Wikis, and Collective Leadership. The crux of the post was simple: Collective Leadership happens when it’s clear who’s in charge. (N51)

In other words, powerful communities empower their participants to lead by giving them Permission To Participate. When it’s clear that a community has thought about what needs to be done and that people within the community are doing those things, then people can have confidence in that community’s leadership. (N52)

Entangled in all of this are notions of trust and transparency. One of the simplest ways to build trust within a group is to have good Personal Information Hygiene and even better Group Information Hygiene. The path to enabling good Group Information Hygiene is transparency. (N53)

Good Project Management tools encourage good Group Information Hygiene via transparency. As a member of a project team, I can look at all of the group’s tasks, I can see what’s been assigned, and I can know who’s following through. Moreover, others can see the same about me. (N54)

In a small team with clearly defined roles, project leaders are supposed to be responsible for all of this. But by making these things transparent, project leaders engender greater trust and empower the entire team. (N55)

In a large community with no imposed authority, this is even more critical, because there isn’t anyone who has been pre-assigned with the responsibility. One of the most powerful ways to be transparent and empowering is by using a Project Management tool to openly list tasks, and by enabling anyone in the community to contribute to or volunteer for tasks. (N56)

A few years ago, I had a conversation with my friend, Steve Ketchpel, about this phenomenon, and he shared a brilliant insight. He said that most Project Management tools are not useful for empowering grassroot communities, because they assume that people who take responsibility for a task will actually follow-through. What we actually need are tools that encourage people to do their best to follow through on tasks, but that also encourage others to take over those tasks when the original volunteers don’t or can’t follow through. This is simply a reality of life in grassroot communities, and tools need to support this. (N57)

The Project Management tool that comes closest to supporting this is Chandler. Obviously, I’m biased, but I think that Chandler does a great job of making it easy for anyone to see and take on tasks. Ironically, one of the ways it does this is by not having a task assignment feature. You can sign up for a task by adding your initials to the title or description of a task, and you can just as easily reassign tasks the same way. (N58)

Fun Fact About Eugene #322: I’m obsessed with cooking shows. There’s nothing I like better on a Saturday morning than rolling out of bed, turning on PBS, and watching Jacques Pepin work his magic. What’s amazing about these chefs is that they always have a clean cooking station. Always. It’s apparently a principle they teach at cooking school, and it makes a lot of sense. It also seems to apply to other areas of life. Getting Things Done. Project Management. And of course, hacking. (K95)

Ingy dot Net (The Hacker Formerly Known as Brian Ingerson) was in town this past week, and we hacked a little bit on Wednesday night. “Hacking” with Ingy for me so far has mostly consisted of me watching him in action, catching a typo here or there and occasionally pursuing some philosophical disagreement. But it’s cool, because I enjoy watching other folks code, especially folks who are better than me. (K96)

(Earlier this month, while working on the Ruby YADIS library with Brian Ellin, I learned for the first time about command completion in Emacs using meta-backslash. Emacs has been my primary programming environment for about 15 years, and yet, I never knew about this. Very embarrassing.) (K97)

One thing that surprised me about Ingy is that he doesn’t code very fast. On the other hand, one thing he does incredibly well is that he always has a “clean hacking station.” Even when he creates temporary directories or inserts debug statements in his code, he does it in a very clean way. It’s a practice I’d like to do a better job of emulating. (K98)