Innovate - Develop the work breakdown structure
In every project the devil is in the details, and fleshing out the details can be challenging, particularly when you are looking to transform how you render your services. It can be problematic as you start to communicate this across your organizations, because traditional IT staffers may not initially (or ever) see the need for change. Fortunately, the work breakdown structure (WBS) provides a mechanism to break a project into more digestible chunks. I watched a project manager struggle to gain updates from her supporting team of operations engineers, as they knew what needed to be done and perceived no value in documenting the steps for someone else’s benefits. But when the WBS was drafted with their names attached to deliverables, they instantly had a more accessible view of the larger project. They could, at a glance, determine what their responsibilities where and who to go to if they had questions in a particular area, which helped remove ambiguity. More responsibility and less ambiguity lead directly to less surprises and a more cohesive project team. Change normally comes through pain or gain, but introducing a couple of new tools to make everyone’s life easier can help enable the transformation you seek!
|
|
|
