CFICSE

1
CFICSE

• Project Organizations and Responsibilities
• PM-09

2
Outline

• Line-of-Business versus Project Organizations
• Line-of-Business Organizational Structure
  (default)
• Project Organizational Structure (default)
• Software Management Team
• Software Architecture Team
• Software Development Team
• Software Assessment Team
• The Evolving Software Project Organization

3
Line-of-Business versus Project Organizations

• most studies of software engineering focus solely
  on the project organizational structures
• recognizing software functions within traditional
  line-of business hierarchies, emphasizes the
  important role that corporate policy and strategy
  has with respect to the success of software
  projects
• there is a requirement for staff / corporate
  bodies outside the selfish project office
• a project offices timeframe is too short
• an issue of infrastructure instead of environment

4
Line-of-Business Organizational Structure
(default)
...
Project N
Project B
Project A
5
Project Organizational Structure (default)
6
Software Management Team

• Responsibilities
• resource commitments
• staffing
• planning, prioritization
• stakeholder expectations satisfaction
• risk management
• project control

• Artifacts
• business case
• vision
• software development plan
• work breakdown structure
• status assessments
• requirements set

responsible for attaining a balance among all
aspects of quality such that the system is right
for all stakeholders
7
Software Architecture Team

• Responsibilities
• requirements trade-offs
• design trade-offs
• component selection
• develop versus buy decisions
• initial integration
• technical risk resolution

• Artifacts
• architecture description
• requirements set
• design set
• release specifications

responsible for system level quality including
reliability, performance and maintainability
8
Software Development Team

• Responsibilities
• component design
• component implementation
• component test
• component maintenance
• component documentation

• Artifacts
• design set
• implementation set
• deployment set

responsible for the quality of individual
components including all development testing and
maintenance
9
Software Assessment Team

• Responsibilities
• project infrastructure
• independent testing
• verification and validation
• metrics analysis
• configuration control
• change management
• user deployment

• Artifacts
• deployment set
• SCO database
• user manual
• environment
• release specifications
• release descriptions

responsible for the quality of the baseline
releases with respect to requirements (vision)
and customer expectations
10
The Software Organizationversus Phase
Inception Phase
11
The Software Organizationversus Phase
Elaboration Phase
12
The Software Organizationversus Phase
Construction Phase
13
The Software Organizationversus Phase
Transition Phase
14
References

• Royce, Walker. Software Project Management,
  Addison-Wesley, 1998. Chapter 11.