What is agile? Where did it come from, and how can it help me? This session will go through a history of agile, including the origins of waterfall, the Toyota Production System and lean manufacturing, the creation of the agile manifesto, and how these all lead to the modern agile development frameworks we use today. By exploring the original design and intent behind agile principles and practices, we'll also uncover common pitfalls to agile adoption, and insights into overcoming them.

1. JOYCE VARGAS | PROGRAM MANAGER, AGILE SCRUM MASTER | ATLASSIAN | @JOYCEPANGVARGAS
Agile Fundamentals

2. Source: https://bit.ly/2uMzj7Z

3. FEBRUARY 2001…
Source: https://bit.ly/2CWCnmr

4. SNOWBIRD, UTAH…

5. Kent
Beck
Alistair
Cockburn
Ward
Cunningham
Ron
Jeffries
Ken
Schwaber
Jeff
Sutherland
Jim
Highsmith
Mike
Beedle
Arievan
Bennekum
Dave
Thomas
Steve
Mellor
Andrew
Hunt
Martin
Fowler
RobertC.
Martin
JonKern
BrianMarick
James
Grenning

6. Kent
Beck
Alistair
Cockburn
Ward
Cunningham
Ron
Jeffries
Ken
Schwaber
Jeff
Sutherland
Jim
Highsmith
Mike
Beedle
Arievan
Bennekum
Dave
Thomas
Steve
Mellor
Andrew
Hunt
Martin
Fowler
RobertC.
Martin
JonKern
BrianMarick
James
Grenning
Scrum
Extreme Programming
LIGHTWEIGHT METHODS

7. AGILE ADAPTIVENESS, RESPONSE TO CHANGE
Source: https://bit.ly/2ONVKCN, https://bit.ly/2UxcLGH, https://bit.ly/2I1s1FL

8. Source: https://bit.ly/2I1s3xn

9. Manifesto for Agile
Software Development
Source: https://bit.ly/2K88PZ3

10. Principles behind
the Agile Manifesto
Source:https://bit.ly/2uOAZhg

11. Principles behind
the Agile Manifesto
Customer Satisfaction
Welcome Change
Deliver Frequently
Work Together
Motivated Team
Face to Face
Working Software
Constant Pace
Technical Excellence
Simplicity
Self Organization
Reflect and Adjust

13. MARTIN FOWLER
I just hoped that greater
communication would lead to
something interesting. I didn't
expect much at that meeting…

14. 18 YEARS LATER…DO ≠ BE

15. Agile as a concept is finally coming of
age as a philosophy and way of thinking
in lieu of being seen as a mere project
management methodology.
FORBES.COM

16. 🧠 ?

17. 🧠 EMPIRICISM

18. Source: https://bit.ly/2I0yXTN

19. Transparency
Empiricism is the foundation of Scrum
Inspect Adapt

20. A core tenet of Extreme Programming
Embrace Change

21. 1900 1960 1990 2010
AgileManifesto
Scrum
1600s
Bacon,
Galileo
1600s
1956
Royce
1970
1980
Ishikawa,
Ohno
1980s
Deming
1950 1995
ExtremeProgramming
1996
2001

22. 1600s
FrancisBacon GalileoGalilei
1600s 1970 1980s1950
Source: https://bit.ly/2eyGfRI, https://bit.ly/2VrIqXq

23. 1600s
FrancisBacon
GalileoGalilei
1600s 1970 1980s1950
Source: https://bit.ly/2Vp3zBd

24. WilliamEdwardsDeming
1600s 1970 1980s1950
1950
Source: https://bit.ly/2FZs4Qc

25. WilliamEdwardsDeming
1950
1600s 1970 1980s1950
Source: https://bit.ly/2uNxLu8

26. WilliamEdwardsDeming
1950
1600s 1970 1980s1950
PDCA
Source: https://bit.ly/2I0NWwM

27. WilliamEdwardsDeming
1950
1600s 1970 1980s1950
AGILE
Source: https://bit.ly/2WORQMN

28. WinstonW.Royce
1970
1600s 1970 1980s1950
Source: https://bit.ly/2FPWnaN

29. WinstonW.Royce
ManagingtheDevelopment
ofLargeSoftwareSystems
1970
1600s 1970 1980s1950

