Discussion in fishbowl format to find out how Scrum and DevOps should more power-full if we use it together and properly, then validating with data and convergence of CEO Scrum.org and CEO DevOps Institute.

1. August 19, 2019
SCRUM DAY
BANDUNG
How (Can) Scrum & DevOps Walk TogeTher
to Build a High-Quality Product Delivery Organisation

2. linkedin.com/in/rgesit/

3. Development teamProduct owner Operation team
Stakeholder consultant Recruiter

7. Hire
ONE EXPERT

8. Hire
GROUP OF EXPERTS

9. CONTRACT
BIG GROUP OF EXPERTS

10. REALITY
(Please Help me …..)
expectation
(We will help each other)

11. When your company brings in outside consultant
To change and speed up the process with rush and bad approach

12. and when it fails
or feels failed ...

13. Hard
Work
sacrifice

15. WDYT
What Do You Think ?

16. WDYT
What Do You Think ?

17. WDYT
What Do You Think ?

18. WDYT
What Do You Think ?

19. WDYT
What Do You Think ?

20. WDYT
What Do You Think ?

21. DevOps is all about people. All kinds of people. Thought
leaders. Tool providers. Enterprise leadership. Stakeholders.
Engineers. Customers. Humans.
WDYT
What Do You Think ?

22. WDYT
What Do You Think ?

23. WDYT
What Do You Think ?

24. WDYT
What Do You Think ?

25. WDYT
What Do You Think ?

26. WDYT
What Do You Think ?

27. We need a DevOps Guide ?
WDYT
What Do You Think ?

28. DevOps is just about tools ?
WDYT
What Do You Think ?

29. DevOps Evolution of Agile ?
WDYT
What Do You Think ?

30. Agile is Just a Development Phase ?
WDYT
What Do You Think ?

31. Could Ops team be a part of Development Team ?
WDYT
What Do You Think ?

32. In Scrum,
releases are done only at the end of the Sprint ?
WDYT
What Do You Think ?

33. The CI/CD is only introduced on DevOps ?
WDYT
What Do You Think ?

34. * Do The Simplest Thing That Could Possibly Work (DTSTTCPW)
You Are Not Gonna Need It (YAGNI)
*

35. DevOps is about, "Ops who think like devs.
Devs who think like ops." ?
WDYT
What Do You Think ?

36. WDYT
What Do You Think ?

37. WDYT
What Do You Think ?

38. WDYT
What Do You Think ?

40. Agile and Scrum, actually, are
not interchangeable synonyms,
but two inseparable ingredients in a so@ware development
ecosystem, pure chemistry.
Agile are the principles to Scrum,
Scrum is a foundaCon for agility.
— Gunther Verheyen

41. — DevOps Defini<on

45. Continuous Delivery Continuous DeploymentContinuous Integration
Commit Everything Toggle and Train Chaos Monkey

47. WDYT
W
hat Do You Think ?

48. Two Movements, One Goal
Agile and DevOps are the primary means by which organiza9ons are driving these changes. They share much in common: faster delivery cycles, smaller increments (or
batches) of releases, using feedback to improve, removing waste and impediments. Their emphasis varies, and this some9mes leads people to believe that they are
different things. Agile emphasizes team interac9ons, culture, and values, while DevOps emphasizes delivery pipelines and flow. But, Agile is also concerned with
automa9on, and DevOps is also concerned with communica9on and culture.
Two movement, One Goal
Agile emphasises team interacCons, culture, and values,
while DevOps emphasises delivery pipelines and flow.
But, Agile is also concerned with automaCon, and DevOps is also concerned
with communicaCon and culture.
*The Convergence of Scrum and DevOps

49. Your system was released not with a bu?on / system trigger
but with a pen for a wet signature

51. End2End of Chaos

52. WHY ?
Give
UNDERSTANDING
STORY STAR
WHo ?
AMBASSADOR/
Sponsor
How ?
Build
ABILITY
WHAT ?
Create
WORK SYSTEM
SKILL SYSTEM

53. DEVOPS
Dev wants changeOps wants stability

54. Is this familiar with you ?

55. *The Convergence of Scrum and DevOps
Also, agility is often undermined by the organization
itself, which reduces credibility and success.
Alienated stakeholders Culture clash Increased fear Bad NoOps Mindset

