Highlight the importance of DONE in Agile methods (scrum, lean, kanban, XP) using theory from other body of knowledge (risk management, finance, management, etc.)

1. The DONE Concept
In Agile and
out there

2. Agenda

3. Done In Agile

4. DONE in Scrum
Definition of Done (DoD)
§Transparency
§Quality oriented
§Ready for release

5. Extreme Programming

6. Lean

7. Kanban

8. The truth is out there

9. Risk management
Risk
Done
Time /Effort

10. Done & Finance

11. Finance – Snowball Method
Not Done item is like a debt

Use « Debt-snowball » method

12. Finance - ROI
Scoping : Good
ideas but high costs
Before Release:
Quick win

13. Finance - ROI
Past is already over!

14. Tool : refresh youR ROI
Item close to DONE
have HIGH ROI

15. Tool : refresh youR ROI
ROI = (Revenue – Cost ) / Cost

16. Tool : refresh youR ROI
ROI = (Revenue – Cost ) / Cost

17. Done & ManagEment

18. ManagEment By Objectives
Benefits
§ Coordination
§ Motivation & commitment
§ Transparency
§

19. Tool : Radiator

20. Management By Objectives
Benefits
§ Coordination
§ Motivation & commitment
§ Transparency
§
Limits
§ Goals before people
§ Incomplete
§ Not easy to formalize

21. Tools – Preparation meeting

22. Situational leadership
Delegation : Tell « What », not « How »
§ Define « DONE »
§ Control

23. Tool : Team Control

24. The good old process

25. Old school Methodo
Done defined by list of Delivrables and
Templates

26. Tools - Checklist

27. Old school Methodo : drawback
Too many things useless
Too general

28. Tool : Rétrospective
Possible result of a retrospective
⇒ Update Definition of Done

29. Pareto
20% of effort
80% of Results
20% Done
20% of Features
100% Done

30. Conclusion

31. Questions / Contact



gilles.scokar t@oniryx.be
https://www.linkedin.com/in/gscokar t