agile42 TCF Team Assessment

agile42 | The Agile Coaching Company www.agile42.com | All rights reserved. Copyright © 2007 - 2015.

Team Assessment

Part of the TCF: The Team Coaching Framework


Every team is unique! •  Each team has different strengths and challenges

•  This means each team requires a different focus.

•  The TCF allows for coaches and teams to understand the team situation more quickly.

•  It provides tools and content that allows for an accelerated learning path.

•  It is independent of any specific agile framework or approach that the Team may adopt, whether Kanban, Scrum or XP.

•  The TCF is a compilation of the collective learning of agile42 coaches for the pas decade.


TCF Overview

• Team Assessment •  Understand the status quo

•  Determine the focus

• Coaching Cards •  From observations and hypotheses

•  To goals, tools and metrics

• Coaching Tools •  Tools to influence team behaviour


TCF - Team Assessments

• Different team assessments • Agile Principles • Kanban Depth

• Team Behaviour • Technical Practices • Soft Skills


Why an assessment?

• But more importantly – why not!

• Not because we want to compare teams

• Not because we want to follow a checklist • Not because we want to check compliance


So Why Then?

• We want groups of people to become ‘teams’

• We want teams to identify opportunities

• We want teams to own their own process


12 Agile Principles Assessment

• Let’s focus on one of the assessments •  the 12 Agile Principles Assessment. •  The 12 principles are part of the Agile Manifesto.

• We ask teams to evaluate themselves based on 36 statements around these 12 principles.

• The goal is not to collect numbers, but to facilitate a discussion and create a team consensus and identify opportunities for improvement.


Group exercise • We will tell you a story about a team. • Listen carefully because we will only tell it once. • You should imagine you are part of this team, if it helps you can imagine you can identify yourself with one of the individual team members.

• Story time …..


Once upon a time … •  There was a team:

•  John: A backend specialist, is not really keen on other things.

•  Samantha: A frontend developer, who would like to learn backend programming.

•  David: A data specialist who is also an ok front end developer.

•  Ben: A frontend specialist, and prefers to stick to that.

•  Ellen: The Product Owner who’s also the VP Product Development.

•  Philip: He was quite pleased with his promotion to Scrum Master.

•  The team has gotten a Scrum training 2 months ago and just completed their 4th Sprint.

•  During Sprint planning they have no trouble selecting the stories for their Sprint because they have spent some time with the PO refining the Product Backlog.

•  A few new User Stories were identified at the last Sprint Review based on discussions with the stakeholders.

•  David was on vacation the last week of the 4th Sprint and the team had trouble finishing some stories due to data management issues.

•  The team has a good Definition of Done which is understood well by the whole Scrum team.

•  In the last retrospective some areas of improvement were identified, but not everyone is convinced it was worth spending 1.5hrs in this meeting.


"Rather than us explaining this …. …. we would like you to experience this yourself!


Agile Principle

At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly

• Statement: • The Scrum Team is aware that true continuous improvement is starting

from openly sharing experience and accepting mistakes as an opportunity to learn

• Statement: • The Scrum Team is using metrics to help them measure their

performance and identify areas of improvement


Agile Principle

Build projects around motivated individuals. Give them the environment and support their need, and trust them to get the job done.

• Statement: • Team members know what the other members can do, and they respect

their contribution

• Statement: • The Scrum Team has a clear Vision and they share that Vision on a daily

basis


Let’s hear from the groups • What are some insights?

• Are there differences between groups?


Now what? What to do with the outcome?


Accelerators Breaks

Goals & TryKeep

Active Learning Cycle provides

guidance on what to change and what to

expect from the changes…

TDD on hard

story Delay with designers

Next: TDD on one story

Working Agreements!1.  We want to pair when stories

are bigger than 2 points, so that we reduce risk

2.  We want to work with ATDD on all stories, so that

we will have a cleaner design

3.  ...

Definition of Done!✓  Integrated in the staging

system✓  all acceptance criteria are

fulfilled✓  no regression

✓  PO has seen the story✓  Performance ok

Definition of Ready!✓  User Story format

✓  Max 5pt.✓  INVEST

✓  At least 2 Acceptance Criteria

All Stories worked with TDD

No extra effort for

infrastructure

Doing TDD on everything

1 size > estimated

90% coverage of the code


Goal

Leading Indicators

Lagging Indicators

Coaching Tools

Goal 1

Leading Indicators

Lagging Indicators

Coaching Tools

Goal 2

Leading Indicators

Lagging Indicators

Coaching Tools

Goal 3

Leading Indicators

Lagging Indicators

Coaching Tools

Goal 4

Leading Indicators

Lagging Indicators

Coaching ToolsCoaching Card

Coaching Structure

Build a Coaching Structure


Online resources for Coaching Cards and Tools

• Try it yourself, sign up at: • http://tcf.agile42.com

Leadership & Management

agile42 TCF Team Assessment