Retired course

This course has been retired and is no longer supported.

About this lesson

Most projects will have a specific date or event at which the stakeholders will approve the Project Charter in order to authorize work to begin. Often this immediately followed by a kickoff meeting with the project team and stakeholders to ensure alignment on project goals and objectives.

Exercise files

Download this lesson’s related exercise files.

Approval and Kickoff.docx
63.2 KB Approval and Kickoff - Solution.docx
62.9 KB

Quick reference

Approval and Kickoff

Most projects will have a specific date or event at which the stakeholders will approve the Project Charter in order to authorize work to begin.  Often this is immediately followed by a kickoff meeting with the project team and stakeholders to ensure alignment on project goals and objectives.

When to use

Projects can be approved in many different manners.  Large projects are often approved as part of a strategic planning or annual budgeting process.  During those meetings many Project Charters are reviewed and a subset is selected for approval.  Smaller projects are more likely to be approved at staff meetings or business review meetings.  Externally funded projects are often approved when the contract is awarded by the customer or funding agency.  Regardless of how the project is approved, the project manager will normally call a Kickoff meeting at the start of detailed project planning to explain the elements of the project charter and ensure alignment with all key stakeholders.   

Instructions

The Project Charter approval process is driven by local practice and procedures. The only best practice is to do it!  The project manager and project sponsor should have a clear point when the project manager has been authorized to begin work.  At that point the project manager will acquire a project team (unless one has already been appointed) and initiate any project accounting that must be done with Finance or Purchasing so that the project can begin to spend money. 

In many organizations, this authorization is part of a formal stage-gate or toll-gate process.  The business leadership reviews and approves the Project Charter and the project is authorized to start work.  However, in some organizations or for some category of projects, the authority to start is much more informal.  The project manager will meet with the sponsor in a one-on-one meeting, or the Project Charter may be one of many items covered at a staff meeting.  In fact, the Project Charter may not even be a formal document, it may just be an action item assigned from the meeting.  If the approval is informal, I still recommend that you follow-up with a formal email or other document that provides the elements of the project charter with the date and authority for approval.

Regardless of how the approval is received, it is always a good idea for the project manager to conduct a kickoff meeting.   This meeting is used to answer any questions about the project and to gain alignment among stakeholders on the project goals and objectives along with any assumptions or constraints.  The attendance at this meeting should be the project sponsor, the project manager, the project management team and any other team members who have already been identified.  In addition, the meeting will sometimes have customers, suppliers, operational and functional managers, along with any project management support.  Basically it will be any of the key critical stakeholders that were identified during the stakeholder analysis.

This is an important meeting, especially if the project manager or some of the team members do not know each other.  There is an old saying that, “You only get one chance to make a first impression.”  This kickoff meeting is the first impression that many of the stakeholders will have for how this project will be managed and executed.  It is a great time to clarify expectations, build team comradery, establish team ground rules for communication and decision-making, and start the planning process. During this meeting the context of the project should be clear: a customer need, a business improvement, a technology upgrade, or a regulatory requirement.

I often use the “W’s” as an outline for this meeting:

What:  the intended project goal or objective.

Why:  the reason the project is needed.

Who: the project stakeholders and team members.

When: the project start date and desired finish date.

Where: location of key project activities (if the team is not co-located)

How: assumptions and constraints around the options available for planning and executing the project.

