Scrum Technology

DESKRIPSI Scrum merupakan framework untuk manajemen pengembangan software dengan karakteristik cekatan dan bersifat iteratif dan incremental. Scrum mendefinisikan dirinya fleksible, strategi pengembangan yang menyeluruh di mana seluruh team bekerja sebagai satu unit dalam mencapai sebuah gol yang sama. SCRUM adalah salah satu metode rekayasa perangkat lunak dengan menggunakan prinsip-prinsip pendekatan AGILE, yang bertumpu pada kekuatan kolaborasi tim, incremental product dan proses iterasi untuk mewujudkan hasil akhir. Prinsip kunci dari scrum adalah memahami bahwa dalam project yang tengah berlangsung, klien mungkin mengubah apa yang menjadi kebutuhan dan keinginannya. Perubahan sulit diadaptasi oleh framework pengembangan aplikasi yang bersifat tradisional. Scrum menerima perubahan ini dan memaksimalkan seluruh anggota team untuk menyesuaikan perubahan mendadak ini.   TUJUAN

1. Memahami konsep scrum untuk mengelola berbagai program dan proyek
2. Memahami prinsip pengembangan menggunakan Agile (Agile Development)
3. Memahami item-item yang ada pada scrum framework
4. Memahami requirement yang dibutuhkan dari proyek scrum
5. Memahami peran penting product backlog pada proyek pengembangan scrum
6. Mampu mengimplementasikan prinsip-prinsip scrum framework dalam proyek pengembangan yang ada

MATERI 1. Scrum Framework

• Scrum Roles
• Scrum Activities and Artifacts

2. Agile Principles

• Variability and Uncertainty
• Prediction and Adaptation
• Validated Learning
• Work In Process (WIP)
• Progress
• Performance

3. Sprints

• Timeboxed
• Short Duration
• Consistent Duration
• No Goal-Altering Changes
• Definition of Done

4. Requirements and User Stories

• Progressive Refinement
• What Are User Stories
• Level of Detail
• INVEST in Good Stories
• Nonfunctional Requirements
• Knowledge-Acquisition Stories
• Gathering Stories

5. Product Backlog

• Product Backlog Items
• Good Product Backlog Characteristics
• Grooming
• Flow Management
• Which and How Many Product Backlogs

6. Estimation and Velocity

• PBI Estimation Concepts
• PBI Estimation Units
• Planning Poker
• Understanding the Velocity
• Calculate a Velocity Range
• Forecasting Velocity
• Affecting Velocity
• Misusing Velocity

7. Technical Debt

• Consequences of Technical Debt
• Causes of Technical Debt
• Technical Debt Must Be Managed
• Managing the Accrual of Technical Debt
• Making Technical Debt Visible
• Servicing the Technical Debt

8. Product Owner

• Characteristics/Skills
• Product Owner Combined with Other Roles
• Product Owner Team

9. Scrum Master

• Characteristics/Skills
• Fulfilling the Role

10. Development Team

• Role-Specific Teams
• Characteristics/Skills

11. Scrum Team Structures

• Feature Teams versus Component Teams
• Multiple-Team Coordination

12. Managers

• Fashioning Teams
• Nurturing Teams
• Aligning and Adapting the Environment
• Managing Value-Creation Flow
• Project Managers

13. Scrum Planning Principles

• Don’t Assume We Can Get the Plans Right Up Front
• Up-Front Planning Should Be Helpful without Being Excessive
• Keep Planning Options Open Until the Last Responsible Moment
• Focus More on Adapting and Replanning Than on Conforming to a Plan
• Correctly Manage the Planning Inventory
• Favor Smaller and More Frequent Releases
• Plan to Learn Fast and Pivot When Necessary

14. Multilevel Planning 15. Portfolio Planning

• Scheduling Strategies
• Inflow Strategies
• Outflow Strategies
• In-Process Strategies

16. Envisioning (Product Planning)

• SR4U Example
• Visioning
• High-Level Product Backlog Creation
• Product Roadmap Definition
• Other Activities
• Economically Sensible Envisioning

17. Release Planning (Longer-Term Planning)

• Release Constraints
• Grooming the Product Backlog
• Refine Minimum Releasable Features (MRFs)
• Sprint Mapping (PBI Slotting)
• Fixed-Date Release Planning
• Fixed-Scope Release Planning
• Calculating Cost
• Communicating

18. Sprint Planning

• Approaches to Sprint Planning
• Determining Capacity
• Selecting Product Backlog Items
• Acquiring Confidence
• Refine the Sprint Goal
• Finalize the Commitment

19. Sprint Execution

• Sprint Execution Planning
• Flow Management
• Daily Scrum
• Communicating

20. Sprint Review

• Participants
• Prework
• Approach
• Sprint Review Issues

21. Sprint Retrospective

• Participants
• Prework
• Approach
• Follow Through
• Sprint Retrospective Issues

22. The Path Forward

• There Is No Definition of Done for a Scrum
• Discover Path
• Sharing Best Practices
• Using Scrum to Discover the Path Forward

PARTICIPANT IT Project Manager, IT Manager, System Analyst, Business Analyst, Programmer TRAINING METHOD Presentation Discussion Case Study Evaluation   FACILITY Training Kit Handout Certificate Lunch + 2x Coffee Break Souvenir Pick Up Participant (Yogyakarta)