Page 244 -
P. 244

13 - PROJECT STAKEHOLDER MANAGEMENT






                   13.3.2.1 Communication Methods


                      See Section 13.3.2.1 of the PMBOK  Guide.
                                                     ®

                   13.3.2.2 Interpersonal Skills

                      See Section 13.3.2.2 of the PMBOK  Guide.
                                                     ®

                   13.3.2.3 Management Skills

                      See Section 13.3.2.3 of the PMBOK  Guide.
                                                     ®


                   13.3.2.4 Information Radiators

                      As explained in Section 10 of this Software Extension, information radiators are large, graphical displays of
                   the metrics used to report project status. They are frequently updated and located in view of the software project
                   team and other project stakeholders. Commonly used graphs include task boards, burnup and burndown graphs,
                   cumulative flow diagrams, and defect lists. Information radiators can diffuse internal politics and unhealthy
                   competition with project-relevant information. See Section 10 of this  Software Extension for examples of
                   information radiators.                                                                                 13


                   13.3.2.5 Velocity Metrics and Yesterday’s Weather


                      See Sections 10.2.2.7 and 10.2.2.8 in this Software Extension (Velocity Statistics and Yesterday’s Weather) for
                   additional tools to manage software project stakeholder engagement.



                   13.3.2.6 Communication Tools

                      As discussed in Section 10 of this Software Extension, adaptive life cycle models for software projects use a set
                   of communications tools for describing scope, schedule, progress, and risks. These tools include product backlogs,
                   release maps, cumulative flow diagrams, and product burndown graphs, and risk burndown graphs. They provide
                   outputs from managing software project stakeholder engagement.
                      Predictive software projects use techniques such as earned value reporting, CCB status reports, configuration
                   management reports, and risk registers as tools for communicating project status.



                   13.3.3 Manage Stakeholder Engagement: Outputs


                                                                                                ®
                      The outputs for managing stakeholder engagement in Section 13.3.3 of the PMBOK  Guide are applicable
                   outputs from managing software project stakeholder engagement. In addition, the output in 13.3.3.6 is an applicable
                   output from managing stakeholder engagement for software projects.





                   ©2013 Project Management Institute. Software Extension to the PMBOK  Guide Fifth Edition              237
                                                                   ®
   239   240   241   242   243   244   245   246   247   248   249