56. How Dev perceives Ops
Narrow-minded
No care about business/momentum
Slow to change
Bureaucra9c process geeks
Too rigid
Less technically skilled
Risk adverse
Unreliable infrastructure
More of a bo?leneck than an enabler
Stop sign
Rule followers
Speed bump, Slow
Overwhelmed, anxious
Risk-adverse, controlling
Iron-clad
Process – ITIL – stability, availability
Overly-structured

57. How Ops perceives Dev
Undisciplined
Tech-centric (No business savvy)
Unrealis<c
Careless
Uncommunica<ve
Risk takers
Unreliable code
More of a boOleneck than an enabler
Irritable, defensive
Undocumented
Risky
Turn and burn
Edgy (make the ops people nervous)
– trust us!, over-confident
Hyper – moving at light speed
Too busy to follow rules
Unstructured

58. The balance of automation, process and
empowered teams
*The Convergence of Scrum and DevOps

59. The power of Cross-functional
Cross-funcConal teams have all competencies needed
to accomplish the work without depending on others not part of the team.
*The Convergence of Scrum and DevOps
Reduce the number of hand-offs Develop all the skills to deliver value Increase the automa<on

60. Let’s start (again)
Change starts with a customer who could be beLer served,
and a product delivery organizaCon that wants to make them more saCsfied.
*The Convergence of Scrum and DevOps

61. *The Convergence of Scrum and DevOps
Change starts with a customer who could be better
served, and a product delivery organization that
wants to make them more satisfied

62. 1 Integrate Your Approach
to Delivering SoXware
2 Add Feedback Loops 3 Grow a Culture of Con<nual
Experimenta<on & Learning
Building teams that are aligned
to products and the customer
Including the right people to
deliver Done soXware
Taking responsibility for the
complete value chain, not just
the development bit
Releasing soSware more
frequently and measures into
Product Backlog Items
Sprint Reviews more visible and
transparent to the business
Instrument soXware to gain
beOer understanding
Put in place evidence-based
measures to enable teams to
improve
Empower the Product Owner to
implement changes and make
product decisions
Include “experimental” backlog
items
Create a shared incen<ve model
that aligns team members and
stakeholders
Restructuring the porVolio
around products/customers
Removing queues from the
system
Provide Opera<ons Services to
the Scrum Teams
Automate, automate, and
automate
PuXng in place environmental
support for instrumenta9on and
analy9cs
Building shared dashboards
Being part of the Scrum Team(s),
Daily Scrum, Sprint Review and
Sprint Retrospec9ve
Ensuring Sprint Retrospec9ve
issues are taken into any DevOps
ini9a9vesDevelopment
Opera<on
Teams
*The Convergence of Scrum and DevOps

63. *The Convergence of Scrum and DevOps
Scrum believes that professionalism is so important,
that the Scrum Guide includes the five values of focus,
openness, respect, commitment and courage.

64. *The Convergence of Scrum and DevOps
The ultimate end goal is to no longer have a separate
operations and Scrum Team, but instead have Scrum
Teams and a community that supports them.

66. Organiza<onal Models
Accountability
and Responsibility
Self-Organizing
and Empowerment
Does the amount of complexity and the unknown make
any shared model impossible to operate?
Does it make sense for these specialist skills to be
learned by more people?
Is it important for legal reasons to have a separation of
ownership?
One shared Product Backlog
A single, outcome-based dashboard that everyone
works toward
A Product Owner who is accountable for what is
delivered to customers
High-performing teams decide how they are organized
(work, tools and process)
Accountable for the value and quality of results they
deliver
Not micro-managed on how to get those results
Focus on an empirical approach that starts from idea
and finishes with customers

68. According to CBR, businesses should
look at these seven skills:
1. Flexibility
2. Security skills
3. Collaboration
4. Scripting skills
5. Decision-making
6. Infrastructure knowledge
7. Soft skills

69. $100M $55M (45%)
Development costs reduced
(140%)
Increase in the number of products being supported
5% 40%
Increased capacity for innova9on
The Organisation of HP achieved those results through applying DevOps and Agile
principles at scale
(Leading the Transformation by Gary Gruver and Tommy Mouser)

70. You can release multiple times in The Sprint.

71. Operation can be a part of Scrums Team.

72. What most important isn't about the right terminology
but how you improving the way you to deliver value.

73. Don't let the obstacles prevent you for a long time to produce high value.
Break the glass and let's collaborate
— rgesit

74. What are you waiting for?
Let’s get the journey started!

75. August 19, 2019
SCRUM DAY
BANDUNG
How (Can) Scrum & DevOps Walk TogeTher
to Build a High-Quality Product Delivery Organisation