Identify and Involve the Relevant
Stakeholders as Planned (GP 2.7)
Involving the customer as a relevant stakeholder is a strength of Agile Methods. This
practice further identifies the need to ensure that the expected level of stakeholder
involvement occurs. For example, if the project depends on customer feedback with
each increment, build, or Sprint, and customer involvement falls short of expectations,
it becomes necessary to communicate the problem to the appropriate level,
individual, or group in the organization. This group or individual will provide corrective
action, as corrective action may be beyond the scope of the project team. In
advanced Scrum implementations, this is often formalized as a MetaScrum where
stakeholders serve as a board of directors for the Product Owner.
Monitor and Control Agile Methods against the Plan
and Take Appropriate Corrective Action (GP 2.8)
This practice involves measuring actual performance against the project??™s plan
and taking corrective action. Direct day-to-day monitoring is a strong feature of
the Daily Scrum Meeting.
Pages:
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730