Login to download
  • 00:05 Hi, I'm Ray Sheen.
  • 00:06 Let's flap up this discussion of project initiation by talking about the approval
  • 00:11 of the project charter and the project kickoff bidding.
  • 00:16 The project charter documents the project goals and
  • 00:19 project objectives along with some key assumptions and constraints.
  • 00:23 The approval of that charter is an approval by the stakeholders for
  • 00:26 the project to actually get under way.
  • 00:28 The project manager can recruit team members and
  • 00:30 begin to spend money associated with conducting the detailed project planning.
  • 00:35 In many companies, this approval is made at a formal stage-gate or
  • 00:39 tollgate meeting.
  • 00:41 This is especially true if the project is a large strategic one or
  • 00:45 it is a capital intensive project.
  • 00:47 In those cases, the business wants to have a formal recognition of the project and
  • 00:51 ensure that the goals and boundaries are documented.
  • 00:54 For smaller projects or
  • 00:56 smaller organizations, the approval may be less formal.
  • 00:59 It may come from a staff meeting or with a one-on-one meeting with the sponsor.
  • 01:04 On more than one occasion, I've received formal approval for
  • 01:07 a project based on a hallway conversation with the boss.
  • 01:11 When that happens I still recommend following up with an email or
  • 01:14 some other form of documentation that the project has started.
  • 01:18 If this project is likely to be a big spender, this formal approval is needed by
  • 01:22 finance to setup a cost account that we'll use for tracking the project cost.
  • 01:27 Approval of the project charter is directly tied to the project initiation
  • 01:32 context.
  • 01:33 Let me explain.
  • 01:35 There's a reason behind doing this project.
  • 01:37 Most organizations are resource constrained.
  • 01:40 When they decide to do one project,
  • 01:42 they're giving up the opportunity to do some other projects.
  • 01:45 Because they won't have enough money or people.
  • 01:47 The approval of the project occurs with the understanding that the project is
  • 01:51 focused on or constrained towards reaching the specific project objectives.
  • 01:56 That objective could be to satisfy the needs of a key customer or stakeholder.
  • 02:01 That objective could be to implement changes to business processes or
  • 02:05 products as part of a change in business technology or strategy.
  • 02:09 It could be to fix a problem with the current projects, processes or services.
  • 02:14 And sometimes the project objective is to ensure compliance with new or
  • 02:18 modified regulatory legislative or social requirements.
  • 02:22 This objective constraints a project team to ensure project resources
  • 02:26 are applied to the priority that has been set by the business stakeholders.
  • 02:30 By understanding why the project is done, they can optimize project performance.
  • 02:35 The context also affects the risk sensitivity of the project.
  • 02:39 For instance, a project incorporating a new technology may be focused primarily on
  • 02:44 risks associated with proving that the technology is effective,
  • 02:47 even if it takes longer than planned.
  • 02:49 While a project that is addressing a regulatory requirement will be focused on
  • 02:53 fully complying by a certain date specified by the regulator.
  • 02:58 Much of the day to day decisions of project management involve risk tradeoffs.
  • 03:02 Understanding context is essential for making the correct decisions.
  • 03:06 This context can be explained to the project team during the kick off meeting.
  • 03:10 This will help them understand the constraints that are being imposed and
  • 03:14 help them minimize risks to the objectives.
  • 03:17 So let's talk about that kickoff meeting.
  • 03:19 The meeting has many purposes, they include, starting project team-building,
  • 03:24 laying out the ground rules for project planning, and
  • 03:26 how project communication and updates will be handled.
  • 03:29 Articulating the project objectives to ensure all of the team are on the same
  • 03:33 page, and clarifying constraints to clear up any confusion or
  • 03:37 doubt about how the project will be planned and managed.
  • 03:40 All of these serve to align the project team and get them working together.
  • 03:45 There's an old saying you get one chance to make a first impression.
  • 03:48 This kickoff meeting is the first impression about the project for
  • 03:52 most of the project team members and stakeholders.
  • 03:54 If the meeting sends a message of confusion, disorder or
  • 03:58 bureaucracy, that first impression would be hard to overcome.
  • 04:02 So plan the meeting.
  • 04:03 Decide what you will say, who will present, and
  • 04:06 how you will engage the stakeholders.
  • 04:09 Ensure that all of the project core team attend.
  • 04:12 This is also the opportunity for core team members who are working together for
  • 04:16 the first time to make their first impression.
  • 04:19 A no show sends a message that that core team member can't be relied upon
  • 04:23 to do their share of the project work.
  • 04:26 A great technique that I have found works well for
  • 04:28 planning the meeting is to go through the project W's.
  • 04:32 What is the project goal?
  • 04:34 Why are we doing this?
  • 04:35 Who is the customer and introduce the team members.
  • 04:38 When do we start and when do we need to finish?
  • 04:41 Where would the project activities occur and
  • 04:44 how will the project be planned and managed?
  • 04:50 Project charter approval and
  • 04:51 the kickoff meeting are the transition from initiation to planning.
  • 04:56 This forms the building blocks for the start of this next phase.

Lesson notes are only available for subscribers.

PMI, PMP, CAPM and PMBOK are registered marks of the Project Management Institute, Inc.

Gift this course