MPD

Books, MPD

Nice Review of Manage It!

I’m pleased that here are several nice reviews of Manage It! Your Guide to Modern, Pragmatic Project Management. See the most recent: The Library’s post. Labels: Manage It, project

MPD

Product Development Survey

  Every two years, my good friend and colleague, Brad Goldense, gathers research about the state of product development metrics. It’s that time again. Here’s the information: GGI

measurement, MPD

When Is Defect Data Not About Defects?

  I taught my Pragmatic Project Management workshop in Israel last week. I was talking about defect charts and what they mean and how I use them. (No, I don’t include priority or severity data on defect charts; just # opened and closed by week and # remaining open each week. One of the participants

MPD

Whose Standup Is It?

  Esther and I were teaching a Behind Closed Doors tutorial at Better Software yesterday. One of the participants was a program manager. He couldn’t see the value of the standup meetings the Scrum teams used every day. “They talk to each other all the time–why do they need the standup? I can’t see the

conference, MPD

Better Speaking Naturally (Not Through Chemistry)

I work hard on my speaking skills–not just how I present myself on the platform, but also the content of what I say, and how I present that. I’ve almost converted to Keynote, but occasionally still use PowerPoint. For AYE, we don’t use any PowerPoint (or equivalent) at all. Here’s why. If you scroll down,

Books, MPD

Manage it! is Available

  Drum roll please… Manage It! Your Guide to Modern Pragmatic Project Management is available. (I don’t know when it will be available from Amazon. Soon, I suspect.) See the press release. I’m sooo excited. Labels: Manage It, project management

MPD

Two Good Rules

  In his recent IEEE Software column, “Ship Effortlessly” J.B. Rainsberger has a gem: I start each project with two rules: all source files must be in a version control repository, and the build must be fully automated at all times. Does your project follow these rules? If not, what would you have to do?

MPD

Services to the Organization

There are several questioning comments on my post Testing is Not a Service: What do I mean by testing and how do I reconcile my statement with the context-driven school of testing? Let me clarify what I mean by service first. The way the participants were discussing testing as a service, they meant a common

Scroll to Top