Inscrivez-vous ou connectez-vous pour rejoindre votre communauté professionnelle.
Basically , The kickoff meeting can serve multiple administrative purposes, such as introducing the audit team, explaining the purpose and approach of the audit, establishing communication protocols, and communicating target time lines for the project. Additionally, the meeting can be used to inform and educate audit clients about the role of internal auditing and the value of a well-conducted audit. Effective Kickoff Meetings allow managers to set a positive tone in their initial meeting with clients, auditors, employees, subordinates can ensure a successful partnership during the engagement. Sometimes project managers overlook the importance of kickoff meetings to the overall project management process. Generally the first formal contact of project team has with its client, kickoff meetings help managers set the tone of a team, develop rapport with the client, and get the project off to a successful start. Some may never fully recover from a poorly conducted kickoff meeting, so this aspect of the engagement should never be taken lightly.
Thanks for invitation....I endorse answers given by colleagues, Mrs. Ghada and Mr. Mohamed farooq.
The kickoff meeting is called by the project manager and formally introduces the project team and all
stakeholders to the project. Optimally, it is best if the kickoff meeting can be held face-to-face with all
participants. Due to the distributed nature of teams in the current business environment, this is not
always possible. Therefore it is strongly recommended that use of videoconferencing or minimally
conference calls with electronic support can be viable alternatives. Kickoff meetings can also occur at
the beginning of project phases as well as at different levels in the organizational hierarchy e.g. business
kickoff meeting, technical kickoff meeting, infrastructure kickoff meeting, etc. Some of the elements
that need to be established in the kickoff meeting include, but are not limited to:
• Project Review - review the high-level details of the project including project risks, approximate schedule,
approximate budget, high level scope, project constraints or any other required element.
• Responsibility Assignment Matrix - for any issues or risks that come up in the project a responsible party
will need to be identified along with a due date for resolution.
• Participation of Key Stakeholders - it is important to determine upfront what kind of information your
stakeholders need, when they need it, how frequently, and in what format
• Escalation Path - in the event there are project issues beyond the control of the project manager or the
immediate performing organization, a clear escalation hierarchy for problems is required.
• Frequency and Need for Meetings - establish immediately the frequency of team meetings and their
necessity. Status can be handled via e-mail or posted on an intranet - it may not require valuable team
time to hold a meeting simply to report status. Also, decide the criteria for conducting a meeting.