SCRUM!

1. Scrum ! SCRUM! Scrum & the QA Danny (Danko) Kovatch Phone: +972-544-26.11.70 Email: Danko@AgileSparks.com Site: www.AgileSparks.com

2. Danny (Danko) Kovatch • Agile coach • and trainer • Certified Scrum Trainer • Founder of AgileSparks • International lecturer, trainer, assimilator & consultant • Head of the Israeli • Scrum user group "רק על עצמי לספר ידעתי, צר עולמי כעולם נמלה" -- רחל

3. Topics for today • The traditional “pains” • What is Agile • What is Scrum • Estimation, planning & visibility • Role of the QA in Scrum • Metrics and measurements • The challenge of the QA manager • Q&A Gaining knowledge how to assimilate Scrum Gaining a drill down visibility on Scrum Getting familiar with Agile WII.FM Learn how to present Scrum to your organization Learn new planning technique Key Performance Indicators Understand the mains problems Have fun

4. הגדרת אי שפיות “Insanity is doing the same thing over and over again and expecting different results.” Albert Einstein (1879-1955) What is the definition of insanity? “You won’t get anything unless you have the vision to imagine it” -- John Lennon

5. הבעיה הראשונית מלון הילטון, תל אביב "A journey of a thousand miles begins with a single step.“ -- Confucius

6. השפעת מידע לא רלוונטי מידע לא רלוונטי בניסוי של הערכת פרוייקט התגלו הממצאים הבאים: 20 שעות : קבוצה א' מסמך דרישות : 39 שעות אותו מסמך עם מידע לא רלוונטי קבוצה ב' Source: How to avoid impact from irrelevant and misleading information on your cost estimates, Magne Jørgensen and Stein Grimstad, Simula Research Laboratory,Simula Research Labs Estimation Seminar, Oslo, Norway 2006.

7. השפעת אורך מסמכי הדרישות כמות המידע בניסוי של בדיקת השפעת אורך מסמכי הדרישות על ההערכות עלו הממצאים הבאים: 117 שעות : קבוצה א' מסמך דרישות • רווחים כפולים בין שורות • שוליים רחבים יותר • פונטים גדולים יותר • יותר רווחים בין פסקאות : 173 שעות אותו מסמך דרישות (ארוך ב 7 עמודים) קבוצה ב' Source: How to avoid impact from irrelevant and misleading information on your cost estimates, Magne Jørgensen and Stein Grimstad, Simula Research Laboratory,Simula Research Labs Estimation Seminar, Oslo, Norway 2006.

8. דילמת השבויים הטיית מעריכים בניסוי של בדיקת השפעת הטיית הערכה עלו הממצאים הבאים: & 456 שעות קבוצת ביקורת מסמך דרישות • הערכת הלקוח היא 500 שעות • הלקוח לא מקצועי מספיק להעריך • יש להתעלם מהערכת הלקוח & 555 שעות הטייה גבוהה מסמך דרישות • הערכת הלקוח היא 50 שעות • הלקוח לא מקצועי מספיק להעריך • יש להתעלם מהערכת הלקוח 99 שעות & הטייה נמוכה מסמך דרישות Source: How to avoid impact from irrelevant and misleading information on your cost estimates, Magne Jørgensen and Stein Grimstad, Simula Research Laboratory,Simula Research Labs Estimation Seminar, Oslo, Norway 2006.

9. Traditional projects We will let you know Phone era Requirements Planning Development QA CA Release date: 30-Apr 2008 • Budget? • Credibility? • Documents? • Content? • Quality? Release date: 3-Apr 2008 !!!! Release date: 27-Jun 2008 Release date: 10-May 2008 "Traditionalists often study what is taught, not what there is to create" -- Ed Parker

10. ואיך מרגישים האנשים הרלוונטים? Customer: Requirements Planning Development QA CA QA Manager: כעס תדהמה הסכמה תיסכול היה אחלה, בוא ננסה עוד פעם! R&D Manager QA Manager "יש לך עוד, יש לך עוד, יש לך עוד...נו, תראה מה עשית!!!!"

11. Roles & Responsibilities QA Manager: A manager that needs to give the exact estimate for assuring the quality of the project suffer the postponements of the R&D manager but has the ability to release the product at the same deadline with the same quality while chasing the R&D manager for all changes that were not communicated R&D Manager: A manager that needs to give the exact estimate for developing the project While anticipating all impediments and future change requests Remember to update every relevant party and develop it according to the original estimate “The price of greatness is responsibility” -- Sir Winston Churchill

12. אז מה עושים?!?!?!?!?!?!?!?! "Someone doing it often interrupts the person saying it cannot be done." -- Unknown

13. Individuals and interactions Working software Responding to change Customer collaboration Following a plan Comprehensive documentation Contract negotiation Process and tools over over over over 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: While there is value in the terms on the right, we value the items on the left more )http://www.agilemanifesto.org) What is Agile? Perfect is the enemy of the good -- Voltaire

14. Topics of today What is Scrum? “SCRUM is a simple framework used to organize Teams, get work done more productively with higher quality, lot of team cohesion and commitment of the team.”

15. Topics of today What is Scrum? “SCRUM is a simple framework used to organize Teams, get work done more productively with higher quality, lot of team cohesion and commitment of the team.” • Changes will happen • Team estimates • Trust • Overall commitment • Visibility (Content & Progress) • Transparency • Frequent feedbacks • Inability to give accurate estimates • Fun!

