Rudy is graduated from non-IT/ non-Computer Science degree but start his debut as a Junior Web Designer at his own almamater, Brawijaya University - Malang with two silver bullet, Front Page and Photoshop Skill :) . Ever work for various company scale, from startup to enterprise, even freelancing. Now, working as an Agent of Happyness (read: Scrum Master) in XL Axiata. He is very excited to have awesome team, both business and developer team, together build better software development environment, in Agile way. And the team looks so happy to nurture their 'baby scrum' now. Also, he is actively going to Agile and Scrum event, meetup, congress, lean coffee, and also organize some scrum event in Jakarta. Means, still learn! *** This slide was shared at Tech in Asia Product Development Conference 2017 (PDC'17) on 9-10 August 2017. Get more insightful updates from TIA by subscribing techin.asia/updateselalu

1. S C R U Mmotivates people
how (come)
the story of baby scrum in XL Axiata

2. What is Scrum ?
introduction

3. What is Scrum ?
Scrum is a management and control
process that cuts through
complexity to focus on building
software that meets business needs.

4. Management and teams are able to get
their hands around the requirements and
technologies, never let go, and deliver
working software, incrementally
and empirically.
What is Scrum ?

5. Scrum itself is a simple framework for
effective team collaboration on
complex software projects.
What is Scrum ?

6. Agile in XL Axiata
background

8. Challenges
background

9. Long Project Assessment Process
Communication Problems - Silo
Frequent Requirement changes
1
2
3
4 Blaming Game
5 Bureaucratic
6 Low Level of Developer Happiness
7 Missunderstanding Agile & Scrum
Challenges

10. How it Works
walk the talk

12. Awareness
Sharing Session
Walk the Talk

13. General
Knowledge of Agile
Agile Manifesto
Scrum Fundamental
Time-boxed concept
Scrum Master
Development Team
Product Owner
Sprint Planning
Daily Scrum
Sprint
Sprint Review
Sprint Retrospective
Product Backlog
Sprint Backlog
Product Increment
Scrum ArtifactsScrum Roles
Scrum Events
How it work?

14. Agile Upstream Meeting
Scrum Master
Product Owner
IT Managers
Special Invitation

15. Insight, Lesson-Learned
what do we get from using scrum

16. Long Project Assessment Process
Communication Problems - Silo
Frequent Requirement changes
1
2
3
4 Blaming Game
5 Bureaucratic
6 Low Level of Developer Happiness
7 Missunderstanding Agile & Scrum
Challenges

17. Short Project Assessment Process
Intensive Communication / Openness
Frequent Requirement changes
1
2
3
4 Solution Oriented
5 Less Bureaucratic
6 Developer Happiness Level Increase
7 Good Understanding of Agile & Scrum
Insight, Lesson-Learned

18. Short Project Assessment
Process
Intensive Communication -Openness
Frequent Requirement changes
1
2
3
4 Solution Oriented
5 Less Bureaucratic
6 Developer Happiness Level
Increasing
7 Better Understanding of Agile &
Scrum
Long Project Assessment Process
Communication Problems - Silo
Frequent Requirement changes
Blaming Game
Bureaucratic
Low Level of Developer Happiness
Missunderstanding Agile & Scrum
Insight, Lesson-Learned

19. The requirements of the market change
invariably faster and only the ones who are
flexible and contemporary can react Time to
Market and stay competitive and create
themselves a competitive advantage.
Scrum allows the incremental development of
features. In time the customer receives the first
working versions, sees the progress and if
necessary can add some new ideas.
Transparency plays a great deal on various
levels of Scrum. Because of transparency all the
stakeholders are informed where the project is
at, it helps discovering weaknesses and it makes
the effective teamwork possible, which makes
Scum so efficient.
Scrum is not afraid of changes. On the contrary,
changes can be shown to the Product Owner at
any time and can be realized in the following sprint.
That way the customer gets the product he or she
desires.
Insight, Lesson-Learned
Competitiveness
Develop what is needed
Confidence through
transparency
Changes are welcome –
calculable change
management
1 2
3 4

20. Regular releases establish the condition to
recognize problems on time and react
promptly. There are long-term statements
about time factor and product completion
possible because of factors as team velocity.
Testing is an integrative component of Scrum at
every sprint. Only if the software is tested it is
“ready”. Methods as Continuous Integration are
very well applicable for securing the quality of
every object from the beginning on.
Scrum involves all the participants of the project.
Communication, collaboration, respect and the
understanding, what the customer requires or
what the team develops, is the basis for
successful projects.
Not the assignment of tasks but the collaborative
functioning and making decisions as a team is an
important part of Scrum. Software development is
seen as what it is: A creative and multisided activity
that can only work properly when everyone takes
responsibility.
Insight, Lesson-Learned
Recognize risks in time –
systematic risk
management
Build Quality in
Keep it lean and agile –
efficient collaboration and
customer satisfaction
5 6
7 8 Scrum is Fun

21. Most Important Motive
Develop Modus Operandi

22. for any work task that involves most than the most basic
cognitive challenge, basic financial reward systems
simply do not work. In fact, they can lead to worse
performance.
–Daniel Pink

23. Autonomy Mastery Purpose
Develop Modus Operandi

24. Autonomy
self-organizing
responsibility
protect the autonomy
support the autonomy
transparency
Develop Modus Operandi

25. Mastery
retrospective
continuous learn
inspect + adapt
Develop Modus Operandi

26. Purpose
commitment
respect
visionary
focus
Develop Modus Operandi

27. “Having a fast car is awesome, but to become
the fastest with your fast car is the most
important.”

28. The Path to Agility

29. What Next ?
training and sharing for
XL agility improvement

30. Introduction to Agile for
People Management (HRD)
People Management (HRD)
will probe, how people in agile
culture work and having fun
concurrently.
Product Ownership
Design Thinking
User Experience
Agile Product Ownership
Knowledge Sharing
Sharing Session
Lightning Talk
Fish Bowl
Continuos Delivery (CD)
Agile way to development
Why CD ?
How to CD ?
What Next?

37. END OF PRESENTATION.
Thank You!
rudyrahadian@gmail.com
+62 8788 7231 581