Open Workbench for Tracking Scope Creep

By James McLellan

Summary

A common problem in engineering environments is tracking "small things" that either don’t make it onto the master schedule or were planned off the schedule somewhere else and not communicated to the rest of the staff, so they end up being done regardless.

 

OpenWorkbench image 1 - McLellan Analytical Systems

 

Open Workbench can be used to let your worker’s keep their own atomic level "to-do" lists and let’s the changes propagate automatically into the large roll-up schedules so that the impacts of scope creep are identified immediately by the folks who make the decisions.

 

How To Do It (that is, How To Track Scope Creep with Open Workbench)

Figure 1: You Can’t Have Documentation without a Block Diagram

OpenWorkbench image 2 - McLellan Analytical Systems

  1. Each individual has their own OpenWorkbench project which includes their assigned tasks. An example:

           Example: Bobby’s Schedule

 

WBS Number
Task
1.0.1 Make Widget
1.1.1 Write TPS Reports

 

 

  1. Each programmer is encouraged to add sub-tasks as they realize low-level derived requirements, update their hours expended, % complete, ETC, material requirements, etc.

           Example: Bobby’s Schedule

 

WBS Number
Task
1.0.1 Make Widget
  Make "W"
  Make "I"
1.1.1 Write TPS Reports

 

Figure 2: Example of Individual Schedule in OpenWorkbench

 

OpenWorkbench figure 2 image

 

 

  1. There is a button that will load the hours and spread them out according to dependency and priority information. This allows changes to the schedule to be calculated automatically.


  1. All of the engineer's individual To-Do lists can be linked together to get a picture of the whole project. How to do that is below. Someone looking from the top-level can merely review the roll-ups to track earned value.

 

 

How-To: Connect OpenWorkbench Projects

 

  1. Open a new OpenWorkbench project

 

Openworkbench figure 2 image 3

 

 

  1. Right-click on the "ID" or "Name" field. Select "insert sub-project". Insert the subproject you’re interested in. In this example, I uploaded "sample-jmass-guy".

 

  1. Items in red are milestones. Items in blue-green are completed. Items in purple are started. Items in black are scheduled, but not started.
  2. Right-click again on a blank space to add another person’s schedule.

 

Openworkbench figure 3

 

 

  1. Now, if Bobby makes a change to the smallest part of his to-do list, the trickle-down effect gets captured automatically.

 

Openworkbench figure 4

 

 

 

END

 

 

Copyright© 2006-2011 McLellan Analytical Systems LLC  |  jhmc@mclellansys.com  |  XHTML 1.1  |  CSS