Teamwork Agile way

How to form a software development team? Why I choose cross-functional feature team over functional layer team? The true story of one team.

Transcript

1. TEAMWORK Jelena Barinova | @jfiodorova | bebetterleader.com AGILE WAY
2. ADFORM Founded in DK YEARS 270 11 employees Offices in 12 countries
3. ADFORM SYSTEM
4. ADFORM DEVELOPMENT Head of development Andrej Ads Manage- ment TEAM
5. How to form a team? For software product development
6. Two approaches to form a team Functional Cross-functional System analysts Development team Common functional expertise Representatives from the various functions Developers Testers
7. Why we choose cross-functional ? Faster feature delivery Customer focus Knowledge sharing cross-functional
8. Two approaches to define scope for team Layer ownership Feature ownership Database team Backend team Frontend team Feat 1 Feat 2 Feat 3 Database Backend Frontend Feat 1 team Feat 2 team Feat 3 team
9. Why our goal - feature teams? Increased value throughput Autonomy Single Point of Contact feature
10. Two types of team members I-shaped skills T-shaped skills Narrow but expert knowledge Wide range of shallow & one deep skill JavaScript JavaScript C#.NET Puppet
11. Why I hire T-shaped people? May cover each other May suggest alternative solutions T-shaped
12. Summary Cross-functional teams Feature oriented T-shaped members
13. What surrounds us? In software product development
14. Two approaches to control any process Defined Empirical Do Check Act Plan Step 1 Step 2 Step 4 Step 3 Step 5 Materials Product
15. Which approach should be used? Defined Empirical Tesla factory Adform Kaunas
16. Two approaches for optimization Sub-optimization System optimization System analysts Developers Testers
17. Game: pass the pennies 20 coins 5 departments 5 managers (track time) 1 CEO (track time)
18. Learning points When batch size decreases, total cycle time decreases As total time decreases, worker time increases! People idle more when batch size is high
19. Optimization Sub-optimization is valid for defined process System optimization for empirical process Feature request Feature delivered Feature request Feature delivered 6 5 7 6 Total system throughput - 5 Total system throughput - 6
20. Multitasking or single-tasking Working on several features at a time Working on one feature at a time Feature 1 delivered Feat 1 Feat 2 Feat 1 Feat 3 Feat 2 Feature 1 delivered Feat 1 Feat 2 Feat 1 Feat 3 Feat 2 Feature 2 delivered Feature 2 delivered time time
21. Game: fill-in the table How long will it take to fill the table? What influences speed? Fill in form horizontally (1, I, A, 2, II, B..). Measure time. Fill in form vertically (1..10, I..X, A..J). Measure time. 1 I A 2 II B 3 III C … 10 X J
22. Learning points There is no multitasking, but fast switching between tasks Time increases when switching happens
23. Multitasking in team Complete highest priority tasks first Work in small batches 1 completed feature is always better than 7 started
24. Summary Empirical process: Inspect and adopt Single-tasking: Focus on highest priority, work on small tasks System optimization: Team is able and is enabled to decide everything
25. True story of teamwork DSP team
26. Team setup Team advocate Product owner UI developers Cassandra developer .NET developers
27. Extended team Delivery managers Product director Client support Sales Development team
28. Feature path from idea to client Roadmap I Quarter II Quarter III Quarter IV Quarter September Backlog October November October October Feature 1 Feature 2 Feature 3 Feature 4 Feature 5 Feature 6 Task board Dev Deploy Live Task 1 Task 2 Task 3 Task 4 Task list Task 1 Task 2 Task 3 Task 4 Task 5 Feature 1
29. Meetings Backlog review (1 hour, biweekly, team) Standup (15 min, daily, team) Review (1 hour, biweekly, extended team) Retrospectves (30 min, biweekly, team) Other meetings on demand
30. Other facts Team in one room 3 TV screens to monitor system in a team room 6 white boards (all walls covered in whiteboards) Personal coffee machine
31. What are your questions
32. HAPPY TEAMWORK! Jelena Barinova | @jfiodorova | bebetterleader.com
33. Please give me FEEDBACK!
34. Sources Pictures: Money designed by Joe Harrison from The Noun Project Timer designed by Casey Ochinang from The Noun Project Arrow designed by Luke Macauley from The Noun Project Rectangle designed by Renee Ramsey-Passmore from The Noun Project Arrow designed by Eakarius from The Noun Project Tesla factory picture is taken from The Washington Times Communities Idea to gather feedback: From Jurgen Appelo blog noop.nl Games: Pass the pennies game is taken from Crisp’s blog