The Berkun Blog

Management, design, and the making of good things.

Archive for the 'PM-Clinic' Category

No secrets: new project management blog

January 28th, 2009

I get lots of thanks and kudos for pmclinic, a discussion list about real issues managers face, despite the fact I don’t contribute much directly to the thing anymore, and Shawn Murphy runs the list. Instead it’s 5 or 10 really smart, wise people who do much of the posting and advice giving.

One of these smart, wise, clever contributors is an industry veteran named Steven Levy. Why do I mention him now? Here’s why.

He’s set up shop on his own at a shiny new blog on project management called: No Secrets.

He’s already been busy with posts on How to kill projects, and is your boss a manager or an administrator?. Check it out.

Last call for resumes: project manager for pmclinic

August 12th, 2008

I’ve received quite a few applications for this role, but there’s still time to apply. I’ll be closing the door this friday. Details on the role here:

Job opening for PM-Clinic

I’m hiring: job opening for pmclinic

July 24th, 2008

Five years ago I started a simple little discussion list called pmclinic. The idea was simple: e-mail out a real world management situation on Monday, discuss it all week, write a summary on Friday.

Unlike most discussion lists, the idea created a surprisingly high signal to noise ratio. As the months went by, without any PR or much of a web presence, the list grew. Today the list has over 1000 members. We’ve covered hundreds of situations, and the list is still going strong.

There are dozens of things that need to be done, from making the list archives public, to getting the list out of the technology dark ages. And the best way for that to happen is to hand the reigns over to someone new.

This opportunity could be great for either a veteran who’s looking for something fun and different to work on with big networking opportunities, or even a rock star intern, college student, or journeyman who’s looking for experience and to build a reputation.

Job title: Project Manager

Project: PMCLINIC 2.0

Description: Lead the planning, brainstorming, organization and development of a new online community for the 1,000+ community of leaders, PMs and managers who reside on the legendary pmclinic. Objectives include taking the list out of the technological dark ages and onto the web, while retaining the stellar signal to noise ratio, and e-mail only options, subscribers cherish. It’s a huge opportunity to play a rare leadership role on a high visibility project in the tech-sector, software development and project management communities.

The current forum has a ghetto web home: http://www.scottberkun.com/pmclinic/.

What you will get:

  • Ridiculous amounts of autonomy and leadership opportunities
  • Use of Scott Berkun, or other select list personalities of your choice, as your top henchman & aides
  • Some funding for webhosting and other basic costs
  • Serious industry fame and acclaim
  • But no salary - this is a volunteer position

Skills required:

  • Ability to lead a small virtual volunteer team
  • Talent for recruiting, nagging, rewarding, and bribing volunteers
  • Willingness to work without immediate financial reward
  • Zero tolerance for bullshit / High standards for what you put your name on
  • Pride, Passion, Attention to detail, Sarcasm, Mind-control, Omnipotence (optional, but desired)
  • Skill with (at least some of ): web development, mailing list software, wikis, web design, mastering things you claim you know but really don’t until after you’re hired, networking with people who possess skills you do not

How to apply:

  1. Re-read the above, carefully this time.
  2. Send a brief note and a resume to info at scottberkun.com
  3. No specific experience required. Just need to convince me you’ll kick ass in this role.

This week in pm-clinic: the white knight

January 29th, 2007

After a few weeks on hiatus, the pm-clinic is back. With a vengeance. New tales of management challenges and great advice await.
This week in the pm-clinic discussion forum:

I was asked by to take over a troubled project. This group is managed by my boss’ peer so I am now dotted-line-reporting to him for this project. This
senior-level manager is not happy about being forced to use me. The project teams are strong but have been micro-managed by said manager who repeatedly
puts the cart before the horse - one of the major reasons the project is in trouble.

I, as the white knight,” am being asked to keep the listing ship from completely sinking. Expectations for getting it on track are high, while still meeting some of the originally set timelines.

How do I both manage this project and a sponsor who doesn’t want me as the PM?

-Signed, the white knight

This week in pm-clinic: Innovate or die

October 30th, 2006

This week in the pm-clinic discussion forum:

Is innovation for innovation’s sake a good idea? I think not, but my new VP has it in his head that our entire organization needs to be more innovative - despite his lack of clarity about what that means. So all of the team leads (including myself) are like a pack of wolves, pacing and racing around our projects.

New ideas are flying all over the place (reorgs, new technologies, new directions), but progress on existing projects has stalled, morale is volatile (rising and falling daily), and there is a shortage on meaningful decisions about why we’re changing things, or how those changes will be made.

How can I help my VP sort out what innovation means? (Or is this some kind of leadership game where he’s testing us by watching our responses)? Or more cynically, protect my team and existing projects from this chaos until it passes?

- Innovate or die

This week in pm-clinic: Haunted by ghost employees

October 23rd, 2006

This week in the pm-clinic discussion forum:

