|
Project
Managment Basic
|
|
Tool Name |
Description |
Timing |
Benefits |
|
A description of project purpose
including identification sponsorship, business needs, scope, objectives,
assumptions, and deliverables. |
Start of project |
Needed to ensure agreement &
common understanding of project scope and purpose. |
|
|
A description of the process
that the project will follow including phases, major deliverables, test and Q/A
steps, and review points. |
Start of Project |
Organizes the project as a
sequence of phases, establishes a logical flow of results from requirements
to implementation, integrates testing & review into the project plan |
|
|
A report of project progress
that typically includes · accomplishments and issues, · actual progress as compared to schedule, · actual costs as compared to budget, and · any revisions to either budget or
schedule. |
Periodically |
Informs project stakeholders of
the state of the project. |
|
|
A hierarchical structure of work
that needs to be done to produce project deliverables including phases,
milestones, tasks, and dependencies among tasks. |
Project planning with periodic
updates |
Identifies, itemizes, and
organizes the work that must be performed to produce project deliverables. |
|
Tool Name |
Description |
Timing |
Benefits |
|
An assessment of resources
needed to complete the project including people, skills, hardware, software,
and network resources. |
Project planning with periodic
updates |
Identifies and itemizes the
resources that are needed to produce project deliverables. |
|
|
Determine who is available to
work on the project and the skill pool available from these staff. |
Project Planning |
|
|
|
Identification of project
stakeholders, communication needs, and communication methods including web
pages, mailing lists, meetings and minutes, etc. |
Project planning |
Helps to ensure that everyone
with an interest in the project is informed of project activities and events. |
|
|
Determine elements of campus
computing infrastructure that the project must integrate with, and make plans
to do so. |
Project planning with periodic
updates |
Ensures appropriate use of
infrastructure services, and availability of required infrastructure
capabilities. |
|
|
Time-based allocation of project
activities and results, describing when work is planned to be done and when
results are expected to be delivered. |
Project planning with periodic
updates |
Essential to track, monitor, and
manage project tasks and deliverables. |
|
|
A final review and report of
project experiences including · What was done well and how to make it
repeatable. · What mistakes were made and how to prevent
them in future projects. |
End of project |
Formalizes learning from project
experience and adds value to future projects. |
|
Meeting Type |
Description |
Timing |
|
A meeting with the client
(external to C&C) for the project to discuss what they would like to
accomplish, timing, etc. |
Start of project |
|
|
Meet with the project team to
discuss the reason for the project; review the Project Charter; discuss
roles; etc. |
During planning stages of
project |
|
|
Meet with the project client
(external to C&C) (s) to review the plans for the project. |
During planning stages of
project |
|
|
Periodic meetings with the
project client (external to C&C) (s) to review the progress on the
project. |
Periodically |
|
|
Meetings with the project team
members to review work progress and status; technical issues relating to the
project work; problems; etc. |
Periodically |
|
|
A meeting with the client
(external to C&C) for the project to end the formal project work. |
End of project |
|
|
A meeting with the project team
to discuss the project; identify areas of change or improvement for the next
project; discuss the on-going work requirements or plans for future work on
the project. |
End of project |
|
|
Social get-together for the
project team to acknowledge a job well-done |
End of project |
| < back |
help
|
exit
|
copyright © 2001 Chee Data Tie