1. Using Scrum in Indonesian Banks Workshop
Joshua Partogi
http://www.scrumway.asia
@ScrumWayAsia
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

2. Who Am I?
• I am a Scrum expert from Indonesia and the only Professional Scrum Trainer
through Scrum.org based in Asia to date
• Scrum.org is the home of Scrum. We host the Scrum Guide - Scrum Body of
Knowledge - in 30 languages and provide assessments to allow people to
evaluate themselves and improve.
• I translated Scrum Guide to Bahasa Indonesia
• I have successfully helped many Indonesian companies transition to Scrum
• So you can say that I am a reliable source anything related with Scrum
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

3. Today we are going to discuss how to implement
Scrum in Banking environment in Indonesia
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

4. Compliance
• In implementing Information Technology in Bank, Indonesian Banks must
comply with:
• Surat Edaran Bank Indonesia Nomor: 9/30/DPNP Tanggal 12 Desember
2007
• Peraturan Bank Indonesia Nomor: 9/15/PBI/2007
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

5. Misconception (1):
These two regulations is Waterfallaholic
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

6. The truth...
• Waterfall is one of System Development Life Cycle
• Agile is another
• But Bank of Indonesia never specifically mentioned that you have to use
Waterfall
• At first sight the processes may seems like Waterfall
• SEBI Nomor: 9/30/DPNP point 2.4.2 specifically mentioned that you can use
Agile software development
• Scrum is one of Agile flavour
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

7. So we have solved one problem...
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

8. Mapping Scrum to SE BI
• Remember that Scrum is just a framework and we are responsible to fill in the
missing pieces
• Scrum context is in Product Development, which means we can plug in any
other processes in SE BI that is not related with Product Development
• SE BI never said that you have to do the processes sequentially, but you have
to do all of the processes
• We will do all of the processes in SE BI but not sequentially
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

9. Analyze Design Code Test Release
Analyze Analyze Analyze Analyze Analyze
Design Design Design Design Design
Review
Review
Review
Review
Review
Plan
Plan
Plan
Plan
Plan
Code Code Code Code Code
Test Test Test Test Test
Release Release Release Release Release
You don’t have to release every Sprint, but you
This is 1 Sprint can if you are confident with your code integrity
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

10. Risk Management
• SE BI talks about Risk Management over and over again.
• Scrum will make risks in your banking projects painfully visible throughout the
project for you to manage (not only before the project).
• These risks are exposed so you can make hard decisions based on it.
• And everyone needs to be proactively involved to manage these risks when it
comes right to the surface.
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

11. Misconception (2):
This Scrum thing seems to have little planning,
how can I get the big picture?
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

12. You can even have your own Scrum team for this
Analyze Analyze
Design Design • Release/
• Feasibility
Study
Implementa>on
Review
Review
• Project
Ini>a>on
Plan
Plan
Release
Planning Code Code • Post
Implementa>on
• Project
Charter
• Maintentance
Test Test • Disposal
Release Release
Scrum prefers emerging architecture.
The output of this meeting is the Product Backlog or the Release Backlog.
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

13. Planning
• Gather requirements and design architecture in detail only if you are smart
enough to predict the whole future.
• The only way to predict the future is not to make detailed requirements but to
inspect and adapt the outcome of your work.
• Detailed documentation doesn’t proof that you will get a good software.
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

14. Detail
Effort or Time
But details is sometimes expensive
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

15. So we have solved two problems...
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

16. Misconception (3):
Product Backlog is the only documentation in
Scrum
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

17. Documentations in SE BI
• Naming convention
• User Manual
• Application detailed description
• Inline coding documentation
• Business Requirement Document
• Functional Spec Documentation
• etc ...
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

18. Testings in SE BI
• Unit Testing
• System Integration Testing
• Stress Testing
• User Acceptance Test
• etc ...
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

19. Non Functional Requirements
• Data Backup
• Data Verification
• Data Retention
• Disaster Recovery
• Security
• etc...
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

20. We will not lower quality because that is not professional
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

21. So we have solved three problems...
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

22. Concerns
That sounds great, but how can possibly do all that
in one Sprint?
Shall we have 30 days Sprint?
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

23. Focus on getting things “DONE”
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

24. Co-location lowers communication complexity and
increases productivity.
Scrum expects high-bandwidth communication, full
interaction and collaboration.
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

25. Other concerns
Scrum sounds great. But our developers need to
be multitasking.
Scrum recommends developers not to be
multitasking as it automatically lowers product
quality and in the long run it can make developers
less intelligent.
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

26. It’s your call now. Scrum will expose a lot of
dysfunctions in your organization. It may be
painful along the way but it can make everyone
joyful in the long run.
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.

27. Contact us today for consulting work
and let us help you!
info@scrumway.asia
This presentation is the work of Joshua Partogi of @ScrumWayAsia. Please kindly mention the original source when you are citing from this slide.