The Sofware Development Life Cycle codifies how we build applications. Optimizing this process allows working software to be delivered more quickly and efficiently.
12. Define the Problem
Plan > Design > Build > Deliver > Repeat
● Define it. Really. Write it down.
● Explore the Status Quo
● Study Competition
● Discover Alternatives
15. “To communicate effectively, the code must be based on
the same language used to write the requirements - the
same language that the developers speak with each
other and with domain experts.”
Eric Evans, Domain-Driven Design: Tackling Complexity
in the Heart of Software
Plan > Design > Build > Deliver > Repeat
16. Plan > Design > Build > Deliver > Repeat
if X is in Y then multiply A by B
17. Plan > Design > Build > Deliver > Repeat
if ZIP CODE is in THIS STATE then multiply the
SHOPPING CART TOTAL by SALES TAX
29. Plan > Design > Build > Deliver > Repeat
Iterate
Like a Boss
30. Plan > Design > Build > Deliver > Repeat
Don’t Go Chasing
Waterfalls
31. Plan > Design > Build > Deliver > Repeat
Fight for
the User
32. Plan > Design > Build > Deliver > Repeat
Individuals and Interactions
Working Software
Customer Collaboration
Responding to Change
33. Manifesto for Agile Software Development
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.
34. Kent Beck
Mike Beedle
Arie van Bennekum
Alistair Cockburn
Ward Cunningham
Martin Fowler
James Grenning
Jim Highsmith
Andrew Hunt
Ron Jeffries
Jon Kern
Brian Marick
Robert C. Martin
Steve Mellor
Ken Schwaber
Jeff Sutherland
Dave Thomas
agilemanifesto.org
35. This Talk Was Really About
AGILE!
Pro Tip: Make Clickbait Titles for Conference Talks