An introduction to "agile development" and what "agility" means in the world of software. Principles to embrace, culture changes to pursue, and so forth.

1. AGILITY
@DmitrySharkov dsharkov@gmail.com
A PRIMER

2. TODAY'S AGENDA
How did we get here?
What agility means to us
Philosophy behind agile development
Work culture and agility
Roles in agile development
Following the principles
Beyond process - people and tools
An example approach
Measuring success
Revisiting our purpose
Q & A

3. WHY ARE WE TALKING ABOUT AGILE
DEVELOPMENT?
Because it beats the alternative?
Because developers, customers, and everyone in-between
has found it makes them happier.
Because developers, customers, and everyone in-between
has found it makes them more successful.

4. THE FAILURE OF WATERFALL SHOULD NOT COME AS A SURPRISE.
HTTP://WWW.MOUNTAINGOATSOFTWARE.COM/BLOG/AGILE-SUCCEEDS-THREE-TIMES-MORE-OFTEN-THAN-WATERFALL
WHY ARE WE TALKING ABOUT AGILE
DEVELOPMENT?
Success: on budget, on time, with all planned features

5. What is AGILITY?
The ability to change
[direction] efficiently.
In software development, it also includes a philosophy
around making people as productive as possible
regardless of the need for frequent or sudden change.

6. Change is inevitable
Must the cost of change rise
exponentially as time passes?
Fight change and it will.
Enable change through agility.
432 PARK AVE

7. People aren't "assets"
HTTPS://THEDILBERTSTORE.COM

8. SNOWBIRD, UTAH
WHAT
WHEN WHERE
FEBRUARY 2001
THE AGILE MANIFESTO
AND THE PRINCIPLES BEHIND IT

9. We are uncovering better ways of developing software by
doing it and helping others do it. Through this work we have
come to value:
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.
THE AGILE MANIFESTO

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

11. 7 - Working software is the primary measure of progress.
8 - Agile processes promote sustainable development. The sponsors,
developers, and users should be able to maintain a constant pace
indefinitely.
9 - Continuous attention to technical excellence and good design
enhances agility.
10 - Simplicity — the art of maximizing the amount of work not done
— is essential.
11 - The best architectures, requirements, and designs emerge from
self-organizing teams.
12 - At regular intervals, the team reflects on how to become more
effective, then tunes and adjusts its behavior accordingly.
PRINCIPLES BEHIND THE AGILE MANIFESTO

12. BUILDING TRUST
SHARING OWNERSHIP
WORKING

13. TOGETHER
REMOVING

14. OBSTACLES
DOING

15. VALUABLE

16. WORK
MY SIMPLE AGILE PRINCIPLES
ELIMINATING RISK

17. MY SIMPLE AGILE PRINCIPLES

18. TRANSPARENCY
EMPOWERMENT
9 P
Know what 100% of the
team is doing 100% of
the time. Communicate.
Trust each other to be great.
Eliminate obstacles to success. Let
teams self-manage. Give everyone
the tools to be the best they can be.

19. This

20. is

21. a

22. big

23. culture

24. change
Trading old values and old approaches for new.

25. Businessandclient-centrism
Self-managingteams
Servant-leadership
Focusonvaluedelivered

26. ROLES IN SOFTWARE DEVELOPMENT

27. ROLES IN SOFTWARE DEVELOPMENT
• DEVELOPMENT TEAM - Cross-functional; testing, coding,
database work, design - all skills present, ideally.
• PRODUCT OWNER (or proxy) - Fully engaged with the
team. Responsible for maximizing ROI. Decides priority
of work and understands the business needs and values.
• PROCESS MANAGER - Helps the team work towards
increased agility, build good habits, and evolve a
methodology. Coaches to the agile principles.
• PROJECT MANAGER - Empowers the team to be as
productive as possible. Mentors and guides. Helps
resolve obstacles and escalate issues of risk.

28. Following the Principles
TRANSPARENCY

29. Following the Principles
DOING
VALUABLE
WORK
BUSINESS CENTRIC

30. Following the Principles
ELIMINATING
RISK
REDUCING
WASTE

31. Following the Principles
BULDING
TRUST
WORKING
TOGETHER
SHARING
OWNERSHIP

32. Following the Principles
EMPOWERING
DEVELOPERS

33. Following the Principles
CONTINUOUSLY
IMPROVING

34. TYING IT TOGETHER…
SCRUM

35. TYING IT TOGETHER…
SCRUM EVENTS
•Daily Stand-Up
•Sprint Planning
•Sprint Review
•Retrospective

36. SCRUM PROVIDES SCAFFOLDING
Track work remaining
Measure pace
Make a commitment
Write the software
Test the software
Document the software
Define 'DONE'
Measure success
IT DOES NOT DICTATE HOW TO…

37. Beyond Process

38. MEASURING SELF-IMPROVEMENT
Velocity
Regression count
Predictability
Clarity of goal
Stability
Self-management
Team happiness

39. MEASURING SUCCESS
Business value / time
Production defects
Average cost of defects
On-time delivery
Team happiness

40. AGILITY
WRAP-UP