Introduction to Agile

Objectives• High level overview

o Agileo Scrum

• Take Home Messageo Gain enough of an understanding of Agile and Scrum to see how it will

work and how it may bring benefits to us and our customers.

How did we get here?• Traditional Software Development

o Waterfallo Based on False Assumptions

• Requirements can be predicted up front• You can perfect one phase before moving on to the next• Timeframes and budgets can be predicted upfront • Feedback isn’t valuable

• Agile is an answer to this problemo Frequently deliver software in increments o Get detailed requirements “just in time” before development to allow

for change. o Frequently gain feedback to adapt to change. o Agile is about communication and collaboration

Agile ManifestoWe are uncovering better ways of developingsoftware by doing it and helping others do it.Through this work we have come to value:

Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan

That is, while there is value in the items onthe right, we value the items on the left more.

Agile Principals• Early and continuous delivery• Welcome changing requirements• Deliver working software every couple of weeks to a couple of months, with a

preference to the shorter timescale. • Business people and developers must work together daily. • Give the team the environment and support they need, and trust them to get the job

done. • The most efficient and effective method of communicating is face-to-face

conversation. • Working software is the primary measure of progress. • Sustainable development, to maintain a constant pace indefinitely. • Technical excellence and good design enhances agility. • Simplicity 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, adjusts its

behaviour accordingly.

Agile Adoption

Apple

Agile Benefits• What gets better after going agile?

o Ability to manage changing priorities (84%)o Improved Project Visibility (77%)o Increased Productivity (75%)o Improved Team Morale (72%)o Faster Time to Market (71%)o Better alignment to business objectives (68%)o Enhanced Software Quality (68%)o Simplify Development Process (68%)o Reduced Risk (65%)o Improved engineering discipline (62%)o Enhanced Maintainability (60%)o Reduced Cost (49%)

Scrum

Sprints and Releases • Detailed requirements and design occur much

later in the process to allow for change• Each sprint results in potentially shippable

software• Sprint is time boxed and never extended• If requirements change drastically during the

sprint, or meeting the requirements becomes impossible. the sprint can be cancelled

Roles• Product Owner

o Close to the business side of the projecto Responsible for prioritising the backlogo Ensures the maximum ROIo Communicates the vision

• Scrum Mastero An expert in scrumo Facilitates and enables scrumo Coaches the team to be agile and keep to the frameworko Bulldozer of impediments

• Scrum Teamo Responsible for developing the producto Cross functional o Self organising o Makes a fixed commitment to what will be developed in a sprint

Artefacts• Product Backlog• Sprint Backlog• Burndown Chart

Burndown Chart

Ceremonies• Sprint Planning 1• Sprint Planning 2• Daily Scrum• Sprint Review• Sprint Retrospective• Also - Backlog Grooming

Customise Up• Scrum gives us the mandatory basic framework. • Most commonly customised with elements of

extreme programing (xp)o Unit Testingo Test Driven Developmento Coded UI testso Refactoringo Continuous Integrationo Pair Programmingo Whole Team

Expectations• Learning Curve• We must behave in an agile way• We must implement the whole process

o Don’t be wagileo Don’t be fragileo Do Scrum, not scrumbut.

Discuss• Any questions?