Page 64 -

4 - PROJECT INTEGRATION MANAGEMENT

Release and deployment plans are important for software projects that involve deployment of a software
product to external customer sites. Technology infrastructure plans are important for installation and sustainment
of IT infrastructure products.

The level of detail in supporting plans varies with the scope and criticality of the project and product. Supporting
plans may be incorporated into the project plan or developed as separate documents referenced within the project plan.

4.3 Direct and Manage Project Work

Software project managers who manage predictive life cycle projects tend to follow more closely the traditional
approaches to directing and managing project work included in Section 4.3 of the PMBOK Guide than do managers
®
of adaptive life cycle software projects.

A characteristic attribute of adaptive software teams is that they are self-enabled and self-directed, which
places the project manager in a more hands-off position in the day-to-day management of the project team than
the manager of a predictive life cycle project team. However, this does not mean the software project manager is
left without a role in directing and managing adaptive software projects. Activities engaged in by project managers
of adaptive life cycle software projects include, but are not limited to:

• Communicating the project scope, resources, and schedule/budget constraints to the project team and
other appropriate stakeholders;
• Providing the resources and facilities needed by the software team;

• Managing project scope, stakeholder expectation, resources, schedule, and budget;
• Creating effective mechanisms to see an ongoing overall picture of progress, status, and issues;
• Controlling changes to project scope, resources, schedule, and budget;

• Consulting with and allocating the work among multiple software development teams;
• Ensuring communication and coordination of work activities among multiple teams and coordinating the
integration of resources and components;

• Facilitating ongoing and continuous communications between the customer/user representatives and the
software developers;
• Monitoring productivity, product quality, and team performance while making adjustments as needed;
• Ensuring effective interactions with other organizational units, such as independent testing and user training;

• Facilitating demonstrations of evolving product capabilities for appropriate stakeholders;
• Facilitating delivery of early product capabilities into the user environment, as desired;

• Facilitating delivery and acceptance of the final product and closing the project;
• Coordinating dependencies with related projects, which may be elements of a common development
program or milestone dependencies with related IT infrastructure projects; and
• Managing risk.

52 ©2013 Project Management Institute. Software Extension to the PMBOK Guide Fifth Edition
®