slides from Kyiv PM Day 2017 - Team Health Check approaches by Artem Bykovets

1. HealthСheck – тримаємо
руку на пульсі своєї
команди
ARTEM BYKOVETS
(AGILE COACH & CONSULTANT)

2. Few words about myself
• Agile Coach at Levi9 and Agile Consultant.
• CEO and coach/mentor at "StartIT”
• CSM, CSPO, CSP, CAL-1 by Scrum Alliance
• Certified Kanban System Design (KMP I) by LKU.
• Best QA specialist of Ukraine by IT Awards 2015
• Judge and Expert at UA Web Challenge.
• “Software quality and testing” lecturer at KPI
• Happy father of Sophiia J

3. What is healthcheck?

4. What is healthcheck?
TEAMS
EVALUATING
THEMSELFS

5. Who is doing it regularly?

6. For what?
Healthy teams build
better products
Great organizations
care about healthy
teams

7. How to do it?

8. Different approaches
Clarity of Shared Direction Response
1. We have a shared understanding of what this team is for 4
2. We have a shared understanding of what we are trying to achieve 3
3. Everyone knows why it’s worth getting there 2
4. We agree on how we behave with each other 1
5. We model the behaviours we want to encourage in others 0
Focus on Results and Outcomes Response
7. Where we are headed stimulates us and keeps us focused 4
8. We pay attention to what really matters to the business/organisation 3
9. We divide our time well between discussions about the past, present and future 2
Courageous Challenge Response
14. We say what’s really on our minds 4
15. We discuss the most important and difficult issues openly 3
16. We give each other frank feedback including the team leader 2
Joint Accountability Response
21. Everyone clarifies and commits to areas of accountability 4

9. What we want to achieve?

10. We have started with Spotify model

11. We have started with Spotify model
Green doesn’t necessarily mean
things are perfect. It just means
the squad is happy with this, and
see no major need for
improvement right now.
Red means this really sucks and
needs to be improved.
Yellow means there are some
important problems that need
addressing, but it’s not a disaster.

12. What to decide:
• How often we should do it?
• On which levels of organization?
• Evaluation options (2? Is it enough?)
• Focus Areas & Examples (refine)
• Balance standardization with what works
for the teams
• Measuring efficacy

13. Important!!!
It is NOT an indicator
of performance

14. Quick and dirty

15. Ideas how to improve?

16. Contacts:
My site: www.abykovets.com
Linkedin: https://linkedin.com/in/abykovets/
Facebook: https://facebook.com/artem.bykovets
Mail: a.bykovets@start-it.com.ua
+38 063 495 36 22