Steps: Customize FuSca


Team-Level Changes

After your team has hit the team-level Agile Performance Standards at least three sprints in a row:

  1. If you want to change a technique other than one of the standards, and you are:
    • A team member—Propose the change in a Retrospective Ceremony.
    • Not a member of the team—Propose the change in a Demonstration Ceremony if possible, or by contacting the Facilitator if not.
      Note: Team empowerment is better supported by everyone hearing your request directly.
  2. In the Retro:
    1. Determine if the change:
      1. Is big enough to require research.
      2. Could impact stakeholders, including other teams.
    2. If so, create a continuous improvement user story and manage it according to the standard process.
      Note: If it impacts release planning, create an action item for someone to refer it to the Agile Release Manager instead.
    3. Otherwise:
      1. Build consensus and make the change per the normal Retrospective steps.
      2. Set an action item for the Facilitator to include a review of the results as an agenda item for a later Retro, at least two sprints away.
  3. When the action item comes due, as a team during that Retro:
    1. Review whether the change had a negative impact on your ability to meet the Agile Performance Standards, in which case you must reinstate the prior technique (but can try a different change).
    2. If not, ask for any concerns about the results of the change.
    3. Decide whether to retain, reverse, or revise the change per the normal Retrospective steps.

Details: “Applying the Method.”

Program-Level Changes

Agile Release Manager, if a change affecting more than one team is proposed:

  1. Determine if it can wait until the next Release Retrospective, and if so:
    1. Create an action item to add it to that meeting’s agenda.
    2. Determine if it could impact other stakeholders who do not normally attend the Retro, and invite them.
      Note: If they cannot attend or send a representative, get their input to pass along.
    3. Manage the proposal per the normal Release Retrospective steps.
  2. Otherwise, either add the proposal as an agenda item for the next release planning meeting, or schedule a separate meeting.
  3. Invite other stakeholders who could be affected, if any.
  4. During the meeting, facilitate consensus on the change and create action items to implement it.
  5. Create an action item to add a review of the change as an agenda item for the next Release Retrospective.
    Note: If the group wants an earlier review, facilitate a decision on whether to use a regular planning meeting or schedule a separate one.
  6. During that meeting, perform Step 3 in the previous step set.

Details: “Applying the Method.”

Share this page