3. Introduction
Small budget
for project
support
Milestones 4 new projects
due Year1
NRA Work at 4
solicitations Centers
New work Integrated 3-4
agreements levels below
project
3
4. Outline
Introduction
In the Beginning
Ghost of Projects Past
Love Your Planning Data
Lessons Learned
4
5. Common Project Scenarios
Another call for project data
Why don’t your numbers
match?
Who’s really responsible for the
work?
5
6. How can we do this better?
Better Planning
… but isn’t this a lot of work?
6
7. Pay now or pay later …
Who’s got that data?
Using outdated information
Errors in translating project
data to another format
Great results, wrong
deliverable
7
8. Outline
Introduction
In the Beginning
Love Your Planning Data
Overview
Key Planning Steps
Tool Examples
Lessons Learned
8
9. Today’s discussion focuses on:
Requirements Schedule
Facility
Usage
Work Scope
Tasks
Descriptions
Project
Work Scope
(WBS)
Resources Milestones
Contracts &
Agreements
N2 Budget Risk
9
10. Key planning steps
1. Is the entire project there?
Include technical scope, resources, milestones and
work descriptions for each WBS element
2. Plan low
Identify work done at the lowest work group
Assign resources in “categories”
Use identifier fields to add more definition
3. Automate analysis
Consolidate all planning detail
Use automation to summarize and cross-check
10
21. Put your data in the center
Authorization
Documents
Tasks for Project
Schedule Plan
Project
Planning
Data
Milestone Phasing
Tracking Plan
Reports Support
Performing
Org
Reports
21
22. Staying ahead of the data
Data systems keep Data systems can
the connections require support
between planning and tool-specific
elements processes
Allow information to No tool replaces
be utilized in good people
multiple ways Accurate data
Provides single requires project
repository for data support
What
What
makes
makes
sense
sense
22
24. Lessons Learned – Process
Communication is critical when
formats or processes change
Be sure to include rational explanations
and “big picture”
Remember to include EVERYONE who
uses project data, especially those
“outside” the project
Change takes time. Consider
incremental changes or a phased
approach.
24
25. Questions
Thank you very much
Maura.Fujieh@NASA.gov 25