In the meantime, there may be some conflict about who does what and with what resources are these things to be done. This can be stressful for everyone and could potentially slow progress. The dedicated team approach consists of individuals who are devoted solely to the project. This can be an extremely effective method because there is no competition between the needs of the project and various areas of expertise. This makes for a unified team, focused on a quick and efficient completion of the project.

With the ease of this method, come some drawbacks. It can be costly to employ individuals on a full time basis for an assignment with a definite end.

Total concentration on the project can in some ways cause the team to feel like a separate entity from the organization, which can have two effects, 1. limit the amount of specialized know-how brought to the project and 2. once the project is complete, make it difficult for the team to integrate with the other members of the company.

3. Under what conditions would it be advisable to use strong matrix instead of a dedicated project team?

The efficient use of resources and the successful completion of the project, are the short- and long-term goals to consider when deciding which team type best suits the company's need. If the majority of the work involves individual projects, then the company may find a dedicated project team more beneficial. If there are more standard functions and few projects, then the skill of the functional leader and project manager through a strong matrix may be valuable.

What do you believe is more important for successfully completing a project -- the formal project management structure or the culture of the parent organization?

Whether clearly defined or implied, every organization has a culture, the system of principles that portray its...

It may be necessary to employ a formal project management structure, but allowing the culture to serve as the foundation of the decisions made when executing the project, will help ensure victory.
Chapter 4

What are the six elements of a typical scope statement?

A quality scope statement is essential when creating the project plan. The six elements of this statement are:

The definition of the project's objectives.

The description of the process results anticipated at each phase of the project.

Highlights of major events that will take place throughout the project.

Access to adequate system requirements.

Identification of the limits of the project as well as the activities not included.

Understanding and agreement between the project staff and customers of what is to be expected.

3. What does it mean if the priorities of a project include: Time-constrain,

Scope-accept, and Cost-enhance?

The project must meet the completion deadline. It is not desired, but if necessary, acceptable to reduce the overall scope of the project. The project manager must also take advantage of any and all opportunities to lessen costs associated with the project.

5. When would it be appropriate to create a responsibility matrix rather than a full-blown WBS?

Work Breakdown Structure (WBS) is an intricate tool that defines all aspects of the project, which includes the work itself, who will accomplish what, cost, timeframe, etc... The responsibility matrix is a less complex chart that sums up the assignments to be completed and who is supposed to complete each assignment.

WBS may be ideal for large projects, while the responsibility matrix may be more appropriate for small projects and sub-projects of large projects.