I am a very newbie to PMing and tomorrow I will have my first kickoff meeting, I am so glad I found you. I wrote some notes down that will help me with this meeting tomorrow. Thank you!
Rule no. 1: you are not 'kicking-off' anything, unless you want to see the project as a contest between teams. No. Your job is to bring a cooperative team together to jointly understand a project and set the scene for activating that joint understanding.
at the onset of each project we always run a scoping meeting for 1.5 to 2 hours with each of our customers that includes your suggestions and addresses alignment. We're currently revamping and making a concerted effort to provide each customer with a standardized project experience. we have many repeat customers and we've used their feedback to create this standardized way based upon what most of them have liked and what they found valuable. We've also tried to separate the teaching and training around project management to our customers and actually delivering the project with a team. As PMs we are the process experts, and understand that our customers are the content experts. We're trying to use this for the customers advantage by making our standardized process much more efficient, quick and valuable. There are still teaching moments in our projects, but we've tried to keep processed jargon acronyms and other things at a minimum, sort of like pay no attention to the man behind the curtain. However as you described with the kickoff meaning, what we call a scoping meeting we stay very technical at that point to define the boundaries seek out the scope and set the goals
Thanks for sharing! You make so many great points here. Having standard practices for this type of meeting is perfect, and getting feedback to improve the process is very smart!
The only alignment exercise is to discuss scope, performance expectations, the client/sponsor's objectives and the basic contextualizing 'why' for the project. Then, how the project will create unique value/capability for the owner.
Being a professional, I don't hold 'kick-off' meetings, like a project is some moronic soccer game. I have commencement/start-up/initial/inaugural meetings. I know, big words frighten people, but it ain't a kick-off as though one side wins and the other looses, and you are expected to score goals to the disadvantage of the others.
I am a very newbie to PMing and tomorrow I will have my first kickoff meeting, I am so glad I found you. I wrote some notes down that will help me with this meeting tomorrow. Thank you!
So glad this was helpful for you!
Rule no. 1: you are not 'kicking-off' anything, unless you want to see the project as a contest between teams. No. Your job is to bring a cooperative team together to jointly understand a project and set the scene for activating that joint understanding.
As someone who wins bread as a PM hustler, this summarised presentation is top notch. Thank you
Thank you for the positive feedback!
at the onset of each project we always run a scoping meeting for 1.5 to 2 hours with each of our customers that includes your suggestions and addresses alignment. We're currently revamping and making a concerted effort to provide each customer with a standardized project experience. we have many repeat customers and we've used their feedback to create this standardized way based upon what most of them have liked and what they found valuable. We've also tried to separate the teaching and training around project management to our customers and actually delivering the project with a team. As PMs we are the process experts, and understand that our customers are the content experts. We're trying to use this for the customers advantage by making our standardized process much more efficient, quick and valuable. There are still teaching moments in our projects, but we've tried to keep processed jargon acronyms and other things at a minimum, sort of like pay no attention to the man behind the curtain. However as you described with the kickoff meaning, what we call a scoping meeting we stay very technical at that point to define the boundaries seek out the scope and set the goals
Thanks for sharing! You make so many great points here. Having standard practices for this type of meeting is perfect, and getting feedback to improve the process is very smart!
Excellent! Onset/outset: best description of a commencement meeting.
i want that video you mentioned at the end hahah !!!!! you are great!!!!
Organizing Sprint Planning Meeting and Sprint Kickoff meeting? When should I be scheduling these during Sprint process?
A Sprint Planning Meeting should be held at the beginning of each sprint or iteration.
@@teamgantt and Kickoff comes "immediately" after the Sprint Planning meeting?
@@rugbyrick Correct! Once you have planned out the upcoming sprint, you can have your Project Kickoff meeting with the entire team.
I love the way you explain
This is very well done! Thank you
Thank you, this was very insightful
Glad we could help!
One of the best projects kickoff video
This is super useful, thanks!
Great comments. Thank you much
Would love a video about the games and alignment exercises you mentioned!
The only alignment exercise is to discuss scope, performance expectations, the client/sponsor's objectives and the basic contextualizing 'why' for the project. Then, how the project will create unique value/capability for the owner.
Very Helpful Sr. thank You
great video, do you have a video on risk register
What is the difference between SPC (Statistical Process Control) and the Gantt?
Well done!
Very informative video
We need copy of templates
thank you for this episode! laconic and exciting!
👍
Being a professional, I don't hold 'kick-off' meetings, like a project is some moronic soccer game. I have commencement/start-up/initial/inaugural meetings. I know, big words frighten people, but it ain't a kick-off as though one side wins and the other looses, and you are expected to score goals to the disadvantage of the others.
grow up, you are barking up the wrong tree. Even PMI recognises kick of meetings