Overview Agile Methodologies. Umi Sa adah Desy Intan Permatasari EEPIS 2016

Ukuran: px

Mulai penontonan dengan halaman:

Download "Overview Agile Methodologies. Umi Sa adah Desy Intan Permatasari EEPIS 2016"

Budi Darmadi
7 tahun lalu
Tontonan:

1 Overview Agile Methodologies Umi Sa adah Desy Intan Permatasari EEPIS 2016

2 Agenda 1. Introductions 2. Agile Software Development 3. Scrum Walk Through 4. Benefits 5. Challenges 6. Next Steps 2

3 Agile Software Development 3

4 Agile Manifesto

5 Most Agile methodologies have similar concepts.

6 Iterative Development

7 Create Customer Class Add GetCustomer Service Method Refactor Customer List UI Working from Lists

8 Develop One Small Feature at a Time

9 Sustainable Pace

10 Lean Management Hierarchy

11 Collaborative, Self Organizing Teams

12 Production Ready Deliverables

13 Automated testing and builds (Continuous Integration)

14 Inspect and Adapt

15 Agile Methodologies

17 Agile Overview Agile projects succeed when the team gets the spirit of agility. Ron Jeffries (APM Group)

18 extreme Programming Overview 18

19 XP Values and Principles Communication Simplicity Feedback Courage Quality work

20 20

21 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

22 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

23 Scrum Overview 23

24 Scrum

25 Scrum Roles Scrum Team Scrum Master Carries water and moves boulders Product Owner Responsible for maintaining product backlog

26 Scrum Control Points Events: Sprint Planning Daily Scrum Sprint Review (retrospectives)

27 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

28 XP vs Scrum 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

29 Methodology Agile Method s Focus Project Management Engineering Scrum Crystal FDD XP Structure Unstructured Structured Crystal Scrum XP FDD

30 What is a kanban system?

31 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

32 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

33 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)

34 Signboard Limit Work-In-Progress Visualize the Work Kanban Measure & Manage Flow Visual Card Just-in-time (JIT)

35 Visualize the workflow Kanban (contd ) 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 Limit WIP (work in progress) 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

36 Kanban Board Illustration - I

37 Kanban Board Illustration - II

38 Kanban

39 39

40 Kanban vs Scrum Kanban 1. Complex systems or processes that require (not just follow) long lead times in weeks and months 2. Organizations that desire small, regular and incremental changes Scrum 1. Software development projects or programs that have changing requirements 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 and system 4. Similarity : Complex work needing multiple disciplines and skills 40

41 Why Scrum become the most popular? 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. 41

42 Why Scrum become the most popular? 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 42

43 Appropriate Practices What method to use? Don t use a screwdriver to drive a nail.

44 Which one? Kebanyakan kalau sudah mencoba proses Agile, justru tidak terlalu peduli dengan mana yang terbaik. Tim akan lebih fokus ke mencoba-coba terus praktek-praktek baru yang membuat lebih baik. Karena dalam Scrum ada kegiatan Scrum retrospektif. Kalau mencoba Agile pertama kali, kemungkinan lebih memilih Scrum karena pertimbangan hambatan yang lebih rendah 44

45 45

46 46

47 47

48 48

49 Questions? 49

50 THANK YOU

dokumen-dokumen yang mirip

Software Development Life Cycle (SDLC)

Software Development Life Cycle (SDLC) Budi Irawan facebook.com/deerawan @masbugan blog.budiirawan.com Kenapa butuh SDLC? 1 2 Software pun harus punya dan butuh siklus hidup SDLC 3 Apa itu SDLC? Siklus