![]() The key outcome here is to set expectations regarding methods, processes and handoffs, roles and responsibilities. Again, if we’re are going to have any surprises, we want to know them now instead of partway through the project. During the kickoff meeting, we read aloud all the assumptions listed in the statement of work and discuss in detail, if necessary. In our experience, there are even more project members who have not read the assumptions. By carefully reviewing the project scope during the kickoff meeting, we can set (or reset) expectations now rather than when we’ve completed a good share of the work. Here is where we often discover that there are a few team members who have not read the statement of work on their own. Reviewing a high-level milestone schedule helps everyone begin to see clear interim and long-term project goals. Reviewing a clear list of deliverables makes it much easier for the team to understand their roles and responsibilities and envision when the deliverables are due based on the milestone schedule that we present next. This is a great way to uncover-early in the project-stakeholder expectations, interests, concerns, and areas for quick wins. ![]() This is our opportunity to learn from the client about the stakeholders who will be affected by the project’s objectives. At this point, we discuss and reinforce those goals and address the details related to how we’re going to get it done. ![]() What is the project about? Why is this project important to the company or organization? How is the team going to get it done successfully? Ideally, the project sponsor has addressed the first two questions in the Welcome. There are three important questions we must answer for the team. This gives the team a clear idea on project goals and what the team is expected to produce and when. After introductions, we dive right into reviewing the project statement of work. Our goal is to involve everyone in discovering and buying into what they need to do to make the project a success.Ī key rule here is to never assume the team has read the statement of work. Projects run way better when the people actually doing the work have a shared vision and wrestle with the details together. Project Goals & Scope Discussion (Walk Through The Statement Of Work) Our goal is to set the stage for open, honest dialogue, not a lecture. We find that, if prepped in advance, the most influential welcome comes from the project sponsor, who is in the best position to share his or her vision for the project and emphasize how the project aligns with company goals.Īfter a brief welcome, we have the team share introductions-in an interactive and engaging way. Here's a breakdown: Welcome & Introductions Step 2: Run The Kickoff Meeting Using This Kick-A** Kick-Off Meeting Agenda During this meeting, we run through the kickoff agenda to ensure everyone on our team understands the project scope and his or her role before showing up for the client kickoff meeting. Immediately after meeting with the client, we send the agenda to all attendees, so they know what to expect and can plan accordingly.Įqually important as the client pre-kickoff meeting is our internal team pre-kickoff meeting. Uncover any potential roadblocks or circumstances that might interfere with achieving the kickoff meeting goals and discuss mitigation techniques.Align on specific kickoff meeting goals. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |