Capturing Integration on the Work Breakdown Structure
From the pmStudent Blog
by Josh Nankivel
Ranting and raving about project management and systems engineering.
Recent Posts
The Problem with Project Management
The Problem with Project Management
The Problem with Project Management
LinkedIn Recommendations Are Easy
The Catch-22 of Project Management Certification and Experience
Categories
Agile,
Career Development,
Certification,
Change Management,
Communications Management,
Cost Management,
Documentation,
Earned Value Management,
Education,
Integration and Test,
Kanban,
Leadership,
Lean,
Lessons Learned,
Methodology,
Misc,
Multitasking,
New Project,
Operations,
Planning,
PMP,
Productivity,
Professional Development,
Project Estimation,
Project Leadership,
Quality,
Requirements Management,
Risk Management,
Schedule Management,
Scope Management,
Software,
Systems Thinking,
Tools,
Video,
Work Breakdown Structures (WBS)
Date
I recently received this question from a student and would like to share it with you. (note they are referring to Figure O in the eBook, not in the full work breakdown structure training course.)
"I realize that it is important to capture testing and integration but your example (figure o) seemed somewhat arbitrary. Since integration exists to ensure that subsystems work together, shouldn't we have integration identified under deliverable 1 and deliverable 3 as well? Also, is it acceptable to have a deliverable called "final deliverable integration" at level 2? Just so you know, I am a scheduler by background so I tend to think in terms of activities. What you stated about deliverables makes a lot of sense."
Thank you for the question Russ! I'm happy to share my thoughts:
Integration as an example of a support element happens at multiple levels (components, subsystems, systems, segments, etc.) On the project I'm currently working with now (NASA, USGS), for our software and hardware systems we have Integration & Test at the subsystem, system, segment, ground system, spacecraft, and mission levels. We also do unit testing within components of the subsystems but that activity is called out as a schedule item along with code reviews, etc. and the WBS doesn't go down to that level.
Not all branches of a project WBS require integration the way I mean it in Figure O, as in "Integration & Test". For example, a "Project Services" branch may not have any "Integration and Test" going on, because there is no software or hardware being developed that you could test. Figure O is just a simple illustration and is arbitrary, but I was probably thinking deliverable 1 was a project support branch, 2 was a software/hardware system being developed, and perhaps 3 was a stand-alone procurement or isolated deliverable (perhaps "public relationship management" or something like that).
So, those are my thoughts in response as I understood your questions. Feel free to contact me anytime with follow-ups or questions in the future.
Thanks!
Now here is my question for you. How do you represent Integration & Test activities on your Work Breakdown Structure? (Or Product Breakdown Structure)
Posted on: August 24, 2010 09:35 PM |
Permalink
Comments (0)
Please login or join to subscribe to this item
Please Login/Register to leave a comment.
|
"Words are, of course, the most powerful drug used by mankind."
- Rudyard Kipling
|