Five steps to kicking off the formal project

By guest blogger Brad Egeland.

Customers matter. The size of the project matter. But in the big project management scheme of things, there are some high-level tasks that can be fairly standard from project to project. Yes, there is obviously some variance, but the general idea is pretty much the same – within specific industries, of course.

Five steps to kicking off the formal project
What I’m going to outline here is five important considerations – and basically steps – to follow to get your project started off on the right foot from the beginning. Do these as carefully and detailed as you can – taking budget and time into consideration, of course – and you likely won’t find yourself a month into the project sorting things out with the customer, team and other stakeholders trying to get them all on the same page and your derailed project back on track.

1. Review everything that’s handed off to the PM
You should have some starting point – some document that in some way at least resembles a statement of work (SOW). Review it – know it so you can recite it in your sleep. It should cover general milestones on the project, expected deliverables, key roles for project team members, assumptions, etc. This will provide necessary input into the project schedule as well as the basis for discussion at an official project kickoff session with the project customer, team (what’s assembled to date), senior management and any other necessary stakeholders.

2. The introduction – meet with the project sponsor before kickoff
Prior to official project kickoff, the project manager must connect with the project sponsor on the customer side. An introduction needs to happen as well as an on the phone (unless they are local) planning session for when, who, what and where will happen with the project kickoff session. The project manager needs to be in control and drive this discussion, primarily because from this point forward they are the person with the ball and the leader who will present and conduct the kickoff session to get the project officially started. At the end of this call you both should know the date, time, and primary discussion topics for the kickoff session.

3. Create a formal meeting agenda/presentation
Next, the project manager should put together a draft agenda (to be approved by the project customer) as well as a presentation for the kickoff session. Likely this should be a presentation deck planned for a full room discussion that includes the key players for the project. At this point those will likely be:

– what’s been assembled of the delivery project team to date
– customer side subject matter experts (SMEs) and end users
– a few senior management participants on the delivery side (PMO director, a VP or two, and any critically relevant department heads)
– customer project sponsor
– any other stakeholders deemed critical decision makers or participants at this point (only on a need to know basis, though)

4. Set customer personnel participation levels in advance
One thing the project manager must do in order to stay in control from the outset – and I learned this the hard way on a big ERP-type project – is limit the size of client-side participation. It was a huge project (18 months and multi-million dollar) and for representation on the delivery side we had 3-4 of us (me as the PM, our PMO director, and a couple of VPs, I think), but because I was doing this at the client site they brought everyone. Every end user, every SME, several department heads…anyone who would be interfacing in any way with processes affected by the new implementation. While, in the long run, their input is needed, the formal onsite kickoff session is not really the place for that. What should have taken 2-3 hours ended up taking two days because everyone had input and questions and it became extremely difficult to stick to the agenda and maintain control of the discussion. My kickoff meeting became more of a pre-design session…not the direction it should have gone and it was a great lesson learned for me. From that point on I made sure I set expectations on attendance and what should really happen at these types of meetings in order to ensure maximum effectiveness.

5. Set expectations going forward
Finally, plan out what happens next. As the project manager, you already know what you’re planning for next in your project schedule. Even if you’ve shared that with the customer at this point – and you should have – you need to set those expectations in stone as the kickoff session closes so that meetings, travel arrangements and other details can be made and worked out in people’s schedules so the project can continue forward on time and on budget.

Depending on the size of the project, the visibility of the project, it’s length, duration, price tag and probably a few other variables, this list may be longer or shorter. Or what goes into each step may be a larger or smaller effort requiring different levels of detail and participation. But these are definitely some of the key, basic steps need to be followed. Setting expectations is key as you can never be sure you’re on the same page as the client. What would you add or change about this list? Please share your thoughts and discuss.


brad-egelandBrad Egeland is a consultant and author with over 25 years of software development, management, and project management experience leading initiatives in Manufacturing, Government Contracting, Creative Design, Gaming and Hospitality, Retail Operations, Aviation and Airline, Pharmaceutical, Start-ups, Healthcare, Higher Education, Non-profit, High-Tech, Engineering and general IT. He is married, a father of 11, and living in sunny Las Vegas, NV. Visit Brad’s project management blog.



Try Projectplace, an all-in-one work collaboration tool.
Sign up for free

Leave a Reply

Your email address will not be published. Required fields are marked *