How to get team work started using this tool. You will find several practical examples and common rules for its.

1. GETTING STARTED WITHTHE
TEAMTRUST CANVAS
Presented by:Alexey Pikulev

2. ALEXEY
PIKULEV
!
!
Creator at
InTeamWeTrust.com
@AlexeyPikulev
!
!
#inteamwetrust

3. 1.INTRODUCTION

4. TEAMTRUST CANVAS
ORIGINAL METHODOLOGYTO STRENGTHEN
YOURTEAM PERFORMANCE

5. 8 ESSENTIAL
ASPECTS
!
- Clarity
- Connection
- Compassion
-Value
- Competency
- Commitment
- Contribution
- Consistency
!

6. CLARITY
How shall we build and support the
clarity, openness and transparency?
!

7. CONNECTION
!
How can we connect and engage with
each other?
!

8. COMPASSION
!!
Are we ready to be compassionate?
!
!

9. VALUES
!!
How can we align them?
!
!

10. COMPETENCY
!!
How do we grow our competency?
!
!

11. COMMITMENT
!!
How do we take responsibility and fulfill it?
!
!

12. CONTRIBUTION
!!
Is anything getting done?
!!
!

13. CONSISTENCY
!!
Is our trust and confidence rising or falling
each week?
!
!

14. +1 EXTRA
!
What else is important
for us?
!

16. 2.GROUND RULES ANDTIPS

17. #1.WHAT IS
TRUST?
!
TRUST

18. #2.FIND
YOUR WAY
!
1
2
3

19. #3.WRITE
ON STICKERS
! test

20. #4.USETHE
ACTION
!
Action

21. #5.USE
DIFFERENT
COLORS
As is…
to be…

22. #5.USE
DIFFERENT
COLORS
Fact
Assumption

23. #6.CALL
ATTENTION
!
Action
Action

24. 3.CASE STUDIES

25. CASE #1.TEAM FORMING

26. key points
discuss together
daily stand-up

27. key points
discuss together
daily stand-up meet the clientsharing same
space
retrospectives

28. key points
discuss together
daily stand-up meet the clientsharing same
space
retrospectives
respect
code review
lessons learned
pair
programming

29. key points
discuss together
daily stand-up meet the clientsharing same
space
retrospectives
respect
code review
lessons learned
pair
programming
definition of
done
result
acknowledgment
continuous
delivery

30. key points
discuss together
daily stand-up meet the clientsharing same
space
retrospectives
respect
code review
lessons learned
pair
programming
definition of
done
result
acknowledgment
continuous
delivery
challenges

31. CASE #2.TEAM STORMING

32. daily stand-up
project manager
provides
transparency about
the project

33. daily stand-up
project manager
provides
transparency about
the project
teambuilding
there are no
stupid questions

34. daily stand-up
project manager
provides
transparency about
the project
teambuilding
there are no
stupid questions
we embrace amistakes
recognize the
features of each

35. daily stand-up
project manager
provides
transparency about
the project
teambuilding
there are no
stupid questions
we embrace amistakes
recognize the
features of each
skill balance
identify a
conflict of
interest
development
motivation
attract the
attention of that
commitment may
be broken
compromise

36. daily stand-up
project manager
provides
transparency about
the project
teambuilding
there are no
stupid questions
we embrace amistakes
recognize the
features of each
skill balance
identify a
conflict of
interest
development
motivation
attract the
attention of that
commitment may
be broken
compromise
sharing feedback
with the team
from the client
demonstrate
the results
regular update
agreements
visualization

37. CASE #3.TRUST WITH CLIENTS

38. understand and
adhere to client
policy
discuss the
values of team
and client

39. understand and
adhere to client
policy
discuss the
values of team
and client
share road map
co-location
business trip to
client with the
team
team building
with client
pay on time
meet deadlines/
discuss

40. understand and
adhere to client
policy
discuss the
values of team
and client
share road map
co-location
business trip to
client with the
team
team building
with client
pay on time
meet deadlines/
discuss
defining and
monitoring
metricsfeedback from
end users
joint project
management
trainings
Proactive
attitude

41. SUMMARY
!
- Build dialogue
- Find your own way
- Update often
!
!

42. ALEXEY
PIKULEV
!
Thank you!
!
@AlexeyPikulev
info@inteamwetrust.com
!
!
!
#inteamwetrust