DiscoverVirtual Team Dynamics - The Ulfire PodcastMethod and Scope Complexity in Virtual Team Projects
Method and Scope Complexity in Virtual Team Projects

Method and Scope Complexity in Virtual Team Projects

Update: 2017-09-26
Share

Description

In this installment of the short series looking at the different complexity influences on and from project virtual teams. Here I am considering method and scope complexity and uncertainty, how these factors impact complex projects and how project virtual teams both contribute to the overall complexity and compound the challenges.

Method and scope uncertainty complexity occurs around issues such as the maturity of the scope of the project, the proportion of new or highly novel technology to both the project and the team, the quality and maturity of the estimate and the accuracy and reliability of the assumptions that went into the formation of the estimate.



* Scope maturity – theoretically every project will have a clear scope before sanction, it should have gone through a series of developmental phases prior to full sanction where the owners systematically work to define the required scope, including costs, materials, time frame and how overall success is defined. However, reality is somewhat different. Some projects will be initiated with little to no definition, either to meet a critical need, plug a gap, address a crisis or simply because the owners were so excited to get started they jumped straight in without really taking the time to plan. Even in most of these situations there should be some level of definition around the scope, though budget and time frame are likely less well framed. However well defined the scope may be, conveying the definition across any project team beyond whatever may be written can be challenging, personnel will interpret definitions based on their previous experiences and through their own lenses, leading to confusion and misunderstanding. This confusion becomes substantially compounded in a project virtual team environment, where not only are personnel contending with interpreting the scope definition, they are frequently doing so remotely without access to anyone who was part of the development of the scope to help with any required clarification. It is important to ensure all members of the team, regardless of location, have a full and clear understanding of the required scope as it impacts their tasks.

* Proportion of new technology – Many years ago now a manager of mine advised me to avoid having more than one new major piece of technology on a project. It has been advice that has stuck with me for many years and one which I have seen cause several projects to encounter problems. Several small and unobtrusive new pieces of technology are fine but if more than a certain percentage of the effort on a project is associated with a single new piece of technology it is very easy for projects to slide from simply complicated to complex. Trying to integrate a number of pieces of new technology into a major project while using a virtual team to undertake much of the integration work, and here I mean that the integration is split between a number of locations rather than all of it in one office, can lead to major issues as team members separated by time and distance battle both their displacement and the challenges of the new technology. Examples of this can be seen in things like the problems faced by organisations like Airbus in the development of new aircraft across multiple European centers.When planning for your project identify the major new technology and even the less major but high risk new technology and ensure it forms a manageable portion of the overall project.

* Maturity of estimate – There has been a lot written on the need to have a mature and well developed estimate before committing to the full execution of a project. Some of the best work has been by Ed Merrow of IPA in his book “Industrial Megaprojects” where he discusses what is known as the Front End Loading (FEL) approach to the development of projects, where substantial efforts are expended in a very structured manner to de...
Comments 
In Channel
00:00
00:00
x

0.5x

0.8x

1.0x

1.25x

1.5x

2.0x

3.0x

Sleep Timer

Off

End of Episode

5 Minutes

10 Minutes

15 Minutes

30 Minutes

45 Minutes

60 Minutes

120 Minutes

Method and Scope Complexity in Virtual Team Projects

Method and Scope Complexity in Virtual Team Projects

Virtual Team Dynamics - The Ulfire Podcast