Stand up Process

Standing Up Agile Teams - Guide

Stand Up Process

1. Define Stable teams

· Agile teams should be defined for the entire Capability which should include a Scrum Master, Product Owner, and Technical/Solution Lead

· These teams should be set up not just to cover the current initiatives in flight but to prepare for any work that would be part of the Capability (if applicable) they support with direction from the Capability Strategy Team (CST)

· Names of people should be determined for each role and for each team

· Explain to team members their role and expectations for each role (Responsibilities of Team Member cheat sheet as a guide)

2. Determine location for team – goal is to have teams collocated, if possible.
Items to consider:

· Size of team area

· Collaborative working space

· Space for any information radiators

· Work with facilities to coordinate any moves

3. Define Capability Strategy Teams (if applicable)

· CSTs should be a combination of Business, Technology, Program Management, Resource Managers and other SMEs

· CSTs should set a regular planning, working and reviewing cadence (2-3 week sprints recommended)

· CSTs should work together to create an enterprise vision for their Capability and a roadmap that provides guidance toward the delivery of the vision

· CSTs should create a defined process for how work flows to the CSTs, is prioritized in a visualized backlog and then flows to teams.

· CSTs are also an escalation path for teams as they may need issues to be resolved or impediments to be removed.

· CSTs should review the AgilityHealth rollup results from teams within their Capability and work on Organizational growth items that roll up from those teams.

4. Training needs. Work with leaders within teams to determine training workshop needs and participants.

· Possible Training Options:

· Real World Agile for Teams (3 Days) (For teams new to Agile)

o Analysis, Dev, and Test resources for each team

o Scrum Masters, Product Owners, and Solutions/Technical Leads for each team

o UX Analyst assigned to support teams if applicable

· Advanced Agile for Mature Teams (1 Day) (For teams with Agile experience)

o Analysis, Dev, and Test resources for each team

o Scrum Masters, Product Owners, and Solutions/Technical Leads for each BAU team

o UX Analyst Assigned to support teams if applicable

· Leading Agile Teams (2 Days)

o Scrum Masters, Product Owners, Product Managers, Functional Managers, and Program Manager

· Deep Dive into Agile Requirements (1 Day)

o Product Owners, Analysis resources, Business SMEs and any others involved in requirements processes

· Agile Overview for Leaders (1 Day)

o Resource Managers, Program Managers, Directors and other leaders that need to understand the Agile lifecycle and how to support teams

5. Confirm the proper communication has gone out to all people within Capability prior to trainings being scheduled.

· Business Owner: Send communication to all participants that they are part of the next stand-up and will be set up for Agile training

· Product Owner: Send communication to impacted business units about the change especially if there are any SMEs that will be included in the trainings

· Resource Managers: Communicate to all employees that they are part of an Agile team and their role on the Agile team

6. Plan Team Formation day (should be half to full day)

· Establish Team Charter to include:

o Team Vision and Igniting Purpose

o Roles & Responsibilities chart

o Customers/Stakeholders identified and Communication Plan established

o Resource and/or skill gaps identified

o Team Norms / Working Agreements

o Start, Stop exercise and build team improvement roadmap

· Set up team working space

o Physical Board, if desired

o Set up collaboration area

7. Coaching for Triangle leads to set expectations and help them feel comfortable in their role

· Clarify role responsibilities

· Help set the tone for the team

· Servant Leadership

· Facilitation skills and techniques

· Effective Agile meetings

8. Communicate to team the role of the Agile Coach and how they will work together, as needed.

9. Take baseline Agility Health Retrospective Assessment (see image below). Best after 1-2 sprints of working together.

Sample 12 Week Team Plan – Standing Up a New Agile Team
Use the plan below as an initial guide for how to standup an Agile Team, feel free to change it to fit your own needs. Remember, the team pre-launch checklist should have been completed prior to this.
Mon / Tue / / Wed / Thu / Fri
W1 /
W2 /
W3 / /
W4 /
W5 / /
W6 / /
W7 /
W8 / / /
W9 /
W10 / /
W11 /
W12 /