16. Release Together from the beginning! Development (QA & Code) Hardening • Collection of sprints • Represents the entire products • Release is not a Gantt but only a rough uncommitted estimate • Commitment on the next immediate Sprint only

17. Commitment “While you are about to commit only to the iteration, …” “…it is imprudent to ignore the whole plan” “I've been on a diet for two weeks and all I've lost is two weeks” -- Totie Fields

18. 3 Sprint life cycle A time-boxed period of time during which the Team works to turn the Product Backlog items it has selected into an increment of potentially shippable product functionality Self management team! 15 minutes daily Stand up meetings Sun Mon Tue Wed Thu Sun Mon Tue Wed Thu Sun Mon Tue Wed Thu “Yesterday…” I was late again 15 days “Today…” Sprint #4: Review meeting Retrospective meeting Sprint #5: Planning session Artifacts decision Sprint #3: Review meeting Retrospective meeting Sprint #4: Planning session Artifacts decision “Impediment…”

19. Fully assimilated Scrum company Tester & coders are fully integrated! Each sprint there is an handover Each night there is a build This slide is courtesy of Henrik Kniberg

20. Review “Show me the money!” • Time boxed (up to 1 hour max!) • Team demonstrates product increment • No PowerPoint please!!!!

21. Retrospective • Main challenge: Doing it • Doing it only at the end – Better not doing it at all • Remember only the last things • The “Bad” things • Forgetting the good things • Not implementing them • Do it every Sprint! • Immediate implementation

22. דילמת השבויים הבדיקה תיקח 5 ימים! בטח בוס! שוב לא נעמוד בזמני הפרוייקט • הגורו הטכנולוגי • איש הצוות האסרטיבי • המנהל "המנהל לא תמיד צודק, אבל הוא תמיד המנהל"

23. (Planning Pokerהפתרון: קלפי הערכת משימות ( • Every team member knows about the committed tasks • Overall understanding • Team spirit • Overlapping • Small tasks • Risk reduction • Real estimate ניטרול דילמת השבויים! בוטל "The path to greatness is along with others.“ -- Baltasar Gracian

24. Planning – Just before committing… TMQ / Premortum

25. Create test script 5 Danko Visibility Charts – Task Board Content Visibility! R&D R&D QA Coding Code Review Approval • Each sticky note is a task • Each task is up to 3 days • Tasks are being moved by the team Extra Task! • The team is familiar with all the tasks • No surprises

26. Remaining work Create test script 3 Create HTML 2 Create HTML 5 Create HTML 1 Committed tasks Team 4 Team 2 Team 1 Team 3 Visibility Charts – Burn Down Chart Progress Visibility! 11 days 4 tasks

27. Life cycle of a task Task Success Criteria Coder’s mind set: Construction Tester’s mind set: Destruction “You always pass failure on the way to success” -- Mickey Rooney

28. QA in Scrum Role of the QA • Getting potential shippable product every sprint • Part of the Delivery team • Estimate the tasks together with the R&D • Approve the tasks • Gaining full visibility on the build & product • QA is part of the definition “what is done” Who is he kidding? We’re ready to go! "If a man does his best, what else is there?" -- George Patton www.danko.org.il

29. What is DONE? Launch First Customer Launch Pilot Production Implementation User Acceptance Performance Testing System Testing Unit Testing Coding Design Analysis Planning

30. KPI – How SCRUM are we • Start with the original KPIs • Focus on your weakness • Measure it every sprint • Communicate it to the team • Consider adding: • Team Collaboration (QA & R&D) • Accomplishment (Is it really done) • Technical debts (How fast are we closing gaps) • How accurate are the estimates

31. Scrum is being used for… Commercial software In-house development Contract development Fixed-price projects Financial applications ISO 9001-certified applications Embedded systems 24x7 systems with 99.999% uptime requirements the Joint Strike Fighter Video game development Satellite-control software Websites ISV applications Network switching applications Mobile phones

32. Who is using Scrum CitrixOnline Salesforce.com Ipswitch John Deere Google Capital one Time Warner Siemens Intuit Philips Sanrad Lexis Nexis Nokia Bank of America Microsoft British telecom Lockheed Martin Polycom First American Real Estate Nielsen Media Adelaide Bank High Moon Studios BBC Sabre Oce Yahoo Capital One High Moon Studios Electronic Arts Adobe Systems BMC Software

33. לינקים... www.scrumalliance.org www.planningpoker.com www.controlchaos.com www.implementingscrum.com www.mountaingoatsoftware.com www.agilemanifesto.org/principles.html www.scrum-master.com/ http://scrumforteamsystem.com www.winnowmanagement.com/ http://scrumoogle.com/ "Outside of a dog, a book is a man's best friend. Inside of a dog, it is too dark to read."  --  Groucho Marx

34. אין פתרונות קסם! אבל יש פתרונות יצירתיים שממזערים את הנזק! • הבנה ששינויים רצויים, דרושים ותמיד יקרו • חלוקה לאיטרציות קטנות (שבועות ספורים) • הימנעות מדילמת השבויים • חלוקה למשימות קטנות (ימים ספורים) • המבצעים מעריכים • צוותים עצמאיים, מגובשים ומכווני משימות • האחריות עוברת לצוות • נראות מקסימלית "It is only by doing things others have not that one can advance." -- George Patton

35. Waterfall….? While the waterfall approach can be perfect for some things in life…. The waterfall guy

36. I highly recommend usingScrumfor your Project management It’s fun! It’s efficient! It works!!

37. The end for one is the beginning for another… Thank you! (וזמן לשאלות נשאר לנו?)