You are on page 1of 2

PM Notes

Identify Stakeholders
Key Stakeholders
Those impacted (negatively and positively)
Key stakeholders
 Who is the sponsor?
 Why is this project happening?
 What’s the dead line. Is it a hard deadline, how did they get to that?
 How involved to they want to be? Weekly or monthly updates?
 Who is my core team?
Those Impacted
 Users of the product
o Internal or external? Both
o Both internal and external could be used to give approvals.

Determine your requirements


Requirements document
 What are you doing
 How are you to do it
o What are you not supposed to do it
 Priority order
 A lot of focus on this document
Communication
 Define who is to communicate what and to who
 Control and own the communication plan
 Clearly lay out who communicates and how
 Any adaption you do and communicate needs to be clearly authorized!!
Collaboration
 One source of truth location so everyone can access it. PMO?
 Airlog track action items issues and risk. (template)
 Project plan tracks where it is.
Kick off meeting
 Relay requirements (draft form of requirements documents)
 Finalise the document
o Get team to sign off the finalise document. Get their buy-in.
 Set expectations.
o Let people know off the overall goal and how to measure the goal.
Learn for previous projects
 Seek feedback from other team members on similar projects.
 Be adaptive
 Fast moving project = daily 15minute meeting.
o Slow moving or younger team = weekly meeting

Tools
 Only use the tools you need at the time. A mechanic doesn’t use every tool in his
toolbox on his car. Use some tools sometimes. Not all tools all the time.

You might also like