overview agile methodologies · 2020. 5. 7. · desy intan permatasari eepis 2016. agenda 1....
TRANSCRIPT
Overview Agile Methodologies
Umi Sa’adah
Desy Intan Permatasari
EEPIS 2016
Agenda
1. Introductions
2. Agile Software Development
3. Scrum Walk Through
4. Benefits
5. Challenges
6. Next Steps
2
Agile Software Development
3
Agile Manifesto
Most Agilemethodologies have
similar concepts.
Iterative Development
Working from Lists
Create Customer Class
Add GetCustomerService Method
Refactor Customer List UI
Develop One Small Feature at a Time
Sustainable Pace
LeanManagement
Hierarchy
Collaborative, Self Organizing Teams
Production Ready Deliverables
Automatedtesting and builds
(Continuous Integration)
Inspectand
Adapt
Agile “Methodologies”
Agile Overview
“Agile projects succeed when the team gets the spirit of agility.”
– Ron Jeffries (APM Group)
eXtreme Programming Overview
18
XP Values and Principles
• Communication
• Simplicity
• Feedback
• Courage
• Quality work
20
XP Practices
• The planning game
• Small releases
• Metaphor
• Simple design
• Refactoring
• Testing
• Pair programming
• Collective Ownership
• Continuous Integration
• Sustainable Pace
• On Site Customer
• Coding Standards
XP Roles
• The Customer
Sets project goals and makes business decisions
• The Developer
Turn customer stories into working code
• The Tracker
Keeps track of any metrics used by team
• The Coach
Guides and mentors the team
Scrum Overview
23
Scrum
Scrum Roles
• Scrum Team
• Scrum Master
• Carries water and moves boulders
• Product Owner
• Responsible for maintaining product backlog
Scrum Control Points
Events:
• Sprint Planning
• Daily Scrum
• Sprint Review(retrospectives)
XP vs Scrum
1. Scrum teams typically work in iterations (called sprints) that are from two weeks to one month long. XP teams typically work in iterations that are one or two weeks long.
2. Scrum teams do not allow changes into their sprints. Once the sprint planning meeting is completed and a commitment made to delivering a set of product backlog items, that set of items remains unchanged through the end of the sprint. XP teams are much more amenable to change within their iterations. As long as the team hasn’t started work on a particular feature, a new feature of equivalent size can be swapped into the XP team’s iteration in exchange for the unstarted feature.
27
3. XP teams work in a strict priority order. Features to be developed are prioritized by the customer (Scrum’s Product Owner) and the team is required to work on them in that order. By contrast, the Scrum product owner prioritizes the product backlog but the team determines the sequence in which they will develop the backlog items.
4. Scrum doesn’t prescribe any engineering practices; XP does.
28
XP vs Scrum
Agile Method’s Focus
Scrum FDD XPCrystal
Project Management Engineering
Scrum FDDXPCrystal
StructuredUnstructured
Structure
Methodology
What is a kanban system?
Kanban
• Improves the throughput and reduces cycle times
• Delivers iterationless development
• Kanban limits create a pull system
• White board provides visualization of flow through to delivery
Kanban
• Kanban is made up of Three Foundational Principles:
• Start with what you do now
• Agree to pursue incremental, evolutionary change
• Respect the current process, roles, responsibilities & titles
Kanban
• Five Core Properties in Kanban :
• Visualize the workflow
• Limit W.I.P. (work in process)
• Manage Flow
• Make Process Policies Explicit
• Improve Collaboratively (using models & the scientific method)
KanbanJust-in-time (JIT)
Visualize the Work
Measure & Manage FlowSignboard
Limit Work-In-Progress
Visual Card
Kanban (contd…)
Visualize the workflow
Limit WIP (work in progress)
Split the work into pieces, write each item on a card and put on the wall
Use named columns to illustrate where each item is in the workflow
Assign explicit limits to how many items may be in progress at each stage
Measure the lead time (average time to complete one item,
sometimes called “cycle time”)
Optimize the process to make lead time as small and predictable as possible
Kanban Board Illustration - I
Kanban Board Illustration - II
Kanban
39
Kanban vs Scrum
40
Kanban Scrum
1. Complex systems or processes that require (not just follow) long lead times in weeks and months
1. Software development projects or programs that have changing requirements
2. Organizations that desire small, regular and incremental changes
2. Organizations that need to make a more intense or dramatic change in their culture
3. Longer periods of time 3. Not longer periods of time
4. Similarity : Complex work andsystem
4. Similarity : Complex work needing multiple disciplines and skills
Why Scrumbecome the most popular?
41
1) Scrum tidak ada aturan-aturan teknis, sehingga
hambatan untuk mencoba di awal lebih rendah
2) Scrum merupakan metode yang paling sedikit
menerapkan framework agile
3) Scrum punya asosiasi trainer dan sertifikasi dari awal
tahun 2000an. Sehingga lebih terorganisasi secara
pergerakan.
Why Scrumbecome the most popular?
42
4) Scrum punya guide resmi yang ringkas, hanya belasan
halaman. Sedangkan XP ketika dirilis tahun 1999,
penjelasan resminya dalam bentuk buku.
5) Scrum sesuai untuk software development project yang
sering mengalami perubahan requirement
6) Scrum banyak digunakan oleh perusahaan yang me
Appropriate Practices
What method to use?
Don’t use a screwdriver
to drive a nail.
Which one?
• Kebanyakan kalau sudah mencoba proses Agile, justru tidak terlalu peduli dengan mana yang terbaik.
• Tim akan lebih fokus ke mencoba-coba teruspraktek-praktek baru yang membuat lebih baik. Karena dalam Scrum ada kegiatan Scrum retrospektif.
• Kalau mencoba Agile pertama kali, kemungkinanlebih memilih Scrum karena pertimbangan hambatanyang lebih rendah
44
45
46
47
48
Questions?
49
THANK YOU