I´d like to share this presentation I created to give awareness of that is Agile, the scrum framework and why we should consider that in our daily basis, personal and proffessional level.

1. Enthusiasm
Clarity
Terror
Confusion

2. Ground rules

3. Expectations?
What I want to learn in this workshop?

5. Agile
Why should you care?

7. Why Agile?
Industrial economy
Predictable behavior

8. Information-based economy
Adaptable/ empirical behavior

10. Inspect Adapt
Transparency
Empiricism
Decision
making
Experience Knowledge

12. Inspect Adapt
Transparency
Empiricism
Decision
making
Experience Knowledge
Agile Frameworks
Empiricism
Complex

13. Agile is a mindset based on Values and Principles!
Practices
Principles
Values

14. Manifesto of 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.”
Source: Agile Manifesto

15. 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.
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.
Source: Agile Manifesto- Principles
Principles behind Agile Manifesto

16. Exercise 1- Connect the Values and Principles
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.
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.
A) Individuals and
interactions over
processes and
tools
B) Working software
over
comprehensive
documentation
C) Customer
collaboration over
contract
negotiation
D) Responding to
change over
following a plan

17. “Agile” is not fast/quick- it´s
the art of simplify the work
that needs to be done and
deliver more value as soon as
possible

18. Iterate AND/OR Increment?

19. "the more output you turn out, the more variety you get and the better are your
chances to assembling something truly original"
"quick to start and slow to finish can boost your creativity, that you can motivate
yourself by doubting your ideas, and embrace the fear of failing to try, that you
need a lot of bad ideas in order to get a few good ones"
Adam Grant- The Originals

21. Scrum framework
Sprint

22. Scrum framework

24. Courage
Origin: greek “action from the heart”
- Always keep transparency (even under
pressure)
- During Daily/ Review, assume that the
delivery failed or the expectation did not
met and course correct asap
“ Failure doesn't mean you are a
failure, it just means you have not
succeeded yet. I have tried 99 times
and have failed, but on the 100th time,
came success.”
- Einstein-

25. Focus
Origin: latin "fire", "dash of light"->
direction
- Prioritization of the Product
Backlog Item (PBI)-> increase value
to be delivered in that period, with
less wastes!
- Sense of Urgency (what is urgent?
what is important?)
Techniques that might help: Pomodoro technique/ Eisenhower Matrix

26. Commitment
Origin: latin "compromissis"-> a
willingness to give your time and
energy to something that you believe
in, or a promise or firm decision to do
something:
- Involved x Committed
- Shared purpose!
Video that I recommend-> Are you a giver or a taker?

27. Respect
Origin: latin: “look at back, regard”. Look
at more then 1x
- Different skills, experiences,
background-> multidisciplinary
teams
- Everyone in the team should attend
the events and should be heard

28. Openness
Origin: latin “open, discover”-> be open
and vulnerable
- Adapt and course correct always
needed
- Constant feedback
- Ask for help
Illustration by Peter Bennett

29. Resource utilization trap
Do and do not
(module for vitual team only)

32. Paper Plane factory
(module for F2F attendies only)

33. Paper Plane Factory

34. Goal
- Create a production line to produce paper planes
Team
- Few people, but effective!
Production line
- The airplane starts at one end and ends at
the other end of the production line.
- The applied engineering must be a team
decision
Create your comporate symbol (1:30 min)

35. Our First Contract
- The Air Force wants a new airplane
- The representative of the entity contacted your company to analyze the
proposals
- The representative wants to know how many airplanes you would produce
in 3 (three) minutes
- You have 1 (one) minute to pass the estimate

36. Proposal Analysis
- The Air Force has liked the estimates and will open competition
- You must produce a prototype of the airplane in 3 (three) minutes. The
scope is:
- Must have 12 windows
- Must have a cabin
- Must have the corporate symbol
-On both wings
-At the rear
- And of course, it must fly.

37. What the client really wants
S
S
S

38. Hands On!
- With the scope in hand, now it's up to you!
- The company wants to produce more takes the contract
- You will have 3 (three) sprints of 3 (three) minutes to produce the planes
- They will have another 3 (three) minutes to evaluate and adapt the process
to the end of the sprints, aiming to improve productivity
- They should give an estimate of production at each start of sprint

39. Rules
- Sprints and retrospective / 3 minute planning! Unconditional respect for
time
- The airplane starts at one end and ends at the other end of the production
line.
- The engineering to be applied is team decision
- The product must meet the scope. If the time runs out and the product is
unfinished, it can go back to production at the next sprint

40. Lessons Learned

43. Enthusiasm
Clarity
Terror
Confusion

44. Team Performance
What/when/how to measure?

45. Metrics drive behaviors!