Project Planning Notes Google Project Planning - Google Certificate

week 1
3 main things worked out at planning

1) sheduling - time line of the project ( time estimation technique)
2) budget - total cost break down to spending on each element
3) Risk management plan - searching for possible problem and planning ahead to
motigate the same
Project kick off meeting - once your ready to go into planning mode
First meeting where the project team comes together to ground everyone into shared
vision, gain a shared understanding of the project scope and goals and understand
each person indujival roles on the team
Team members identified in the RACI chart created on the initation phase are
invited to the project kick off meeting
project team, project stakeholders and project sponsers are invited to the project
kick off meeting.
Kick off meeting agenda
1) Introduction - 10 min , team member names, member roles, funfact

2) Background - how the project came to be, and why the project matters, set a
shared vision
3) Goals and scope - bounderies around the project , in-scope, out-scope, target
launch date, milestone
4) Roles - discuss everyone roles, everyone is clear what role they wil work on
5) Collabaration(10 min) - Shared project tools and documentation ( project plan,
work management software tool) , commucation expectaion
6) What comes next (10 min) - set expectation on what comes next- what action they
should take next
7) Q and A ( 15 min) - to gain clarity for team and see if project is benifiting
from diversity of thought
Team mates may put thier q and a on shared document and find thier confudence level
on the topics discussed
send agenda before a day or two of the meeting
ask teammate to take key points and action items and after the meeting, send a
follow up email that summarizes the keypoints of the meeting
Milestone and task - how they differ ??
Milestone - An important point on the project shedule that indicates the progress,
usually signifies the completion of the phase of the project or completion of a
deliverable ( significance check point of the project)
Task - Actvity that needs to be done into set period of time
( to achieve the milestone we must complete the set of tasks)
Importance of milestone
-->knows amount of work project requiure
-->helps breaking up the project better

-->keeps project on track
--> Helps to discover risks
--> team morale is high on knowing where they are going ahead and have little
victory
--> milestone needs to be completed ontime and on sequential order
How to Identify and set milestone
evaluate the project as a whole
make a list what team needs to do to achieeve that goal
bigger items that needs to be done are milestone ( deliveriables)
assign deadline to milestone ( give fair time)
How to account for many task that gather to milestone- WBS ( Work breakdone
structure)
Tool that sort milestone and task in a hierarchey in the order they need to be
completed
week 2
To learn :Project plan, project shedule, Time estimation method, time estimation
technique, tools and technique to build project plan
Project plan - helps document scops, task, milestone and overall actiivity of the
project
Centre of project plan is project schedule( amount of time that it takes to
complete the project)
Elements of project plan
1) Task - activity that needs to be done within a set period of time assigned to
diff team member based on roles
2)Milestone
3) People - working on team and thier roles
4)Documentation - link to relevant documentation ( RACI chart, Project charter,
Budget and risk management plan)
5) Time - estimated time that will be spent on project broken down
Elemnts of project plan in addition to project shedule

1) WBS - tool that sorts milestone and task of a project in hirearchy( also include
RACI chart and link documentation )
2) scope and goals - mentioned in prokject charter and it is mapped in pp
3) Budget - large org someone else/other depart will manage budget. maintain
constant touch with them to know the details and how you are keeping track with
4) Management plans - risk management plan, and communication plan
TIME ESTIMATION : predictingTotal time required to complete the task ( include
inactive time)
EFFORT ESTIMATION : predicting amount/ diffuties of active work req to complete

the task (active time only notes)
your teammates will have the most realistic understanding of the amount of work
required to complete the task, and will be able to provide you the best estimate
( ask your teammates before making an estimate)
Buffer - Extra time added to the end of the task or project to account for
unexpected slowdowns. (two type - task buff, project buff)
task buff - used for task that are out of project team controls ( task that are
unpredictable)
project buff - provide extra time to overall project
Planning fallacy undderestimating the amount of time to complete the task due to
optimism bias. adding task buffers to some of the project tasks to account for the
potential risks
Capacity planning - amount of work that people or resources assigned to the project
can reasonably complete in a set period of time
act of allocating people and resources to the task.
critical path - list of project milestone that should be done to complete the
project on shedule, as well as the mandatory task to complete each milestone( bare
minimum no of task that need to be done to complete the project goal )
Things to do before designing Capacity planning
1_ Identify the dependency teak
2_ time estimation for each task
3_ identify parallel/ sequential task - helps to do task that we should do early on

the project
4_ which project task has fixed start date ( ensure we have right no of people for
doing the task)
5_ IDentify the task with earlier start date ( can set the accurate expectation )
6_ Identify if the task has float/slack ( amount of time you can wait to begin a
task before it impacts the project shedule ) high priority tasks
7__ Task on critical path should have zero float
Soft skills - Asking right questin, negotiationg effectively, asking the right
question, empathy
effective open ended questions -> that cant be answerd with yes or no
negotiate effect--> PM should bridge the gap b/w high level requ and day to day
activity
empathy -> effective way to
Developing project shedule tools
Gannt chart -> visual representation of project task with task broken down and
deligated ( gannt chart used to track shedule)
spreadsheet used to create a gannt chart

Project Planning Notes Google Project Planning - Google Certificate

Uploaded by

Copyright:

Available Formats

Project Planning Notes Google Project Planning - Google Certificate

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project Planning Notes Google Project Planning - Google Certificate

Uploaded by

Copyright:

Available Formats

week 1

3 main things worked out at planning

Kick off meeting agenda

1) Introduction - 10 min , team member names, member roles, funfact

send agenda before a day or two of the meeting

Milestone and task - how they differ ??

Task - Actvity that needs to be done into set period of time

( to achieve the milestone we must complete the set of tasks)

-->knows amount of work project requiure

-->helps breaking up the project better

--> Helps to discover risks

--> milestone needs to be completed ontime and on sequential order

How to Identify and set milestone

evaluate the project as a whole

make a list what team needs to do to achieeve that goal

bigger items that needs to be done are milestone ( deliveriables)

assign deadline to milestone ( give fair time)

Elemnts of project plan in addition to project shedule

EFFORT ESTIMATION : predicting amount/ diffuties of active work req to complete

project buff - provide extra time to overall project

act of allocating people and resources to the task.

Things to do before designing Capacity planning

1_ Identify the dependency teak

2_ time estimation for each task

3_ identify parallel/ sequential task - helps to do task that we should do early on

7__ Task on critical path should have zero float

empathy -> effective way to

Developing project shedule tools

You might also like