Page 184 -

9 - PROJECT HUMAN RESOURCE MANAGEMENT

Resolving conflicts among team members also needs careful balance. Most team conflicts are indicators of a
trusting environment where it is acceptable to present dissenting views. Passionate debate over technical issues
builds commitment to outcomes; conflict is only an issue when it extends beyond business and technical issues
and becomes personal.

Because of the intangible and malleable nature of software, there is rarely only one way to solve a problem,
so debate and discussion over approaches is normal and healthy as long as the discussions do not escalate
beyond what the team can solve or overflow into personal conflict. Should this occur, the approaches to conflict
management recommended in Section 9.4.2.3 of the PMBOK Guide can be used. 9
®

9.4.3 Manage Software Project Team: Outputs

The outputs for managing a project team in Section 9.4.3 of the PMBOK Guide are applicable outputs for
®
managing a software project team.

9.4.3.1 Change Requests

See Section 9.4.3.1 of the PMBOK Guide.
®

9.4.3.2 Project Management Plan Updates

®
See Section 9.4.3.2 of the PMBOK Guide.

9.4.3.3 Project Documents Updates

®
See Section 9.4.3.3 of the PMBOK Guide.

9.4.3.4 Enterprise Environmental Factors Updates

See Section 9.4.3.4 of the PMBOK Guide.
®

9.4.3.5 Organizational Process Assets Updates

See Section 9.4.3.5 of the PMBOK Guide.
®

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