Agile teams and responsibilities talk done at PrairieDevCon 2013 in Saskatoon

1. Agile Teams
Roles & Responsibilities

2. Amir Barylko
(About me & how to find me)

5. Software Quality
Expert

6. Agile Coach

7. Architect

8. Developer

9. Cook

10. amir@barylko.com
@abarylko
http://bit.ly/abarylkop

11. DISSAPOINTMENT
MANAGEMENT

12. Your expectations
here...

13. There’s always lunch!

14. LOOK MA!
NO SLIDES

15. WHAT IS AGILE?
Amir Barylko - Agile Teams
MavenThought Inc.

16. ROLES IN CLASSIC TEAMS
Amir Barylko - Agile Teams
MavenThought Inc.

17. ROLES IN AGILE TEAMS
Amir Barylko - Agile Teams
MavenThought Inc.

18. HOW DO WE FIND THEM?
Amir Barylko - Agile Teams
MavenThought Inc.

19. SOME MAY CHANGE
Amir Barylko - Agile Teams
MavenThought Inc.

20. SOME MAY BE THE SAME
Amir Barylko - Agile Teams
MavenThought Inc.

21. SOME CAN’T CHANGE ALL
Amir Barylko - Agile Teams
MavenThought Inc.

22. ROLES
Classic
Better approach
Collaborative
Micro
Managing
Team oriented
Budget
oriented
Help team
to be productive
PM
Amir Barylko - Agile Teams
MavenThought Inc.

23. ROLES
Classic
BA
SA
Requirements
documents
Design
documents or
diagrams
Amir Barylko - Agile Teams
Better approach
Acceptance
scenarios
MavenThought Inc.

24. ROLES
Classic
Silo
Dev
Unpredictable
Better approach
Collaborative
Focus on quality
Test Driven
Scenario Driven
Amir Barylko - Agile Teams
MavenThought Inc.

25. ROLES
Classic
Better approach
Automated
Manual
QA
Amir Barylko - Agile Teams
Last step is
testing
Acceptance scenarios
drive the features
Works with analysts to
define the scenarios
MavenThought Inc.

26. ROLES
Classic
Better approach
Solution structure
Architect
Show
powerpoint
presentations
Amir Barylko - Agile Teams
Application
structure
Ver much about
coding and being in
the trenches
MavenThought Inc.

27. ROLES
Classic
Better approach
Security
standards or
other std
Review materials
after is done
Work with team while is
getting implemented
DBA
Authorize/review/
centralize any
operation to the
database
Funnel to any DB
operation
Helps when needed,
mostly with tuning,
sharding, etc....
Amir Barylko - Agile Teams
MavenThought Inc.

28. WIN AS A TEAM

29. •The
goal is to produce value
•while
shortening the “lead time”
•Helping
other team members
•should
be a common practice
•even
if is not your usual role
Amir Barylko - Agile Teams
MavenThought Inc.

30. SUMMARY

31. •The
•the
•is
roles may change, however
most important factor
the attitude as a team
•towards
•and
Amir Barylko - Agile Teams
delivering value
feel good about it :)
MavenThought Inc.

32. Thank you!

33. amir@barylko.com
@abarylko
http://bit.ly/abarylkop

34. Books

35. Photo Credit
•
Under http://creativecommons.org/licenses/by/2.5/
•
•
Bill Ward, Derek Schin's Trucks 1, http://flic.kr/p/m5L5S
•
Jeremy Keith, Roast beef, http://flic.kr/p/TKUz
•
Rob Campbell, Field of daisies, http://flic.kr/p/6QJjU4
•
•
Joe Cheng, DSC_7820-01, http://flic.kr/p/2Zt2u
Karin Dalziel, The Thinker, http://flic.kr/p/4UYArc
Under http://creativecommons.org/licenses/by-sa/3.0/us/
•
Derick Bailey, SOLID Motivational Posters, http://bit.ly/17aVaHg

36. Photo Credit 2
•
•
How to write good code, http://xkcd.com/844/
Understanding flow charts, http://lifehacker.com/5909501/how-tochoose-the-best-chart-for-your-data