Why Project Potion?
I had some emails from readers who wondered why I coin the term "Project Potion" in my book "Surprise! Now You're a Software Project Manager".
The origin of the term comes from a blog posting from 18 months ago:
I have to work on my self promotion. I am struggling to make some sense of how to combine components of different PM methods under certain circumstances. It is a a struggle, however, it deserves some attention. Well, heck, that's my opinion.
When I started reading "Balancing Agility and Discipline" by Barry Boehm and Richard Turner. And all of a sudden, it struck me…
They used the term "tacit knowledge" as a concept in agile methods. I am not a native English speaker, so, that sounded verrrrrry goooood. Later I found out it is just the knowledge in your head, instead of writing everything down.
So, to hype things up, you need good terms, great words…
And you know, no hype, no glory…
[hype]
If you are studying agile methods, you are already behind. There is already a new bread of project management approaches at the horizon.
As you know, different circumstances may require a different approach. If you need creativity to solve a problem or to create a design, you need an easy going, stimulating approach; if you are running towards a deadline to get in to production, a rigid, centralized controlled environment is more the way to go. Depending on the environment and general circumstances a project manager should construct a process and organization that serves him or her best.
[\hype]
So actually, you are going to borrow pieces from existing methods, and make one that suits your needs. Nothing new here. But I need a good name.
How about: Project Management Method Engineering?
I already see some new jobs: the project management method engineer. Or more hip: project profiler.
Personally, I would go for "cut&paste-" or "beg-steal-borrow"-approach. But it doesn't have the right hype.
[hype]
Be part of the new PM revolution. Discuss with the founders the all new Project Management Method Engineering!
[\hype]
So, I finally decided on Project Potion. As I point out in the book…
At the end of all those pages, you will feel like an alchemist that throws all kinds of liquids into a jar, mixing it up, stirring it, and creating the perfect blend, a kind of secret potion. At one time, you may need Project Potion No. 4, and on another occasion you may find yourself completely happy drinking Project Potion No. 1. Im mentioning this just in case you are wondering why this chapter is called ProjectPotion.
You see, I find it difficult to use those heavy sounding, difficult names… hope it doesn't ruin the hype :-).
If you like this post then please subscribe to my full feed RSS. You can also subscribe by Email. Not sure how this works?1 Comment so far
Leave a reply

Subscribe to my blog by email and you will receive bi-weekly a summary of my postings. As sign of my gratitude you receive the first part of my book "
Bas de Baar, blogging as "The Project Shrink", is taking his message to the International Project Management community with a vengeance: "Projects Are About Humans. Now Deal With That!" ...
[...] Although I propose picking different techniques and process components from every method that you can lay your hands on, this doesn’t mean that you can just pick a single piece from a method and hope it will work.I stress that an issue should be tackled by the introduction of a certain process component. A certain risk should be reduced. So sometimes this means that you have to add another piece in tandem with the technique you had in mind. They go hand in hand, and one without the other would be useless. [...]