Skip to main content

Key to success: preparation

I've watched today "The Mechanic" with Jason Statham in the main role, as a paid killer. As always, ingenious ways of making the most well guarded people lose their defence, and get them killed, and a lot of action and muscles.

One quote though raised my attention and was a guiding line throughout the whole action: "amat victoria curam", or "victory goes to those who prepare", or... in order to succeed, you must first prepare. It is not a new discovery, just a restatement of something that we've known since ever, and that we always forget about in the rush of our lives. So I am not going to teach you how to leave your life...

When we try to apply this principle to project management, it becomes obvious that this is what we have to do, and this is what the theory states so boldly. When preparing for the PMP certification, for example, the topic where you spend most of your time is on planning: you have to plan everything: your resources, your communication, your financial, your procurement, the quality, the acceptance, and of course the risk.

It is important to leave nothing to chance, and try to foresee almost everything about your project. You also need to find the right balance between planning and execution, of course - if you spend most of your time in planning, and thinking about what might go wrong, it's not good - but rushing into execution is as dangerous.

But... what is the right amount of time to spend in each phase of the project? There are many answers to this question, and - depending of the project type, domain, business needs, clarity of objectives, existing expertise - you might spend anything between 10% to 30% in drafting your plan.

What I usually do is plan the major milestones of the project, and go down into the details of the first phase, and maybe the second one as well, and the rest stays a little bit in the fog. As the project progresses, you will uncover more details, you will better understand the project environment, your stakeholders, the expectations, and you will be able to detail each phase.

During the project plan development (and as the project progresses), it is important to review your assumptions, and make sure that they still hold true - or re-assess them. You should avoid being too over-confident about your plan, as circumstances can become deceiving. Use the incremental development method, in a rolling wave style, and your project will be a successful one.

Coming back to the movie, you might believe that finally the son of McKenna has accepted that Arthur has killed his father and he's fine with that - but the end proves it completely wrong. No, I won't spoil the ending, I let you watch it first.

Oh, one last point: you should not confuse planning with scheduling: you should start the scheduling only when you are done with the planning, and you know WHAT you want to schedule. You need to decide WHAT your project is about and HOW you want it done, before scheduling all steps.

What are are success factors, from your point of view?

Comments

Popular posts from this blog

Getting PMP certified

I've got a lot of friends asking me about how to get certified. Each time, I had to remember how many hours of experience one had to have, and how many hours of learning, and then which where the links that were most useful for me, as well as all the books and software I have ever used. In terms of specific requirements for getting certified, the best resource will always be pmi.org, with a direct link to the requirements: PMI site - Obtaining the Credential . The site lists a credential overview, and then there (currently) 5 handbooks for the 5 available certifications. There is also a page with how to prepare for the exam, from an administrative point of view. If you are new to project management, then you will have to go with the CAPM certification. Then, the rest of certifications are for more and more experienced PMs. I only know well about the PMP certification, as it's the one I've got. First step is to ensure that you meet the elgibility requirements. At the t...

How to handle whiners

We are all going through stressful situations and times. Yet, some handle better the stress, while others tend to stick into the complaining mode. I was actually these days in one such meeting, and it was really interesting to observe the tone and message of the various people when they were raising issues in a large audience: some brought up issues and tried to listen and understand the answers, while others were just continuing to ramble with their own minor issue (which was, of course, exploding in their face). So I was a bit puzzled why this was happening, and starting to search to learn and understand how to handle these reactions. Whining vs. Venting: What’s the Difference? Whining: Attitude : Whining typically stems from a negative attitude. It’s repetitive, unproductive complaining without seeking solutions. Focus : Whiners often focus on problems without considering potential fixes. Energy Drain : Whining drains energy from both the complainer and...

[Goal driven] Why should I care?

A few days ago, I was on a call where we were discussing the status of each person's projects and ideas. One individual was visibly upset because their project wasn't progressing as quickly as they had hoped. The reason? The people they were relying on weren't being as reactive as needed. The facilitator had a brilliant approach to this situation. Instead of letting the person dwell on the lack of support, they suggested looking at the story from a different angle: rather than waiting for others to take action, why not drive the action yourself? Don't just stop at proposing ideas; take the lead and make them happen. And this is especially important when the project is important for you, but for the other party it’s just one more thing to do on their plate, and maybe not even a top priority. When you’re telling yourself the story of “they don’t care about this important project”, don’t forget to consider the story from their shoes as well.  Also, way too often we tend to...