Chapter-2 Project Organization Structure
Chapter-2 Project Organization Structure
Chapter-2 Project Organization Structure
Contents
•Defining scope
•Quality
•Activity sequence
•Work Breakdown Structure (WBS)
•Organization Breakdown Structure (OBS)
Defining Project Scope
• Scope refers to all the work involved in creating the products of the project and
the processes used to create them.
• It is what needs to be achieved and the work that must be done to deliver
a project.
• It determines and documents a list of specific elements in a project scope statement :
project goals,
deliverables (is a product produced as part of a project, such as products, planning
documents,…)
features,
functions,
tasks,
deadlines,
costs
project teams roles and responsibilities
list of stakeholders who will be affected.
Project Scope Management
It ensures that the project team and stakeholders have the same
understanding of what products the project will produce and what
processes the project team will use to produce them.
Collection of Project Requirements
Requirements include:
• Conditions or capabilities to be met by the final
product
• Details on product, functionality, features, attributes,
validation
• Need to be obtained, analysed, prioritised and
approved by stakeholders
Sources of Project Requirements
Stakeholders
• are people who are invested in the project and who will be affected by your
project at any point along the way, and their input can directly impact the
outcome.
•They are typically:
the members of a project team,
project managers,
executives,
project sponsors,
customers, and users.
Project Quality
Project Quality includes the processes and activities that
determine quality policies, objectives and responsibilities so
that the project will satisfy the needs for which it was
undertaken (to meet stakeholders needs and expectations)
Activity Sequence
• the key benefit of this process is that it defines the logical sequence of
work to obtain the greatest efficiency given all project constraints.
WBS
• WBS breaks down the project deliverables into
manageable portions of work packages that you allocate a
unique ID to.
• This is commonly shown in a graphical form, such as an
organizational style chart or a fishbone diagram.
• The project manager defines the key objectives first and
then identifies the tasks required to reach those goals.
Example
Deliverables
•
Overall status of FTVET industry linkage
• Using a WBS, a large project is broken down into smaller subprojects which
may, in turn, be further subdivided into another, lower level of more
detailed sub component activities, and so on.
• Eventually, all the tasks for every activity are identified, commonalities are
discovered, and unnecessary duplication can be eliminated.
Project Organization
• The way you run projects is influenced by the way your
organization is structured
• Like any organization, projects can be managed and
controlled by using different type of organizational
structure.
• Before selecting an organizational structure, the project
team should assess the nature of the job to be performed
and its requirements.
• Formal and informal structures: The formal
organization structure represents the officially
sanctioned structure of a functional area.
– product requirements or
– both
• It is linked to the rest of the system through process reports, organizational policies,
procedures, and funding.
• In pure product organization:
technology utilization and resource sharing are
limited because there is no single group responsible
for overall project planning.
organizational structures
End