What Makes A Great Dev Team - Mike Robinson

1. What makes a great Development Team? What are the challenges faced by development teams and how do they meet them. Mike Robinson

2. Who are you?

3. Who are we?

5. 1 - What is the problem? 2 - How do we solve the problem?

6. 1 - What is the problem?

7. From the customer’s point of view

8. From the development team’s point of view

9. 2 - How do we solve the problem?

10. Process

11. Technology

12. Tools

13. People Tools Process Technology Successful Projects

14. People

15. Different methods are usually viewed as being more or less lightweight, in practice methods contain some elements that are appropriate for different scales of Software Development RUP Scrum RAD FDD DSDM Waterfall XP Crystal

16. Regardless of scale or complexity, all Software Development projects should be based on a set of core values and practices

17. Values

18. C h a n g e

19. Simplicity

20. Quality

21. Commitment

22. v i sibility

23. C o l l a b o r a t i o n

24. Value Focus on

27. Process

28. “ You improvise. You adapt. You overcome.” Clint Eastwood In Heartbreak Ridge

30. Evaluate the project Evaluate Add additional Controls Select Approach Review & Adapt Notes Evaluate the project based on the criteria that have been selected for the organisation.

31. Evaluate the project Evaluate Add additional Controls Select Approach Review & Adapt Notes Score the project on each criteria based on a range and metrics selected by the organisation.

32. Select Approach Evaluate Add additional Controls Select Approach Review & Adapt Notes Select the simplest method which will achieve the project. Light in this case.

33. Add Additional Controls Notes Identify the areas where additional controls are required. Evaluate Add additional Controls Select Approach Review & Adapt

34. Size - Personnel 2-12 12-50 50+ Daily meetings Multi skilled team Deliver small and fast Team of teams meeting More up front planning Split work around architecture Continuously Integrate at multiple levels Hierarchical requirements Collaboration tools Start small then scale Confirm architecture first

35. Review and Adapt Notes As part of the same feedback loops put in place for reviewing the system, the process should also be review to see where it could be simplified or improved. Evaluate Add additional Controls Select Approach Review & Adapt

36. Lifecycle for Light Product Owner Project Manager Team Stakeholders Users Preparation Produce Business Case & Vision Requirements Analysis Produce Initial Project Backlog & Release Plan Iteration Planning Update Project Backlog & Agree Iteration Backlog Design Review Working Software Project wrap up Project Review & Training & Support Iterative Phase 2-4 Weeks Phases Build Deploy Test Daily 15min Meeting Roles Project & Iteration Backlog Impediments List Project, Release & Iteration burn down Working Software Artifacts Review Process

38. “ If you want a guarantee, buy a toaster.” Clint Eastwood In The Rookie

39. Contact Details Mike Robinson [email_address]