Note: This presentation is an update of my previous uploaded presentation found here: http://www.slideshare.net/AmirSyafrudin/scrum-methodology-managing-project-efficiently-and-accurately This is a presentation material used to introduce Scrum Framework in the Directorate General of Taxes, Ministry of Finance, Republic of Indonesia.

1. Scrum Framework
Manage Anything Efficiently and Accurately

2. Introduction
• What this is about:
− Antithesis of Waterfall: Agile
− Specifically: Scrum
• Learning objectives:
− To understand how to migrate to Scrum

3. DRAW SOMETHING

4. Let’s Draw Something!
• Decide on a “picture”:
− Draw something!
• Pick a role:
− Buyer.
− Artist.
• Begin!

5. THE CASE OF AGILE

6. FBI’s Sentinel
• Purpose: To digitize case files.
− To rapidly compare cases and discover connections between
them.
• Estimation: starts March 2006, completes December 2009,
costs $451 million, includes 4 phases.
• Reality: reached August 2010, spent $405 million,
employed 400 staff, delivered 2 of 4 phases, might
require additional money and time to finish.
• Agile: started November 2010, completed November
2011, spent $30 million, employed 45 staff, delivered 4 of
4 phases.

7. FBI’s “Agile” Sentinel
• Initiate “Scrum Studio”.
• Development iteration: every 30 days.
• Release iteration: every 3 months.
− Release type: field pilot.
• National scale deployment finished by June,
2012.
• Highlights:
− More than 90% cost saving.
− More than 70% time saving.

8. Why Agile? Requirements...
• ... are not easy to define at the start.
• ... are not easy to be completely
collected at the start.
• ... are vulnerable to changes in:
− business processes,
− regulations,
− target users, etc.

9. AGILE

10. Individuals and interactions
Working software
Customer collaboration
Responding to change
Processes and tools
Comprehensive documentation
Contract negotiation
Following a plan
Agile Manifesto

11. Agile Principles
1. Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile
processes harness change for the customer's competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a
couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout
the project.
5. Build projects around motivated individuals. Give them the
environment and support they need, and trust them to get the job
done.
6. The most efficient and effective method of conveying information to
and within a development team is face-to-face conversation.

12. Agile Principles (2)
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The
sponsors, developers, and users should be able to maintain a
constant pace indefinitely.
9. Continuous attention to technical excellence and good design
enhances agility.
10.Simplicity--the art of maximizing the amount of work not
done--is essential.
11.The best architectures, requirements, and designs emerge
from self-organizing teams.
12.At regular intervals, the team reflects on how to become more
effective, then tunes and adjusts its behavior accordingly.

13. SCRUM FRAMEWORK

14. Roles
Scrum
Team
Scrum Master
Product
Owner
Development
Team

15. Ceremonies
Sprint Planning
Daily Scrum
(Standup
Meeting)
Sprint Review
(Sprint Demo)
Sprint
Retrospective

16. Workflow

17. Estimation
• Estimate:
− User Story
− Story Points
− Velocity
• #NoEstimate

18. MIGRATING TO SCRUM

19. Total Implementation
• Disseminate the implementation of Scrum.
− To every single person in the organization,
especially the people involved in software
development.
• Adopt Scrum as a whole.
− Avoid partial adoption, i.e. cherry-picking.
• Put a time constraint.
− It’s a project, not a process.
• Provide a project room.
− To improve communication and collaboration.

20. Policy Adjustment
• Adjust the Development Phase.
− Needs to be iterative and incremental.
• Adjust the artifacts.
− URS, SRS, and SDD might need adjustments.
− Make it as simple as possible.
• Make sure the adjustments run well.
− Assign separate technical writer to write URS,
SRS, or even SDD.

21. BINARY COUNTING METHOD
AND SCRUM

22. 1
2 4 8
16

23. Binary Counting Method
• Same hand.
• Same fingers.
• Different counting method.
• It’s merely about getting used to the
new counting method.

24. Scrum
• Same personnel.
• Same working time.
• Same working tools.
• Different mind set and behavior.
• It’s merely about getting used to the
new mind set and behavior.

25. LET’S DO A SMALL TEST

26. Scrum Open Assessment
• Free Scrum Assessment at Scrum.org:
− https://www.scrum.org/Assessments/Open-Assessments
• Test Instructions:
− 30 questions.
− 30 minutes.
− No pause, no save.
• Pass mark: 85% ~ 26 questions.

27. LET’S TRY SCRUM

28. Scrum Project Simulation
• Decide on a project.
• Pick a role:
− Product Owner
− Scrum Master
− Scrum Team
• Begin!

29. END