Scrum is an agile framework for completing complex projects. It focuses on delivering the highest business value in the shortest time. The document discusses the history and principles of Scrum, including its three core values: transparency, adaptation, and inspection. It describes the three roles in Scrum - Product Owner, Scrum Master, and Scrum Team. The Scrum process includes sprints, daily stand-up meetings, sprint reviews, and retrospectives. The key artifacts are the product backlog, sprint backlog, and burn-down charts. Common challenges to Scrum adoption are also reviewed.

1. Scrum Transforming the world of work Duong Trong Tan (CSM) Hanoi, Mar. 2011

2. Agenda On chaos and effectiveness What is Scrum? Three Core Values Three Roles of Scrum Operate Scrum Joining Scrum Users Community 2

3. Chaos and effectiveness In chaos, people still walk effectively Photo: VnExpress.net 3

4. Scrum history Jeff Sutherland Initial scrums at Easel Corp in 1993 IDX and 500+ people doing Scrum Ken Schwaber ADM Scrum presented at OOPSLA 96 with Sutherland Author of three books on Scrum Agile Alliance 2001 Scrum Alliance in 2002 4

5. What is Scrum? Scrum Is an Innovative Approach to Getting Work Done Scrum is an agile framework for completing complex projects. It focuses on delivering the highest business value in the shortest time. Scrum is based on agile software development principles and values Teams in Scrum are self-managed 5

6. Who use Scrum? 6

7. Scrum Framework 7

8. 3 Core Values Transparency Adapt Inspect 8 Dùainóingảnóinghiêng Lòngtavẫnvữngnhưkiềngbachân

9. The Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan 9 That is, while there is value in the items on the right, we value the items on the left more. AgileAlliance.org

10. 3 Roles Product Owner responsible for the business value of the project ScrumMaster ensures that the team is functional and productive Scrum Team self-organizes to get the work done 10

11. Scrum Process Overview Image: ScrumAlliance.org 11

12. Deemer el al. 12

13. 4 Ceremonies Sprint Planning the team meets with the product owner to choose a set of work to deliver during a sprint Daily Scrum the team meets each day to share struggles and progress Sprint Reviews the team demonstrates to the product owner what it has completed during the sprint Sprint Retrospectives the team looks for ways to improve the product and the process. 13

14. Activity: Daily Meeting Photo: http://rosamundwo.com/wp-content/uploads/2010/05/Standup-meeting.jpg 14

15. 3 Artifacts Product backlog prioritized list of desired project outcomes/features Sprint backlog set of work from the product backlog that the team agrees to complete in a sprint, broken into tasks Burndownchart at-a-glance look at the work remaining (can have two charts: one for the sprint and one for the overall project) 15

16. Product Backlog Requirements Items valued to users & customers Prioritized and maintained by the Product Owner 16

17. Estimation in Scrum 17

18. Sprint Backlog Plan and tracking tool for a sprint Maintained by the team 18

19. Burndown Chart 19

20. Scrum Obstacle According to Bas Vodde: The illusion of command and control The persistence of status-quo The mediocracy of ScrumBut The belief in magic The era of opacity The tyranny of the waterfall. 20

21. Causes of failure Ineffective use of retrospective Inability in getting all people in planning meeting Failure to pay attention to the infrastructure required Bad ScrumMaster Product Owner is consistently unavailable Failure to push testing forward Reverting to form Obtaining only "checkbook commitment" from executive management Teams lacking authority and decision making ability Not having onsite evangelist for remote location Cultures that do not support learning Denial is embraced instead of brutal truth Jean Tabaka 21

22. Scrum Community Global community: www.scrumalliance.org Ho Chi Minh City: www.agilevietnam.org Ha Noi City: Gathering Soon… 22

23. References and Resources Jean Tabaka, Twelve ways agile adoption failed, Better Software, Nov. 2007, www.stikymind.com (http://www.nxtbook.com/nxtbooks/sqe/bettersoftware1107/) Mountain Goats, Scrum Overview, (http://www.mountaingoatsoftware.com/scrum/overview) MoutainGoats, Planning Poker Estimating in details (http://store.mountaingoatsoftware.com/pages/planning-poker-in-detail) Scrum Alliance , http://www.scrumalliance.org/blog/129-pmi-develops-agile-certification Scrum Alliance, What is Scrum? (http://www.scrumalliance.org/pages/what_is_scrum) Pete Deemer, Gabrielle Benefield, Craig Larman & Bas Vodde, Scrum Primer ver. 1.2 Tan, practices-of-agile-developers (PPT slide: http://www.slideshare.net/duongtrongtan/practices-of-agile-developers ) 23

24. Books 24