I was invited by Chris Gonsalves (Associate Dean Student Engagement) and Mehran Vahid (Lecturer, Faculty of Information Technology) to present a guest lecture to roughly 200 students @ Monash University on Agile Software Development (June 2016).
Since the students had already covered the theory of Agile, Scrum and RUP, this talk focussed on the real world aspects of Agile in practice and used SEEK as a baseline example.
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)
4.
5. Agenda:
- Why Agile.
- Waterfall & Agile
- Agile Principles
- Agile as a Cookbook
- Roles Ceremonies Artifacts @ SEEK
- Being adaptive - fighting for adaptability over efficiency
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)
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.
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