What Can Go Wrong with Workgroup Workflow: Requirements & Stipulations (Part 3 of 3)

Joe Wynne is a versatile Project Manager experienced in delivering medium-scope projects in large organizations that improve workforce performance and business processes. He has a proven track record of delivering effective, technology-savvy solutions in a variety of industries and a unique combination of strengths in both process management and workforce management.

 

In this series of articles, you are finding out how to make sure your work teams are armed with full and clear knowledge of what requirements and stipulations they must meet. So far several categories have been covered:

• Lack of requirements and stipulations
• Budget not clearly defined or communicated
• Deadlines not clearly defined or communicated
• Project-specific process additions not defined or communicated

The last installment started "scope of work." But there is more to this one!

Scope of work for workgroup not clearly identified or communicated (continued)

Here are more ways to ensure workgroups understand their scope of work. Remember, success depends on your choosing a best practice compatible with project size and culture:

• Create a diagram showing adjacent teams with clear distinction on outputs from each to the others. No matter who you work with to create this diagram, you will find that the development process brings up issues that would have been painful if uncovered too late into the work effort. For example: A newer workgroup specifically tasked with overseeing regulatory compliance issues requires additions to deliverables that were not expected to be in the scope of a design team.
• For simpler situations, create your list of activities that are (and are not) in scope, then get input …

Please log in or sign up below to read the rest of the article.