1. The document discusses the author's journey transforming their organization to adopt agile practices. They faced challenges like a traditional culture, multi-layer approvals, and relying on vendors. 2. The author started small by not trying to change culture initially but add new habits. They documented processes and started with small teams to influence others. 3. Adopting agile practices provided benefits like early releases, faster development and response to changes, increased engagement with business users, and cost savings from using modern technologies and avoiding vendor dependencies.

1. AGILE TRANSFORMATION
MY AGILE, MY ADVENTURE
By : Adhitia Putra Herawan

2. MY PROFILE
“11 Years experience in IT Industry, newbie programmer,
learn to be good architect, never be a Scrum Master, or
even agile trainer, love to play football, listen a music, and
sing at toilet.”
senior_solutions_architect@ptsmartfrentbk
solutions_architect@allianzindonesia
analyst_and_design_expert@ptkeretaapiindonesia
chief_technical_officer@ptcybertrendintrabuana
https://www.linkedin.com/in/adhitia-herawan-arch/
a.putraherawan@gmail.com

5. QUALITY ???

7. AGILE THAT I USED TO KNOW
Un-structured
Unpredictable No Pattern Where is the
Document?

8. “IT IS PRODUCT DEVELOPMENT INSTEAD
OF PROJECT DEVELOPMENT”
AAAAHHH THAT’S
WHY !!!

9. ENLIGHTMENT

10. START THE JOURNEY
Traditional Culture
Big Organisation
Multi Layer Approval Level
Rely on Vendor
CHALLENGES
IT as Operation Old School Style

11. THE ROADSHOW
“Act as sales that offering new product that will bring something good
for organisation.”

12. FRESH GUY
“Don’t try to change the culture in the first place, but try to add new
habit in daily activity.”

13. START SMALL
“Try to start with small team and influence the others by showing the
enthusiasm.”

14. TRY TO DOCUMENTED EVERYTHING
“We start using our wikipedia. Try to write somethings and documented
everything.”

15. START IN THE ONE OR TWO PRODUCT
DEVELOPMENT
LEGACY APPLICATION NEW APPLICATION
1. We leave it as it is.
2. Planning to re-engineer the
application and architecture in
the future.
3. Uses scrum as project activity
monitoring.
1. Scrum as main methodology
2. New architecture implemented
3. CI and CD implemented
4. Focus on quality
5. Involve DEVOPS Engineer

17. OUR BIG PROBLEM

18. CALMS MODEL

19. OUR PRE-REQUISITES

20. OUR STRATEGY

21. OUR CI

22. OUR CI

23. OUR TECHNOLOGY
CENTRAL REPOSITORY
CONTINUOUS INTEGRATION
ISSUE TRACKER
AUTOMATION INFRASTRUCTURE
DEPLOYMENT TOOLS

24. OUR TECHNOLOGY

25. WHAT’S CUSTOMERS THINK ABOUT THE
CHANGES ?

26. BREAKTHROUGH ON METHODOLOGY
“Early Release, Develop Fast, Recovery Fast,
Response Fast To Changes”
Tracking Activity
Business Users
Involvement
Bi-Weekly Review
Each activities
inside
development
process is
monitored and
updated every
day. All progress
are transparent
among all
stakeholders.
Business users as
customers are
involved daily in
the project, and
has responsibility
to decide the
target of each bi-
weekly based on
product and
customer value.
All modules are
reported every 2
weeks and
customers will
decide whether
the product is
ready to release
or not.

27. MORE ENGAGEMENT WITH BUSINESS USERS
“By being agile, customers act as product owner who has responsibility
and has fully ownership to the product.”
1. Business user has more responsibility to the
product
2. Has a customers-values view
3. Team player, involve deeper in the project
activities

28. MAINTAIN LEVEL OF ENTHUSIASM
“Daily stand-up, update every time, helping each others, crossing
functionality.”
1. Daily stand-up to update all activities during
the projects,
2. Has an awareness of every member in the
team,
3. Cross-functionality, backup each other
4. Maintain enthusiasm every day.

29. EARLY RELEASE and FAST DEVELOPMENT
“Deliver the product in earlier phase. Identify the early features based on
Customers-value, Release early, Release Often”
• Waterfall methodology, long time duration of
deliverables,
• 2 Years development, and not even close to
end,
• Most of problem found at end of
development phase,
• Dispute between user requirements and
product development
• Rigid and not flexible to any user changes.
• Agile methodology, early release, release
often,
• 3 Months development, and product is ready
to used,
• Adaptive and flexible to user changes of
request,
• Problems are identified in early phase and
able to close in early phase as well,

30. COST SAVINGS and FAST RESPONSE
“Saving a lot of revenue by implementing internally, and able to focus in
advance technologies”
• IDR 9 Billion to implement existing application,
• Having dependencies to vendor,
• New cost and new spend for every new user
requirements or changes during the project,
• 2 Years development almost utilise more than
1500 man-days.
• IDR 1.9 Billion to implement the new
application,
• Saving more than IDR 7 Billion of revenue,
• No need to spend new budget to have
changes or new features during the project
development,
• Response to any changes from user,
• 3 Months development and only utilise less
than 200 man-days.

31. COST SAVINGS in INFRASTRUCTURE
“Using new and advance technology which support for good performance
and economics in the same time”
• Billion IDR spend to buy a server,
• Physical server still used, less flexibility and
rigid when we want to scale the performance,
• In-consistency still happened between
development and production,
• Complex in deployment process.
• Using “container” technology, which does not
need Billions IDR,
• Flexible and easy to scale the performance,
• Consistent between development and
production environment,
• Fast to handle the deployment process.

32. Let’s discuss!
Thank you