Page 246 -

13 - PROJECT STAKEHOLDER MANAGEMENT

For adaptive life cycle projects, it is important that the customer and other decision-making stakeholders
understand that they are responsible for feature identification, feature prioritization, and sequencing of software
development; that they control what gets worked on; and that they are to be provided with demonstrations of
progress and product functionality, which will require their involvement and feedback.

13.4.1 Control Stakeholder Engagement: Inputs

The inputs for controlling project stakeholder engagement in Section 13.4.1 of the PMBOK Guide are applicable
®
for software projects.

13.4.1.1 Project Management Plan

See Section 13.4.1.1 of the PMBOK Guide.
®

13.4.1.2 Issue Log

See Section 13.4.1.2 of the PMBOK Guide.
®

13.4.1.3 Work Performance Data
13

See Section 13.4.1.3 of the PMBOK Guide.
®

13.4.1.4 Project Documents

See Section 13.4.1.4 of the PMBOK Guide.
®

13.4.2 Control Stakeholder Engagement: Tools and Techniques

The tools and techniques for controlling stakeholder engagement in Section 13.4.2 of the PMBOK Guide are
®
applicable to controlling software project stakeholder engagement.

13.4.2.1 Information Management Systems

See Section 13.4.2.1 of the PMBOK Guide.
®

13.4.2.2 Expert Judgment

See Section 13.4.2.2 of the PMBOK Guide.
®

13.4.2.3 Meetings

See Section 13.4.2.3 of the PMBOK Guide.
®

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