Very few Agile teams are all together co-located in one place. For most of us there are some barriers – walls at least or oceans at most. We are faced with situation when team is split in few different locations.
Being Agile (building agile team) is obviously harder in such setup – communication is critical and there are tools that can help to make it more effective, but this is not our topic today.
Our topic is more concrete: different tools are used to share information, progress statuses, etc. It can be simple wiki, it can be Google Docs, it can be separate dedicated specialized tool to visualize Scrum or Kanban board (for example).
All tools suck, we will check which suck less.
15. Features comparison
Important stuff
200
150
100
50
4,2
0
1 2 3 4 5
1 = not important not very
2 important important
3
4
5 = very important
16. Features comparison
Important stuff Unimportant stuff
200 200
150 150
100 100
50
4,2 50
1,6
0 0
1 2 3 4 5 1 2 3 4 5
1 = not important not very not very
2 important important important important
3
4
5 = very important
17. Features comparison
Important stuff Unimportant stuff
200 200
150 150
100 100
50
4,2 50
1,6
0 0
1 2 3 4 5 1 2 3 4 5
1 = not important not very not very
2 important important important important
3
4 Does not really care
5 = very important 200
150
100
50
3,0
0
1 2 3 4 5
not very
important important
18. Features comparison
Important stuff Unimportant stuff
200 200
150 150
100 100
50
4,2 50
1,6
0 0
1 2 3 4 5 1 2 3 4 5
1 = not important not very not very
2 important important important important
3
4 Does not really care Either like a lot or do not like at all
5 = very important 200 200
150 150
100 100
50
3,0 50
3,0
0 0
1 2 3 4 5 1 2 3 4 5
not very not very
important important important important
19. Features: web access
200
160
120
80
4,4
40
0
1 2 3 4 5
not important very important
30. Features: time management
3,2
70
3,5
56
3,1
42
28
2-4 3,3
3,0 14
... 0
1 2 3 4 5
>15 not important very important
3,7
31. Features: integration with version control,
bugtrackers, continuous integration systems, etc
70
56
42
28
3,5
14
0
1 2 3 4 5
not important very important
32. Features: integration with version control,
bugtrackers, continuous integration systems, etc
70
56
42
3,3
28
3,6 3,5
14
3,4
0
1 2 3 4 5
not important very important
33. Features: simplicity vs complexity
90
72
54
36
3,1
18
0
1 2 3 4 5
simple and powerful and
easy to use configurable
34. Features: simplicity vs complexity
90
72
54
2,9
36
3,3 3,1
18
3,1
0
1 2 3 4 5
simple and powerful and
easy to use configurable
42. “Ideal” tool portrait
Web based self-hosted tool, with customizable
workflow, so configurable to some degree and
still simple to use. Should have support for
iteration and release planning as well as for
Scrum.
ved
pro
ap
43. Now we are using
others
3% 10%
4%
4%
4% 33%
9%
33%
67. Tool selection strategy
• Do You really need some tool? Sure?
• Pick 3-4 features most important for You! Don’t think of everything You might
need some day at the future.
68. Tool selection strategy
• Do You really need some tool? Sure?
• Pick 3-4 features most important for You! Don’t think of everything You might
need some day at the future.
• Pick 2 tools covering most (80-90%) of your requested features.
69. Tool selection strategy
• Do You really need some tool? Sure?
• Pick 3-4 features most important for You! Don’t think of everything You might
need some day at the future.
• Pick 2 tools covering most (80-90%) of your requested features.
• Try 1st of them. If it looks OK – forget 2nd one and just use it. Best is the
enemy of the good.
70. Tool selection strategy
• Do You really need some tool? Sure?
• Pick 3-4 features most important for You! Don’t think of everything You might
need some day at the future.
• Pick 2 tools covering most (80-90%) of your requested features.
• Try 1st of them. If it looks OK – forget 2nd one and just use it. Best is the
enemy of the good.
• If it’s really bad, stick with 2nd option.