Day-To-Day within a PI

SAFe® is a fractal model; everything we do at the team level, we effectively replicate at the ART level, although the frequency might be different. Figure 3.4 is one of our favorite images from SAFe® because it shows that correlation.

Figure 3.4 – ART events (© Scaled Agile, Inc.)

In this chapter, we need to explore how the PO, Scrum Master/Team Coach, and Agile Team participate in these ART events; however, a more detailed explanation of these events is contained in Part 2. Once you have read Part 2, it might be a good idea to revisit this chapter.

ART Events and the Product Owner

While the PI Event itself isn’t an everyday occurrence, there are activities throughout the PI that involve the PO.

The Product Owner and the PI Planning Event

The Team Backlog is the primary input the PO is responsible for ensuring is prepared for the PI Planning Event. During the event, the PO is critical. In addition to the Team Backlog, the PO is also responsible for ensuring that the team is staying aligned with the priorities outlined by Product Management.

The PO has content authority for the Team Backlog; as the teams are planning their work, questions will often arise, particularly for items in the later iterations, and the PO needs to be available to answer, go get an answer, or provide enough information so that the team can plan the work.

The PO and the Scrum Master/Team Coach often work very closely together at PI Planning, helping to keep the team moving forward with their plans, sequencing the stories, and crafting the PI Objectives.

The Product Owner and PO/ART Sync

The PO needs to attend the PO Sync or ART Sync. This allows the PO to help keep the team aligned with the other teams, reorganize the backlog as new information or dependencies come to light, and share progress toward goals and commitments.

Often, the PO or ART Sync is used to outline the Iteration System Demo based on the work that was completed in the last iteration.

The Product Owner and Iteration System Demos

The PO should be prepared and work with the team to ensure their work is integrated with all of the work from the other teams. The PO should be prepared to help the team show their work within the context of the ART and ensure that Product Management is aware of the work the team is completing and the feedback the team needs from Stakeholders or customers.

The PO and the team should consider what feedback they need or work they want to share each iteration. This can be a good conversation at Iteration Planning.

The Product Owner and the PI System Demo

The PO has a responsibility to make sure the team’s contributions are integrated into the PI System Demo. The PO may even be asked or work with their team to show the work they delivered in the context of the solution.

In the same fashion as the Iteration System Demo, the PO and team can identify in advance what key functionality or feedback they would like to highlight or receive, and the PO can work with Product Management to ensure it is incorporated into the demo.

The Product Owner and the Innovation and Planning Iteration

During the Innovation and Planning (IP) Iteration, the PO will likely be involved with final adjustments to the Vision and Roadmap for the next PI, which includes ART Backlog Refinement.

The IP Iteration is the last opportunity for the PO to socialize the Features so that the teams can create candidate stories in the Team Backlog for PI Planning.

The PO may also work with the team on a hack-a-thon or even attend training with the teams.

ART Events and the Scrum Master/Team Coach

While the Scrum Master/Team Coach works daily with the team, when in a scaled environment, there are additional key events and interactions the Scrum Master/Team Coach participates in.

The Scrum Master/Team Coach and the PI Planning Event

The PI Planning Event is an extremely hectic event for the Scrum Master/Team Coach. We’ve included some key activities that the Scrum Master/Team Coach usually helps with, which, while not comprehensive, will help create a successful event.

In preparation for the PI Planning Event, the Scrum Master/Team Coach should do the following:

• Calculate Team Capacity for each of the iterations for the PI based on up-to-date Team Velocity taking into account any planned holidays/vacations
• Set up team space with appropriate supplies
• Work with the PO to prepare the Team Backlog and stories
• Help RTE to ensure a successful event

This is what the Scrum Master/Team Coach should do during the PI Planning Event:

• Keep the team engaged and on track
• Participate in Coach Syncs
• Adhere to Time Boxes
• Keep Boards (Team, ART Planning, and Risks) up to date
• Manage Dependencies

This is what the Scrum Master/Team Coach should do after the PI Planning Event:

• Help clean up the space
• Make sure that plans are captured in your Agile Tool or whatever method you choose to use