A handful of managers that have worked together for years are good friends. One of them, the one with the least competent reputation, left over a year ago, and is now being hired back into the company as a perennial contractor (product manager).

Every time my team has interacted with him, across various contracts and on different projects, we’ve had some kind of performance problem. However given his connections, despite feedback to the contrary, he keeps getting rehired (generally with different teams each time).

What can I do, as a manager myself, to exorcise this ghost employee from my world?

- Signed, Haunted by a ghost employee

This week in pm-clinic: Killing the zombie project

October 9th, 2006

This week in the pm-clinic discussion forum:

I’m a pm for a web development company - I have what we call a zombie: a project that lives on forever for no good reason. The client continually makes rounds of tiny changes, often to things where they can’t provide specific or actionable feedback so we can’t get it right the first time. The project scope (contract) of work, sadly, doesn’t have language that caps these things as they were unexpected. So, through either politics, influence, bands of garlic, or changing the process, how do you put a zombie
project to rest?

- Hunting project zombies

This week in pm-clinic: Being shown the door

October 2nd, 2006

This week in the pm-clinic discussion forum:

After two years as a general manager, building a team of 25 from scratch, my VP is showing me the door. More precisely, I’m being asked to find a role elsewhere in the company. Yes I’m devistated, but that’s not the point.

My challenge: how do I message my leaving why I’m leaving? Most of them came to the org because of me: I recruited them on the basis of my commitment to them and the project. I don’t want to be ugly and badmouth the VP, but I don’t want to lie either. How do I message this honestly, but create the least damage for the team and whoever has to replace me?

- Signed, trying to close the door (TCTD)

This week in pm-clinic: Keeping top talent

September 25th, 2006

This week in the pm-clinic discussion forum:

For about 16 months my big problem. in forming a new team, was finding top talent - but now that I’ve nailed that goal, I have an unexpectedly annoying problem: keeping top talent. The surprising downside to having rock star people is that they know they can easily find jobs elsewhere, and they demand more from me in terms of assignments and the challenge level of their projects than most of the people I’ve managed before.

I’m starting to think I’m overstaffed - my team has more talent than I really need for the kinds of projects we’re going to have over the next year.

Should I:

  • a)  Stop complaining. This is a good problem to have. I should do whatever it takes to hold on to as many talented people as possible, regardless of the circumstances.
  • b) Call the talent’s bluff and let them leave. I’ve over-hired, and if folks feel they can do better I should let them go, working towards a balanced pool of talent to match the more balanced work I have.
  • c) Fight for bigger projects based on the talent level I have.
  • d) ?

Signed, - Trying to keep top talent

This week in pm-clinic: thick vs. thin specs

September 18th, 2006

This week in the pm-clinic discussion forum:

One ongoing debate in my world is thick vs. thin specs.  The thick camp believes that specs need to be detailed (thick) and that specifications should be comprehensive to the point that most issues are well covered and that the spec can answer most questions programmers and testers have. The thin camp believes no one reads big specs and at best a spec should cover points of contention and basic principles, leaving the rest for the programmer/tester/etc. to interpret or ask for clarification.

Where do people stand on the thin vs. thick spec issue? Do specs in your org typically go for more than 10 pages (thick)? or less (thin)?

- Signed, Thick vs. thin

This week in pm-clinic: The need for two faced managers

August 28th, 2006

This week in the pm-clinic discussion forum:

I manage a rapid prototyping team in for a major consumer software product. We partner with real dev teams from around the org, and explore out ideas they don’t have time for. The group is new and I’m under continual pressure from above to justify the group’s existence (a task of many middle managers) -  I’ve asked my team to think about ways to measure value, but I get the risks: people may game the measurements, or the measuring may kill the creative work - - but I’m asking anyway as I can use the ammunition.

So my challenge is how to satisfy the view of big management, which is measurement centric and the language of VPs, but also satisfy the needs for innovation, protecting the environment from passion killing rules and structure.

How can I be the bridge between these two views without being two-faced or deceptive about what’s going on? Or is this exactly what managers of innovative teams in more production centric organizations always have to do?

- Looking for the benevolent Janus

This week in pm-clinic: Dealing with the powerful but annoying

August 21st, 2006

This week in the pm-clinic discussion forum:

The manager for my team is one of the company founders. He’s smart, but oh man, is he annoying. He has a litany of habits that make my life, as a team leader, frustrating: from disrupting my authority in front of others, to changing his mind and then changing it back, to just being downright egotistical, snide and resistant to ideas from others. He is smart and does contribute, and listens about 1/3rd of the time, just enough to prevent the other founders from doing anything about him.

So I have to work with this man: he’s not going anywhere, and he has significant power over me, my team, and the company. So how can I protect myself and my team from his many less than delightful habits?

- Stuck in Annoyanceville


You're reading scottberkun.com, home of tasty essays. All rights reserved unless noted. You can subscribe here (RSS ).
If you're not sure how to feel now that you're at the footer, joy is free and recommended.