Colin Weaver

1. The Eleven Essential Behaviours of Successful Agile Project Teams Colin Weaver

2. The Agile Manifesto Individuals and interactions over processes and tools. Working software over comprehensive documentation. Customer collaboration over contract negotiation. Responding to change over following a plan. "That is, while there is value in the items on the right, we value the items on the left more."

3. Principles Behind The Agile Manifesto • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. • Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. • Business people and developers must work together daily throughout the project. • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. • The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

4. Principles Behind The Agile Manifesto • Working software is the primary measure of progress. • Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. • Continuous attention to technical excellence and good design enhances agility. • Simplicity -- the art of maximising the amount of work not done -- is essential. • The best architectures, requirements, and designs emerge from self-organising teams. • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.

5. Daily Scrum Meeting Product Backlog Potentially Shippable Product Increment Sprint Backlog 24 hrs 2-4 weeks

6. 11

7. 1

8. Courage

9. Courage • satisfy the customer • Welcome changing requirements • Deliver working software frequently • Business people and developers must work together daily • motivated individuals/trust • face-to-face conversation • Working software as a measure • constant pace • technical excellence and good design • Simplicity • self-organising • the team reflects Courage • If you’re going to fail, fail fast

10. 2

11. Desire to Improve

12. satisfy the customer • Welcome changing requirements • Deliver working software frequently • Business people and developers must work together daily • motivated individuals/trust • face-to-face conversation • Working software as a measure • constant pace • technical excellence and good design • Simplicity • self-organising • the team reflects Improve Desire to Improve • Agile is a mindset change Courage

13. 3

14. Collaborative

15. satisfy the customer • Welcome changing requirements • Deliver working software frequently • Business people and developers must work together daily • motivated individuals/trust • face-to-face conversation • Working software as a measure • constant pace • technical excellence and good design • Simplicity • self-organising • the team reflects Courage Improve Collaborate Collaborative • Encourage rather than criticise

16. 4

17. Openness

18. satisfy the customer • Welcome changing requirements • Deliver working software frequently • Business people and developers must work together daily • motivated individuals/trust • face-to-face conversation • Working software as a measure • constant pace • technical excellence and good design • Simplicity • self-organising • the team reflects Courage Improve Openness Collaborate Openness • Be honest / admit weaknesses

19. 5

20. Trust

21. satisfy the customer • Welcome changing requirements • Deliver working software frequently • Business people and developers must work together daily • motivated individuals/trust • face-to-face conversation • Working software as a measure • constant pace • technical excellence and good design • Simplicity • self-organising • the team reflects Courage Improve Openness Trusting Collaborate Trust • “You must trust and believe in people or life becomes impossible”

22. 6

23. Simplicity

24. satisfy the customer • Welcome changing requirements • Deliver working software frequently • Business people and developers must work together daily • motivated individuals/trust • face-to-face conversation • Working software as a measure • constant pace • technical excellence and good design • Simplicity • self-organising • the team reflects Courage Improve Openness Trusting Simplicity Collaborate Maximise what you don't do. Simplicity "The ability to simplify means to eliminate the unnecessary so that the necessary may speak" - Hans Hofmann

25. 7

26. Pride

27. satisfy the customer • Welcome changing requirements • Deliver working software frequently • Business people and developers must work together daily • motivated individuals/trust • face-to-face conversation • Working software as a measure • constant pace • technical excellence and good design • Simplicity • self-organising • the team reflects Courage Improve Openness Trusting Simplicity Pride Collaborate Pride • Be the best you can

28. 8

29. Focused

30. satisfy the customer • Welcome changing requirements • Deliver working software frequently • Business people and developers must work together daily • motivated individuals/trust • face-to-face conversation • Working software as a measure • constant pace • technical excellence and good design • Simplicity • self-organising • the team reflects Courage Improve Openness Trusting Simplicity Pride Focused Collaborate Focused • Deliver business value

31. 9

32. Motivated

33. satisfy the customer • Welcome changing requirements • Deliver working software frequently • Business people and developers must work together daily • motivated individuals/trust • face-to-face conversation • Working software as a measure • constant pace • technical excellence and good design • Simplicity • self-organising • the team reflects Courage Improve Openness Trusting Simplicity Pride Focused Motivated Collaborate Motivated • Deliver the team commitment

34. 10

35. Proactive

36. satisfy the customer • Welcome changing requirements • Deliver working software frequently • Business people and developers must work together daily • motivated individuals/trust • face-to-face conversation • Working software as a measure • constant pace • technical excellence and good design • Simplicity • self-organising • the team reflects Courage Improve Openness Trusting Simplicity Pride Focused Motivated Proactive Collaborate Proactive • Contribute and help the team find solutions

37. 11

38. Responsible

39. satisfy the customer • Welcome changing requirements • Deliver working software frequently • Business people and developers must work together daily • motivated individuals/trust • face-to-face conversation • Working software as a measure • constant pace • technical excellence and good design • Simplicity • self-organising • the team reflects Courage Improve Openness Trusting Simplicity Pride Focused Motivated Proactive Responsible Collaborate Responsible • Collective responsibility. Succeed or fail as a team

40. ] [ Good Governance Good Governance Agile Evolved Agile Principles