1. Dwika Sudrajat
Presented by
Defense and Military Strategy with
Agile - Scrum
VIDE Freeman Enterprise Inc.
California Branch - Thursday, May 25, 2023

4. Agile Project Management using
Scrum Framework

5. Agile Project Management
using Scrum Framework

8. The Daily Scrum
• Parameters
• Daily
• 15-minutes
• Stand-up
• Not for problem solving
• Whole world is invited
• Only Team Members,
Scrum Master,
Product Owner, can
talk
• Helps avoid other
unnecessary meetings

11. Defense Build by Scrum
•

13. Scalability of Scrum

16. Agile Approach

17. Traditional Approach
(Waterfall)

21. Incremental vs Iterative

22. Iteration

24. Risk Management

25. Waterfall and Agile
• Give me all
requirements,
otherwise it will
cost you!
25

26. Waterfall vs Agile

27. Risk Management

29. PM Framework to Scrum Framework
Image source:
http://uk.eurosport.yahoo.com/02092007/8/photo/general-shot-4x400m-relay-race.html
http://www.sports-corporate.co.uk/uploads/sports_pics/rugby.jpg

30. Traditional vs Agile

31. Risk
www.scrumtrain.com 31
Define Design Develop
Sign-off Deploy
Sign-off Sign-off
Suprise!
Waterfall
False security Uncertainty
More uncertainty
Prioriterer
kravene –
designe,
utvikle, test
Prioriterer
kravene –
designe,
utvikle, test
Prioriterer
kravene –
designe,
utvikle, test
Feedback
Prioriterer
kravene –
designe,
utvikle, test
Feedback Feedback

Agile
Timeboxed
Uncertainty Safe
Safer
Risk Management

32. Digital Age

33. Thank You

34. Thank You

35. Thank You

36. Backup Slide

37. Agile selain Scrum
• 1. Kanban: fokus pada
pengoptimalan proses
produksi dan
meningkatkan
efisiensi.
• 2. Lean: fokus
penghapusan
pemborosan dan
penerapan prinsip-
prinsip manufaktur
lean.
• 3. Extreme
Programming (XP):
• 4. Crystal: fleksibel:
skala, kritisitas, dan
kompleksitas proyek
• 5. Dynamic Systems
Development Method
(DSDM): fokus
kolaborasi tim dan
pengiriman cepat
kualitas tinggi.

40. Sprints

41. Sprints
• Scrum Projects make progress in a series of “Sprints”
• Typical duration is 2–4 weeks or a calendar month at
most
• Product is designed, coded, and tested during the sprint

42. The Sprint Review
• Team presents what it accomplished
during the sprint
• Typically takes the form of a demo of new
features or underlying architecture
• Informal
• 2-hour prep time rule
• No slides
• Whole team participates
• Invite the world

44. Sample Product Backlog

45. Sample Sprint Backlog

46. Sprint Burndown Chart
Progress
752 762
664
619
304
264
180
104
20
0
100
200
300
400
500
600
700
800
900
5
/
3
/
2
0
0
2
5
/
5
/
2
0
0
2
5
/
7
/
2
0
0
2
5
/
9
/
2
0
0
2
5
/
1
1
/
2
0
0
2
5
/
1
3
/
2
0
0
2
5
/
1
5
/
2
0
0
2
5
/
1
7
/
2
0
0
2
5
/
1
9
/
2
0
0
2
5
/
2
1
/
2
0
0
2
5
/
2
3
/
2
0
0
2
5
/
2
5
/
2
0
0
2
5
/
2
7
/
2
0
0
2
5
/
2
9
/
2
0
0
2
5
/
3
1
/
2
0
0
2
Date
Remaining
Effort
in
Hours

47. Scalability of Scrum