the$wbs:$an$agile$tool - pmi-nh.org • the$wbs$is$too$hard$to$create$and$ manage •...

46
The WBS: An Agile Tool PMI New Hampshire December 4, 2013 Presented by: Lisa Sieverts, PMP, PMIACP

Upload: leanh

Post on 14-Jul-2018

213 views

Category:

Documents


0 download

TRANSCRIPT

The  WBS:  An  Agile  ToolPMI  New  HampshireDecember  4,  2013Presented  by:

Lisa  Sieverts,  PMP,  PMI-­‐ACP

Isn’t  the  WBS  Dead?

2

Table  Discussion

• What  does  “Work  Breakdown  Structure”  mean  to  you?• Do  you  use  Work  Breakdown  Structures,  and  if  so,  how?

3

Raise  your  hand  if  ...

• A  WBS  is  the  same  as  a  GanN  Chart• I’m  Agile,  so  I  don’t  use  a  WBS• The  WBS  is  too  hard  to  create  and  manage• I’ve  never  been  able  to  figure  out  what  a  WBS  really  is,  so  I  don’t  use  this  tool.

4

Raise  your  hand  if  ...

The  WBS  is  the  foundaUon  document  for  project  management,  and  is  simply  an  organized  list  of  

the  project’s  deliverables

5

Projects

• Temporary

6

• Goal

• Constrained

What  Makes  Projects  Special?

•Projects  are  temporary,  have  a  specific  goal,  and  have  constrained  resources

•Projects  are  characterized  by  uncertainty

Waterfall  and  Agile

8

Waterfall

9

High

Medium Low

Optional

Requirements

High

Medium Low

Optional

Design

High Medium Low

Optional

Development

High

Medium Low

Optional

Testing

High

Medium Low

Optional

Deploy

Agile

10

Dem

o & Feedback

Requirements

Test

Design

Develop Test

Test Integrate

Sprints – High Priority Features Sprints – Medium Priority Features D

emo &

Feedback

Requirements

Test

Design

Develop Test

Test Integrate

Sprints – Low Priority Features

Dem

o & Feedback

Requirements

Test

Design

Develop Test

Test Integrate

Dem

o & Feedback

Requirements

Test

Design

Develop Test

Test Integrate

Sprints – Optional Priority Features

11

The Foundation Documents

100 % of Scope

Waterfall:  The  WBS

12

Roman Pichler, Agile Product Management

Agile:  The  Product  Backlog

But  all  Projectsbegin  the  same  way  ...

13

Current  SituaEon

TheNeed

The  Stakeholders

15

Project  Goal

TheOverall

MEASURABLEGoal

WHO  

is  doing  WHAT  for  

WHOM

HOWwill  we  KNOWit’s  

DONE

Out  of  Scope

What  our  project  is  not!

19

The  Devil  is  in  the  Details

Are  we  building  a  log  cabin…

21

Or  the  Taj  Mahal!

22

23

24

Scope  DefiniEon

   Scope  changes  are  cheap  and  easy  during  “envisioning”

25

Scope  DefiniEon

   Scope  changes  may  be  expensive  and  difficult  during  project  execuUon

26

IniEate Execute Monitor ClosePlan

Work  Breakdown  Structure

An  organized  list  of  project  deliverables

28

Work  Breakdown  Structure

DeliverableA  tangible  result

29

NOUN

For  Example• Hardware  or  Sodware  • Planning  Documents  • Widgets  • Process  Documents  • Test  Cases  • Training  Materials• DocumentaUon• MarkeUng  Materials

An  organized  list  of  project  deliverables

30

Work  Breakdown  Structure

The  Party  Project

31

Work  Breakdown  Structure  

Level  1

Level  2

Garage Project  Management

Landscaped  Grounds

Garage  Project

Design

33

Level  3

• Driveway• Landscaping

• Materials• FoundaUon• Walls• Roof• UUliUes

• ConstrucUon  Planning• Permits• Financing• InspecUons

Project  Management

Landscaped  Grounds

Garage

Design

Level  4  -­‐  Handout

34

InstrucEons  • Think  about  a  recent  project  you  worked  on• List  Deliverables,  not  Tasks  (Nouns,  not  verbs)• List  the  Level  2  Items• Compare  your  projects  with  your  tablemates’

ExerciseWork  Breakdown  Structure  (WBS)

36

Roman Pichler, Agile Product Management

Agile:  The  Product  Backlog

What  do  We  Mean  by  Success?

hNp://www.flickr.com/photos/jurvetson/3031088430/Available  for  download  under  a  CreaUve  Commons  license.

Business  Results

hNp://www.flickr.com/photos/31796655@N07/2974942783/sizes/m/Available  for  download  under  a  CreaUve  Commons  license.

Customer  SaEsfied

hNp://www.flickr.com/photos/adriarichards/4484844867/sizes/o/Available  for  download  under  a  CreaUve  Commons  license.

Efficient  Project

hNp://www.flickr.com/photos/chelseagirlphotos/296235886/sizes/l/Available  for  download  under  a  CreaUve  Commons  license.

Proud  Team

hNp://www.flickr.com/photos/nicmcphee/276227701/Available  for  download  under  a  CreaUve  Commons  license.

Ready  for  the  Future

hNp://www.flickr.com/photos/thowi/46455100/sizes/l/Available  for  download  under  a  CreaUve  Commons  license.

Summary

• Begin  projects  with  a  clear  purpose.• Take  a  few  minutes  to  define  deliverables.• The  more  clarity  the  team  has,  the  more  likely  it  is  that  they  will  achieve  their  goals.

Long  Live  the  WBS

44

Work Breakdown Structure

Q  and  A

Resources

• Extreme  Project  Management  by  Doug  DeCarlo• hNp://www.successful-­‐project-­‐management.com/work-­‐breakdown-­‐structure.html

• hNp://www.projectmgt.com/ArUcles/ArUcle-­‐WBS%20How.pdf

46