The document presents insights on agile development, highlighting its importance over traditional waterfall methodologies through principles that prioritize customer satisfaction and adaptability. It discusses the role of teams, effective communication, and sustainable development practices within agile frameworks, as well as the evolution of roles and ceremonies in agile processes. The emphasis is on delivering valuable software frequently and fostering an environment conducive to motivated individuals and self-organization.

1. Agile Development in practice
Nigel Fernandes
Architecture Practice Manager

2. Github.com/nigelfds
Architecture Practice Manager
I’ve worked for:
ThoughtWorks, Envato, Suncorp, WorldVision, NBN, Unicief, Nokia,
TheTrainline, PCT, Real Estate Australia, MYOB, Channel 4, ForwarGroup,
Westpac, etc
I’ve worked in
India, China, UK, Germany, Uganda, Brazil, and Australia

3. 1 in 3 of you would find a job on SEEK (statistically)

5. Agenda:
- Why Agile.
- Waterfall & Agile
- Agile Principles
- Agile as a Cookbook
- Roles Ceremonies Artifacts @ SEEK
- Being adaptive - fighting for adaptability over efficiency

6. So why Agile?

7. A story
about
phones

8. Rate of change is accelerating
Connected Company – Dave Gray

9. State of Agile Survey 2015

10. A cost story
Too Long
32% of projects delivered
successfully
Long duration defers revenue
(Source: Standish Report 2009)
Time wasted on Junk
52% of requirements implemented
64% of functionality rarely used
(Source: Standish Report 2003)

11. Not all projects are equal

13. Waterfall vs Agile

14. Software for the mars rover

15. Software for businesses

16. Agile Principles @ Seek

17. Group activities @ Monash

18. Agile principles @ SEEK
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.

19. Agile principles @ SEEK
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 maximizing the amount of work not done--is essential.
The best architectures, requirements, and designs emerge from self-
organizing teams.
At regular intervals, the team reflects on how to become more effective,
then tunes and adjusts its behavior accordingly.

20. Agile as a cook book

22. State of Agile
Survey 2015

23. Human Methods
Agile methods are people oriented rather than process oriented

24. State of Agile Survey 2015

25. Evolving
Roles, Ceremonies and Artifacts
@ SEEK

26. Story walls

27. Stand ups

28. The original roles
Pig Roles
Core team of Developers, Business
Analysts and QAs
Project/Iteration manager
Product owner
Chicken Roles
Architecture, Security,
Operations, Strategy, Data
Analysts, UX etc.

29. Evolving from there
Delivery Managers over Scrum masters
Steering committees with accountability
Design, Operations & Architecture as part of core team

33. Being adaptive – trading for
adaptability over efficiency

41. Summary

42. Thank you