Beruflich Dokumente
Kultur Dokumente
and
Embedded Systems
A Guide to the Project Management Body of
Knowledge
(aka PMBOK)
PMI Certification
Certified Associate in Project Management
(CAPM)
Project Management Professional (PMP)
Program Management Professional (PgMP)
Christopher Brooks: Project Management 2/7/12 3
Why does Project Management Matter?
Credit: xkcd.com
Christopher Brooks: Project Management 2/7/12 4
What is a project?
Q: What is a project?
A: A temporary endeavor undertaken to create a
unique product, service or result -source PMBoK, p368
Quality
Cost Time
Christopher Brooks: Project Management 2/7/12 6
Time, Cost, Scope and Quality in the
definition of a Project
Q: What is a project?
A: A temporary endeavor undertaken to create a unique product, service or result
Planning and
Initiating
Design
Project
Charte
Project Plan Change
r
(Schedule) Control
Management
Monitoring and
Executing Closing
Controlling
Lessons
Learned
Document
2.
2. Plan
Plan your
your Project:
Project: Follow
Follow Project
Project Charter
Charter Instructions
Instructions [5]
[5] to
to create
create aa
project
project charter.
charter. Ensure
Ensure that
that you
you are
are reasonable
reasonable inin your
your objectives
objectives andand
deliverables,
deliverables, especially
especially considering
considering the
the experience
experience of of your
your group.
group. i.e.
i.e. Do
Do not
not
make
make aa circuit
circuit board
board aa major
major deliverable
deliverable if
if no
no group
group member
member hashas any
any circuit
circuit
design
design experience.
experience. OnOn the
the same
same token,
token, the
the scope
scope of
of the
the project
project should
should
match
match the
the size
size of
of the
the group
group and
and the
the goal
goal be
be to
to produce
produce anan interesting
interesting andand
impressive
impressive product.
product.
Your
Your charter
charter should
should include:
include:
(a)
(a) Overview
Overview
(b)
(b) Approach
Approach
(c)
(c) Objectives
Objectives
(d)
(d) Major
Major Deliverables
Deliverables
(e)
(e) Constraints
Constraints
(f)
(f) Risk
Risk and
and Feasibility
Feasibility
Your
Your charter
charter should
should be
be one
one (1)
(1) page.
page. The
The point
point is
is succinctly
succinctly summarize
summarize your
your
project
project for
for aa busy
busy manager.
manager.
Each
Each group
group should
should submit
submit one
one charter.
charter.
The project charter
Will help define the project
Will help with the second part, the schedule of milestones and
responsibilities
Project Charter
One page!
Time
Level of Abstraction
Source: Wikipedia
Based on Waterfall
Validation: Are you building the right thing? (User)
Planning and
Initiating
Design
Project
Charte
Project Plan Change
r
(Schedule) Control
Management
Monitoring and
Executing Closing
Controlling
Lessons
Learned
Document
Combines
Waterfall &
Iterative
Good for
large projects
Source: B.W Boehm,
A spiral model of
software development
and enhancement,
A group of methodologies
Based on Iterative/Incremental
Break up tasks
small timeboxes (1-4 weeks)
Each iteration: Full devel cycle:
Planning, Requirements, Design, Coding, Testing
Customer Representative:
Appointed by stakeholders. Answers Questions
Adaptive, not Plan-driven
Product Backlog
Everything needed in the product
Product Owner is responsible for content
An ordered list of items.
Each item description, order, and estimate
Ordered by value, risk, priority, and necessity
Product Backlog grooming: add detail, update estimates,
change order. Usually no more than 10% of development
teams capacity
Monitoring: Total work remaining is visible.
Planning
Designing
Simplicity
Release planning
System Metaphor
Frequent Releases
Refactoring
Coding
Standards
Testing
UnitTests
Unit tests first
Bugs need Tests
Pair Programming
Acceptance Tests
Late Optimization
Based on http://www.extremeprogramming.org/rules.html
1
Wirths Law: Software is getting slower more rapidly than hardware becomes faster (1995)
Christopher Brooks: Project Management 2/7/12 39
Project Charter: Approach (again)
Update the look and feel of the website to a modern
standard
Provide access to student and faculty pages
Provide access to active projects
Provide access to summaries, downloads and key
papers of inactive projects. The old pages of
inactive projects should be archived.
Provide a simple static listing of seminars. A more
complex calendar and a search engine are deferred
due to schedule constraints.
Christopher Brooks: Project Management 2/7/12 43
Project Charter: Deliverables
Whats a deliverable?
Physical artifacts which describe your
progress and include your product
Deliverables should include:
A description (Scope)
A date (Time)
A person or persons who are responsible (Cost)
A schedule along with time estimates.
A prioritized list of features.
An example of the main page so we can review
look and feel.
An archive of the old website
The final website.
Example:
The primary risk is that the project takes too long to complete
and we miss the mid-March opportunity. Another risk is that
we complete the project too quickly and quality suffers. A
third risk is that there are only so many resources available.
By fast tracking, we can handle some of the tasks in parallel
and avoid these risks. The project is definitely feasible if we
roll out the website in stages.
Christopher Brooks: Project Management 2/7/12 47
EECS 149 Deliverables (Contd)
Milestones
Date Deliverable
3/6 5 minute project presentations due
3/13 Monday labs have completed charter, WBS & milestones on 3/12
3/20 First 5-min Project Mini-Updates,
1st Milestone Update Report due
4/5 5-min Project Mini-Updates,
New Milestone Report due
4/12 5-min Project Mini-Updates, New Milestone Report due
4/21 Demo your projects!
4/24 5-min Project Mini-Updates,
New Milestone Prediction (including goals for the final presentation)
5/3 Final project milestone reports due
5/9 Project Presentations
5/11 Project reports due at 12 noon (Pacific)
The
The diagram
diagram should
should show
show dependencies
dependencies between
between milestones
milestones
and
and which
which tasks
tasks can
can be
be performed
performed in
in parallel.
parallel.
For
For simpler
simpler projects,
projects, this
this could
could be
be very
very linear,
linear, but
but try
try to
to
divide
divide the
the tasks
tasks so
so as
as much
much as
as possible
possible can
can be
be done
done in
in parallel
parallel
so
so work
work can
can be
be split
split between
between people.
people.
Ensure
Ensure that
that the
the WBS
WBS answers
answers when
when aa milestone
milestone will
will be
be
finished
finished and
and who
who is
is responsible
responsible for
for it
it finishing.
finishing.
Work Breakdown Structure (WBS)
2.0 Alpha
1.0 Planning 3.0 Beta Release 4.0 Final Release
Resource: cxh Release Resource: team Resource: team
Cost: 10hr Resource: team Cost: ?> 1d, ~10d?? Cost: ?>2d ~ 10d??
Finish: 2/6/07 Cost: ?>5d, ~10d? Finish: 6/4/07 Finish: 7/31/07
Finish: 3/13/07
B
Metro II Work Breakdown Structure
Christopher
Christopher Brooks: Project Management
Page 1 of 2 3/6/2008
Brooks 2/7/12 55
Partial Informal WBS for the LED T-Shirt
2/7/12 56
Textual WBS for a small project
WBS Name Duration Effort Resources Cost Finish
spccdt1 Develop Project Charter 1 day 11.2 hrs PM,Cust,Fac $1,168 1/13/09
spccdt2 Project Charter 0 days 0 hrs $0 1/26/09
spccdt3 Develop User Interface Design 2 days 5.6 hrs Dev,Fac,Cust $304 1/27/09
spccdt4 User Interface Design Doc. 0 days 0 hrs $0 1/30/09
spccdt5 Develop Risk Mgmt Plan 1 day 8 hrs PM $800 1/26/09
spccdt6 Risk Management Plan 0 days 0 hrs $0 1/26/09
spccdt7 Develop Change Mgmt Plan 1 day 0 hrs $0 1/26/09
spccdt8 Change Management Plan 0 days 0 hrs $0 1/26/09
spccdt9 Develop Project Mgmt Plan 4 days 38.4 hrs PM,Fac,Cust $3,936 2/4/09
spccdt10 Project Management Plan 0 days 0 hrs $0 2/4/09
spccdt11 Develop Project Schedule 1 day 8 hrs PM $800 2/5/09
spccdt12 Project Schedule 0 days 0 hrs $0 2/5/09
spccdt13 Kickoff Meeting 1 hr 4 hrs Cust,Fac,PM,Dev $360 2/6/09
spccdt14 Develop Marketing Plan 10 days 10.22 hrs Dev,Fac,Cust,PM $789 2/20/09
spccdt15 Marketing Plan 0 days 0 hrs $0 2/4/09
spccdt16 Develop new features 16.67 days 21.33 hrs Dev,Fac,Cust $1,320 3/2/09
spccdt17 Bug fixes 25 days 28 hrs Dev,Cust,Fac $1,520 3/13/09
spccdt18 Beta Software Release 0 days 0 hrs $0 3/13/09
spccdt19 Develop Status Report 1 day 2 hrs Dev $60 3/16/09
spccdt20 Status Report 0 days 0 hrs $0 3/16/09
spccdt21 Status Meeting 1 hr 4 hrs Cust,Fac,PM,Dev $360 3/16/09
spccdt22 Develop website & poster 10 days 28 hrs Dev,Fac,Cust $1,520 3/30/09
spccdt23 Marketing Website & Poster 0 days 0 hrs $0 3/30/09
spccdt24 Bug Fixes 10 days 28 hrs Dev,Fac,Cust $1,520 4/13/09
spccdt25 Final Software & Doc Release 0 days 0 hrs $0 4/13/09
spccdt26 Lessons Learned Doc. 0 days 0 hrs $0 4/13/09
spccdt27 Closing Meeting 1 hr 4 hrs Cust,Fac,PM,Dev $360 4/13/09
Totals $14,817
Name
spccdt6
spccdt7
Risk Management Plan
Develop Change Mgmt Plan
0 days
1 day
0 hrs
0 hrs
$0 1/26/09
$0 1/26/09
spccdt8 Change Management Plan 0 days 0 hrs $0 1/26/09
Duration
spccdt9 Develop Project Mgmt Plan 4 days 38.4 hrs PM,Fac,Cust $3,936 2/4/09
spccdt10 Project Management Plan 0 days 0 hrs $0 2/4/09
spccdt11 The total number of work periods . . . required to complete a schedule
Develop Project Schedule 1 day 8 hrs PM $800 2/5/09
spccdt12 activity or work breakdown component (PMBoK)
Project Schedule 0 days 0 hrs $0 2/5/09
spccdt13 Kickoff Meeting 1 hr 4 hrs Cust,Fac,PM,Dev $360 2/6/09
spccdt14 Develop Marketing Plan 10 days 10.22 hrs Dev,Fac,Cust,PM $789 2/20/09
spccdt15 Marketing Plan
Q: How many 0hoursdays
per0 hrs A: Not more than$0
~32.5
2/4/09
Effort
spccdt16 week of effort
Develop new features pers person?
16.67 da hrs/week $1,320 3/2/09
21.33 hrs Dev,Fac,Cust
spccdt17 Bug fixes 25 days 28 hrs Dev,Cust,Fac $1,520 3/13/09
spccdt18 The number of labor units required to complete a schedule activity or
Beta Software Release 0 days 0 hrs $0 3/13/09
spccdt19 Develop Status Report 1 day 2 hrs Dev $60 3/16/09
spccdt20 work breakdown structure component (PMBoK)
Status Report 0 days 0 hrs $0 3/16/09
spccdt21 Status Meeting 1 hr 4 hrs Cust,Fac,PM,Dev $360 3/16/09
Resources
spccdt22 Develop website & poster 10 days 28 hrs Dev,Fac,Cust $1,520 3/30/09
spccdt23 Marketing Website & Poster 0 days 0 hrs $0 3/30/09
Cost
spccdt24 Bug Fixes 10 days 28 hrs Dev,Fac,Cust $1,520 4/13/09
spccdt25 Final Software & Doc Release 0 days 0 hrs $0 4/13/09
Finish
spccdt26 Lessons Learned Doc. 0 days 0 hrs
1 hrEECS149:
$0 4/13/09
spccdt27 Closing Meeting WBS and Cost are
4 hrs Cust,Fac,PM,Dev $360probably
4/13/09 not necessary
Totals $14,817
Poor Estimates
Humans are optimistic, when was the last time you
Why? finished early? One rule of thumb is to multiply an
estimate by pi.
Also, consider that each teammate has other classes.