30. WinstonW.Royce
System
Requirements
Software
Requirements
Analysis
Program
Design
Coding
Testing
Operations
1970
1600s 1970 1980s1950

31. WinstonW.Royce
“riskyandinvitesfailure…”
“hasneverworked…”
System
Requirements
Software
Requirements
Analysis
Program
Design
Coding
Testing
Operations
1970
1600s 1970 1980s1950

32. KaoruIshikawa TaiichiOhno
1980s
1600s 1970 1980s1950
Source: https://bit.ly/2IdtDvq, https://bit.ly/2GWwWUS

33. KaoruIshikawa
1980s
1600s 1970 1980s1950
Source: https://bit.ly/2FOLKFo, https://amzn.to/2K3Ctyq

34. TaiichiOhno
1980s
1600s 1970 1980s1950
Source: https://bit.ly/2Ui0Ih9

35. TaiichiOhno
1980s
Toyota
Production
System
1600s 1970 1980s1950
Source: https://amzn.to/2uLVqev

36. TaiichiOhno
1980s
Toyota
Production
System
1600s 1970 1980s1950
Eliminate Waste
Just in Time
Lean Manufacturing
Make Problems Visible

37. 1980s
TaiichiOhno
看板
kàn bǎn
1600s 1970 1980s1950
Source: https://bit.ly/2ON4OYJ

38. 1980s
TaiichiOhno
1600s 1970 1980s1950
Source: xxxxSource: atlassian.com/software/jira

39. 1900 1960 1990 2010
AgileManifesto
Scrum
1980
Ishikawa,
Ohno
Deming
1956
Royce
1600s
Bacon,
Galileo
1600s 1970 1980s
1950 1995
ExtremeProgramming
1995
2001

40. What is agile?

41. Agile is a growth mindset. It’s
a way of working grounded
in a culture of learning.
AHMED SIDKY (AKA DR. AGILE)

42. 🧠MINDSET
4VALUES
∞PRACTICES
BEING
AGILE
DOING
AGILE
12PRINCIPLES
Scrum Extreme Programming
Lean Kanban
Acceptance Test Driven Development Behavior Driven Deve
Continuous Integration Continuous Delivery Ethnography Design Thinking
Minimum Viable Product Sprint Retrospective Stand Up Experimentation
User Research
Paired Programming
Tasking Story Pointing Back

43. Agile in practice

45. The former state of things…
Didn’t deliver on
commitments
Useless
estimates
Stalled work
mid-sprint
😟 😟 😟

46. The former state of things…
Didn’t deliver on
commitments
Useless
estimates
Stalled work
mid-sprint
Unsustainable
pace of work
Meetings
without value
Individuals, rather
than a team
😟 😟 😟
😟 😟 😟

47. DefofReady
DefofDone
SCRUM FRAMEWORK
Product
Backlog
Sprint
Backlog
Increment
Sprint
Daily
Scrum
Retrospective Review
Sprint
Planning
2 3 3 5
Scrum
Master
Product
Owner
Dev
Team

48. DefofReady
DefofDone
SCRUM FRAMEWORK 2 3 3 5

49. DefofReady
DefofDone
SCRUM FRAMEWORK 2 3 3 5
Scrum
Master
Product
Owner
Dev
Team

50. DefofReady
DefofDone
SCRUM FRAMEWORK
Product
Backlog
Sprint
Backlog
Increment
2 3 3 5
Scrum
Master
Product
Owner
Dev
Team

51. DefofReady
DefofDone
SCRUM FRAMEWORK
Product
Backlog
Sprint
Backlog
Increment
Sprint
Daily
Scrum
Retrospective Review
Sprint
Planning
2 3 3 5
Scrum
Master
Product
Owner
Dev
Team

52. DefofReady
DefofDone
SCRUM FRAMEWORK
Product
Backlog
Sprint
Backlog
Increment
Sprint
Daily
Scrum
Retrospective Review
Sprint
Planning
2 3 3 5
Scrum
Master
Product
Owner
Dev
Team

53. ∞PRACTICES
Scrum
Backlog Refinement
Kanban
Extreme Programming
Acceptance Test Driven Development
Behavior Driven Development
Story Pointing
Tasking
User Stories
Planning Poker

