23. Then you go back to your workplace
Dependencies
24. Then you go back to your workplace
Carry overs
E
N
D
of
S
P
R
I
N
T
25. Then you go back to your workplace
How to do release planning?
26. Then you go back to your workplace
How to do release planning?
27. Then you go back to your workplace
People are too busy to listen to you
28. Then you go back to your workplace
Some people just don’t care
29. Then you go back to your workplace
Transition is hard
30. Then you go back to your workplace
Middle management is usually the opposing force
MIDDLE MANAGERS
31. Then you go back to your workplace
Companies around the globe struggle with the implementation of Agile
“…It takes at least 2 years to start to get comfortable with the
uncomfortable…”
“Someone” from the Scrum Alliance in 2016
32. Then you go back to your workplace
Usually just to be able to say:
“We are Agile!”
33. Then you go back to your workplace
Jeff Sutherland's Getting to DONE!! by Jeff Sutherland at DC Scrum
User Group on 5/21/2015
34. Then you go back to your workplace
Jeff Sutherland's Getting to DONE!! by Jeff Sutherland at DC Scrum
User Group on 5/21/2015
"There is a lot of bad agile out there" - 7:10
35. Then you go back to your workplace
Jeff Sutherland's Getting to DONE!! by Jeff Sutherland at DC Scrum
User Group on 5/21/2015
"There is a lot of bad agile out there" - 7:10
"If the management team has done waterfall for 20+ years it is a major shift...
or they go back to university or agile will never work in the company" - 39:40
36. Then you go back to your workplace
94% adoption of Agile in 2016
37. Then you go back to your workplace
A company to make a successful transition can't just change the IT
department... it must change everywhere in order to be Agile
38. Then you go back to your workplace
Companies that have very formal project management processes (e.g.
approval gates, benefits calculation, tons of effort upfront) aren't
compatible with Scrum
39. Then you go back to your workplace
Fixed Scope, Time and Resources projects (usually consultancy) aren't
compatible with Scrum… in fact they aren’t compatible with anything
40. Then you go back to your workplace
Overly concerned about metrics... and the wrong ones... is your team
doing points... or software? Are you measuring the real output of your
teams? And what about the outcome?
41. Then you go back to your workplace
Asking for estimates for developments with and without (writing) tests
42. Then you go back to your workplace
No time to clean tech debt... because it was the developers that
introduced the bugs in the first place
43. Then you go back to your workplace
The tech debt to be paid after the next release... and never is
44. Then you go back to your workplace
The implementation of Scrum that isn't improved anymore... because
it's done and it’s working
45. Then you go back to your workplace
The mature teams that we don't have so all the things that we want to
experiment... will not work because we only have immature teams
46. And on top of everything
Jurgen Appelo: “I’ve Had Enough”
47. And on top of everything
Jurgen Appelo: “I’ve Had Enough”
48. And on top of everything
Jeff Sutherland’s book title
49. And on top of everything
Mike Cohn talking about estimating tasks with hours
50. And on top of everything
Mike… have you ever heard of ScrumPLoP? And Yesterday’s Weather?
51. And on top of everything
Events with lots of companies’ success cases
52. And on top of everything
Did you ever aspired to become a CST?
53. And on top of everything
The Spotify model that not even Spotify follows
54. So at the end of the day
There aren't Scrum engineers... but Software engineers
Scrum Software
55. So at the end of the day
Scrum is not the goal... delivering software is
56. So at the end of the day
Maybe you should do XSKL (XP, Scrum, Kanban, Lean)
XP Scrum Kanban Lean
XSKL
Your Reality
57. Let’s go back to the beginning
Agile is a mindset with the purpose of "uncovering better ways of
developing software"
58. Let’s go back to the beginning
Since the beginning of Agile Portugal (in 2010) we are discussing the
same issues over and over again...
Where is the continuous improvement?
What have we learned since then?
59. Since the beginning of Agile Portugal (in 2010) we are discussing the
same issues over and over again...
Where is the continuous improvement?
What have we learned since then?
Let’s go back to the beginning
60. Let’s go back to the beginning
Agile is not about making money, self promotion or certifications
It's about:
PEOPLE CHANGE
IMPROVEMENT
HAPPINESS
CULTURE
EMPOWERMENT
PURPOSE
AUTONOMY
FEELING SAFE TO FAIL
HEARING AND BEING HEARD RESPECTING YOUR PEERS
BELIEVING THAT WE ALL GIVE OUR BEST AT WORK
RESPECTING YOUR STAKEHOLDERS
TRUST
61. Let’s go back to the beginning
We have a lot to learn with machines... Just go back to 1981 and take a
look at the Robustness principle (or Postel's law)