Meetings as a Blunt Instrument

This week I’ve come to appreciate the simplicity of dedicated colocated teams. The cross-fuctional project i’m managing has team members distributed across 5 floors. Of course, each team is working on more than one project, all of which require multple meetings in a given week. What this means is the time-honored best practice of Management By Walking Around is just impossible. By the time I get to one team lead’s cube, they’ve been sucked into another meeting via their blackberry.

In a large IT matrix organization, the temptation is to optimize around funtional teams: the DB team, the GUI team, the mainframe team, etc. The teams all sit together, working on tasks organized around a specific functional knowledge, rather than the projects they work on. Of course, each functional team is working on several projects at once. As a result, I am exhausted trying to walk around getting questions answered. I’m beginning to appreciate the temptation to resort to “manage by email”…it’s just too hard to track everyone down face to face. So until I can convince the world at large to optimize around project teams, I have to utilize the secret weapon of large organizations: schedule a meeting of my own.

I have now scheduled one-on-one coffee breaks with each of my team leads, so that I can get an informal status from them well before the official weekly status meeting. In contrast, when I’ve worked on colocated Agile project teams, a quick sidebar gets me the answers I need in real-time. No hunting down people; No scheduling a conversation; just question-anwser. It also has the side-effect of updating the other team members with the same info.

Alas, in matrixed project organizations, you must journey vast and far to find your project members. So here I am, resorting to meetings to overcome everyone else’s meetings. It feels like schoolyard tactics: retaliating with the blunt instrument that I’m being clobbered with.

20 Years Of Agility: Reflections, Tough Questions & Surprising Answers

As we approach the 20th anniversary of the “Manifesto for Agile Software Development”, it’s time to ask some big questions: Are projects really any more successful these days? Have companies truly shed any of the bureaucracy? Are professionals actually feeling the empowerment we’ve been fighting for so long? And where are things headed in the next few years?

Leaders Lean Into Ambiguity

This past year has taught me one lesson over and over: people need clarity to do great work. Yet too often, we hesitate to be the ones to provide it. When the path forward is unclear, we hold back, waiting for someone else to step up. But here’s the truth: clarity...

YES, Racial Justice Matters at the Office

We are at an inflection point in the american conversation about institutional racism. As project managers, departmental directors, VPs, scrum masters, we have influence in that institutional system. Therefore, we have a professional obligation to create a safe space for our black and brown colleagues, during this crisis moment. Here are 5 things you can do to promote racial justice and equality at your office.