54. Radiate information

55. Developing Testing DoneSprint Backlog
Kanban

56. Conversation Confirmation DefinedCard Sprint Ba
Kanban

57. DEFINITIONS
• Passes Code Review
• Passes QA
• Defects are resolved
• All tasks are completed
• Product Owner acceptance
• User story written
• Coarse estimate done by team
• Designs defined
• Open questions answered
• Acceptance criteria defined and
agreed upon by team
• Refined estimate done by team
Definition of Ready Definition of Done

58. Commitment
StoryPoints
Completed
Velocity

59. Burndown

60. Sprint 7
This is crap! I want out.
Not feeling so good about this right now.
I can live with this, but there are many things that need to be fixed.
Pretty happy, but there are things that need to be fixed.
There’s always room for improvement but I’m super happy with this.5 = 😃
4 = 🙂
3 = 😐
2 = 😞
1 = 😭
Sprint 8 Sprint 9 Sprint 10
4.2 - 🙂 4 - 🙂 4.1 - 🙂 3.8 - 😐
Team Health

61. Increase frequency
of communication

62. The most efficient and effective
method of conveying information
to and within a development
team is face-to-face conversation.
PRINCIPLE BEHIND THE AGILE MANIFESTO

63. MORE MEETINGS?!
Source: https://bit.ly/2TZzEOt

64. Backlog Refinement Agenda
Sprint Planning Agenda
Sprint Retrospective Agenda
Sprint Review Agenda
Meetings with Value

65. 1. What did I do yesterday that helped
the team meet the Sprint Goal?
2. What will I do today to help the
team meet the Sprint Goal?
3. Do I see any impediment that
prevents me or the team from
meeting the Sprint Goal?
Daily Scrum

66. Small Team Size
Source: https://bit.ly/2IbJxGJ, https://bit.ly/2VoLeEq

67. Small units of work

68. Backlog Refinement
Behavior Driven Development
User Stories
Definition of Ready

69. Backlog Refinement
Definition of Ready
Tasking
Definition of Done

70. NO FLOW 😭
Sprint Backlog Developing Testing Done

71. FLOW 😃
Backlog Developing Testing Done

72. Agile estimation

73. RELATIVE VS. ABSOLUTE
Relative values:
Absolute values: 24 oz 16 oz 8 oz
Large Medium Small
Source: https://bit.ly/2IdyjRX

74. RELATIVE PARAMETERS
Effort Risk Complexity Uncertainty
NOT time

75. Planning PokerStory Pointing
Source: https://bit.ly/2FQZm2K, https://bit.ly/2YTpPFs

76. COLLECTIVE
Dev QA Design

77. Product Backlog Card Conversation Confirmation Sprint Ba
REFINED THROUGHOUT
Uncertainty Definition
Coarse Estimates Refined Estimates

79. Agile benefits

80. TURNS DEVELOPMENT UPSIDE DOWN
FLEXIBLE
FIXED
scope
scoperesourcestime
time resources
WATERFALL AGILE

81. DESIGNED FOR COMPLEXITY AND UNCERTAINTY
Sim
ple
Com
plicated
Com
plex
Chaos
Technology
Scope
Unknown
Know
n
Unknown
Source: https://bit.ly/2Tu8Iau

82. SMOOTHS OUT THE PRODUCTIVITY CURVE
WATERFALL
AGILE
Time
Productiveoutput
Source: https://bit.ly/2I8MA2u

83. REDUCES RISK
WATERFALL AGILE
TimeTime
Value
Value
Value delivered Risk of failure
Source: https://bit.ly/2FT0T8p

84. ADVOCATES FOR DEDICATED TEAMS
%ofTime
# of Projects
Time lost to context switching
Working time available
0
100
5
Source: https://bit.ly/2FUQdWP

85. EMBRACES T-SHAPED SKILLS
Testing Product
Design
Designer
Testing Analysis
Development
Developer
Dev Research
Testing
Tester

86. Continuous improvement is
better than delayed perfection.
MARK TWAIN

87. Thank you!
JOYCE VARGAS | PROGRAM MANAGER, AGILE SCRUM MASTER | ATLASSIAN | @JOYCEPANGVARGAS