Scott Berkun

Last call for resumes: project manager for pmclinic

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

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: thick vs. thin specs

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