It’s important that the Scrum Master/Team Coach is prepared for the event and understands how the event flows, their responsibilities, and how to help the ART be successful.

The Scrum Master/Team Coach and Iteration System Demos

The Scrum Master/Team Coach helps the team ensure they are integrating their work with the other teams on the ART at each iteration. The Scrum Master/Team Coach partners with the PO to ensure the team members attend and participate in the Iteration System Demo, that their completed work is incorporated into the Iteration System Demo, and that the team receives any feedback from the Iteration System Demos.

The Scrum Master/Team Coach and the Coach Sync/ART Sync

The Scrum Master/Team Coach meets and shares with other Scrum Masters/Team Coaches or ART members the current progress toward delivering the PI Objectives, discusses dependencies between the teams to ensure alignment, and raises and helps to resolve any impediments.

The Scrum Master/Team Coach and Inspect & Adapt (I&A)

Often, the Scrum Master/Team Coach is called upon by the RTE to help with the various I&A activities.

Like the Iteration System Demo, the Scrum Master/Team Coach will want to work with the PO to ensure the work is represented at the PI System Demo. Additionally, the Scrum Master/Team Coach may need to help coordinate schedules for dry runs of the demo, help ensure the team is prepared, and celebrate the success with the team.

The RTE may request the Scrum Master/Team Coach to pull and compile various metrics that will be presented in the Quantitative and Qualitative Metrics section. The Scrum Master/Team Coach may also facilitate the Competency Assessments for their teams.

The Scrum Master/Team Coach is often an excellent candidate to facilitate one of the groups for the Problem-Solving Workshop. A success pattern we recommend is that the RTE facilitate a workshop with the Scrum Master/Team Coach prior to the event so that the Scrum Master/Team Coach understands their role in the workshop and how to best facilitate the activity.

Pro tip

When a Scrum Master/Team Coach helps to facilitate a Problem-Solving Workshop, they often don’t get a chance to fully participate in the problems and then the solutions. As a recommendation, if you have other ARTs within your organization, consider using a Scrum Master/Team Coach from the other ARTs to help facilitate, so that the incumbent Scrum Master/Team Coach can fully participate in their ART Problem-Solving Workshop.

Innovation and Planning Iteration and the Scrum Master/Team Coach

In conjunction with the PO and the team, the Scrum Master/Team Coach will help the team with the activities they are undertaking, whether that is holding a hack-a-thon, organizing or attending training, or addressing technical debt.

Also, they will support the RTE with the final preparation for PI Planning, including ensuring that the PO and the team have a Team Backlog ready for PI Planning.

ART Events and the Agile Team

When we scale, we need to ensure that we maintain alignment. There are several activities and events that the teams are involved with during the PI. Let’s take a look at the key events.

The Agile Team and Iteration System Demos

The team will work with the other teams to ensure their work is integrated and demoed at every Iteration System Demo. The team members should also attend and participate in the Iteration System Demo for understanding and alignment with the other teams. This is a great opportunity for the team to hear directly from Stakeholders and get real-time feedback on the entire solution.

The Agile Team and the PI System Demo

In the same fashion as the Iteration System Demos, the teams will need to integrate and demo their work that was completed over the course of the PI. Participation at this event is necessary and continues to build alignment and trust across the ART.

The Innovation and Planning Iteration and the Agile Team

During the Innovation and Planning (IP) iteration, the Agile Team often engages in various activities that are not directly related to delivery but are focused on improving the team’s productivity and effectiveness. Some typical activities include the following:

• Conduct research on emerging technologies to inform future decisions
• Review and refine the team’s processes. Review and adjust the DoD, DoR, Working Agreements, and so on
• Engage in team-building activities to improve collaboration and communication among team members
• Develop and improve skills and knowledge through training and education
• Collaborate with other teams and Stakeholders during PI Planning
• Hold a hack-a-thon to create prototypes or proofs of concept to validate assumptions or explore new ideas
• Address technical debt or other areas of improvement that may have been previously identified

The team will want to work closely with the Scrum Master/Team Coach and PO to identify and determine the activities they are undertaking during the IP Iteration.