1. Agile development
We-BBT Event
31 March 2010
People boosting your business
© iLean

2. Our goal
research
General introduction to Agile development
Scrum & eXtreme Programming
Q&A
© iLean

3. Lean principles
Reduce cycle time
Build quality in
Eliminate waste
Respect people
© iLean

4. Agile values
individuals and interactions
over processes and tools
working software
over comprehensive documentation
customer collaboration
over contract negotiation
responding to change
over following a plan
© iLean

5. Agile methods & processes
Prince2
PMBOK
LAD
Agile Scrum
Kanban
Lean RUP
DSDM
eXtreme
Programming
© iLean

6. Agile is a tool
© iLean

7. Why agile?
working software better ROI
flexibility understand your business
motivated people continuous improvement
© iLean

8. Iterative and incremental
!! Break down product
BUSINESS VALUE
!! Plan according business value
!! Deliver regularly
© iLean

9. Manage goals
detail requirements at the last responsible moment
© iLean

10. Collaborate
daily and with all involved parties
© iLean

11. Develop and test
build quality in
© iLean

12. engineering practices!
pair programming! coding standards!
unit testing! team charter!
continuous integration! definition of done!
test driven development! code reviews!
refactoring! test coverage!
© iLean

13. Develop and test
build quality in
© iLean

14. Integrate and release
as early and often as possible
© iLean

15. Continuous improvement
is a daily routine
© iLean

16. To deliver incrementally and iteratively:
!! Manage requirements
!! Collaborate
!! Develop and test
!! Integrate and release
!! Continuous improvement
© iLean

17. Agile methods & processes
Scrum
© iLean

18. Deming quality cycle
© iLean

19. Scrum History
1986 study by Takeuchi and Nonaka,
published in the Harvard Business Review
1993 Jef Sutherland:
first Scrum at Easel 2003 Lean Software Development
by Mary & Tom Poppendieck
1995 Ken Schwaber:
First white paper on Scrum
2008
1996 Kent Beck: XP
2001 Agile Manifesto
© iLean

20. The Scrum Process
© iLean

21. Scrum Product Owner
•! defines product, releases, ROI, ...
•! represents customer and users for the team
•! manages the Product Backlog
•! accepts work
BUT also
•! respects team estimates
•! respects sprint planning
© iLean

22. Product Backlog
nr! prio! user story! inschatting!
1! 970! Als gebruiker kan ik onder mijn naam veilig inloggen! 2!
2! 960! Als gebruiker kan ik volledig manueel alle gegevens voor nieuwe client invoeren. Dit zijn de identificatiegegevens van de persoon. ! 2!
Als gebruiker kan ik een aanvraag invoeren, wat will zeggen dat ik kan invullen welke attesten bij de aanvraag zitten en dat ik kan aangeven dat er nog een
3! 950! 3!
indicatiestelling moet gebeuren. (Na invoeren van de gegevens kan ik de aanvraag opslagen met status 'in behandeling'.)!
Als gebruiker kan ik een aanvraag goedkeuren. Het systeem checkt dan de nodige gegevens en berekent dan start- en einddatum van de tenlastenneming en
6! 900! 5!
toont alles aan mij ter bevestiging (ik kan de beslissing van systeem overrulen en daarvooreen reden/motivatie ingeven).!
9! 800! als gebruiker kan ik betalingen genereren voor een bepaald type dossier voor een bepaalde maand (door op 1 knop te klikken).! 3!
als gebruiker kan ik uit de lijst van betalingen een betalingsbestand genereren en downloaden. Het systeem zet tegelijkertijd de status van de betaling op
10! 780! 3!
'uitbetaald' !
32! 500! Als gebruiker kan ik een rapporteringsbestand genereren. ! 3!
Als gebruiker kan ik een aanvraag en (eventueel bijhorende) tenlasteneming opzoeken op basis van een Rijksregisternummer. Het systeem toont de
4! 940! 3!
identificatiegegevens, de aanvraag en de tenlasteneming samen op één scherm.!
Als gebruiker kan ik een aanvraag wijzigen (velden verder invullen of wijzigen, attesten toevoegen of verwijderen, enz) en achteraf de aanvraag terug opslaan als
5! 920! 3!
'in behandeling'.!
© iLean

23. Product Backlog
•! The business objectives
•! All desired work
•! Every item must be valuable
•! Prioritized by the product owner
•! ‘Living’ document
© iLean

24. The Scrum Process
© iLean

25. Sprint planning
•! PO + Team
•! Team takes commitment
•! Team prepares sprint
!! Break down work
!! Discuss and design
!! …
© iLean

26. The Scrum Process
© iLean

27. Scrum Team
•! cross-functional
•! self-organizing and empowered
•! typically 5-9 people
BUT also
•! respects Product Owner prio’s
•! respects Scrum values and process
© iLean

28. Direct and control
© iLean

29. Self organizing
servant leader!
coach!
© iLean

30. The Scrum Process
© iLean

31. Sprint Demo
© iLean

32. Sprint Retrospective
© iLean

33. Sprint review (demo + retrospective)
•! Results:
–! Updates to the backlog (scope)
–! Update of the team agreements (charter)
–! Specific actions (owner + deadline)
© iLean

34. The Scrum Process
© iLean

35. Sprint Backlog & Commitment
...
© iLean

36. Burn Down Charts
© iLean

37. Scrum Board
© iLean

38. Daily Scrum meeting
© iLean

39. The Scrum Process
© iLean

40. Scrum Master
•! guards the Scrum process and the
improvement cycle
•! removes impediments
•! motivates and coaches the team
•! facilitates collaboration
BUT also
•! respects team decisions
© iLean

41. The Scrum Process
© iLean

42. The Scrum Process
© iLean

43. User Stories
•! User Story = description of an objective
As as user I can do something
to achieve a goal.
•! Add examples/scenarios/what NOT to do
© iLean

44. Daily Scrum meeting
•! What did I do yesterday?
•! What will I do today?
•! What’s bothering or blocking me?
!! SM facilitates
!! Time boxed! No side-discussions.
!! By and for the team
© iLean

45. Scrum
Toolbox Philosophy
roles courage
openness
artifacts
focus
ceremonies
respect
practices
commitment
© iLean

46. Agile methods & processes
eXtreme
Programming
© iLean

47. Extreme Programming (XP)
© iLean

48. Test Driven Development
~unit tests
•! use short development iterations based on
pre-written test cases that define desired
improvements.
© iLean

49. Refactor Mercilesly
XP Practices
•! Don’t leave duplicate or uncommunicative
code around
© iLean

50. Code and design simply
XP Practices
•! Objective
take a "simple is best" approach to software design.
•! Practical
After every new piece of code: 'is there a simpler
way to introduce the same functionality?‘
•! Refactoring
© iLean

51. Collective Code Ownership
•! everyone is responsible
for all the code
•! this, in turn, means that everybody is
allowed to change any part of the code
•! if you run across some code that could be
improved, you have to stop and improve it
© iLean

52. Coding Standards
developing is a team game
Examples
•! choose same style of class & variable names
•! format code the same way
© iLean

53. Continuous Integration
•! The development team
should always be working on
the latest version of the software
•! Often combined with a regular (automated)
build process & automated testing.
© iLean

54. Sustainable Pace
•! Every day
–! starts at start time
–! ends at end time
•! need for regular overtime is a clear signal
that something else is wrong with the
project.
•! better awareness, better refactoring, simpler
code
© iLean

55. Pair Programming
•! two programmers work together at one
workstation.
> Driver + Observer/navigator
© iLean

56. Extreme Programming (XP)
© iLean

57. Lean principles
Reduce cycle time
Build quality in
Eliminate waste
Respect people
© iLean

58. Agile values
individuals and interactions
over processes and tools
working software
over comprehensive documentation
customer collaboration
over contract negotiation
responding to change
over following a plan
© iLean

59. Why Agile?
•! Respond to change
•! Deliver quality software
•! Boost people
•! Deliver more business value
•! Increase creativity
•! Have a working solution at all times
•! …
© iLean

60. What’s next?
People boosting your business
© iLean

61. Implement Agile values and
principles…
in your specific context!
© iLean

62. Implement Agile
Reduce cycle time
•! Break scope into valuable increments
•! Deliver often
© iLean

63. Implement Agile
Adapt to changes
•! Get feedback from iteration deliverables
•! Think and act “Just In Time”
•! Collaborate with all involved parties
© iLean

64. Implement Agile
Eliminate waste
•! Reflect regularly on process and
collaboration
•! Reduce ‘stock’
•! Limit work in progres
© iLean

65. Implement Agile
Continuously improve
•! Inspect and adapt
© iLean

66. References
Scrum in five minutes
http://www.softhouse.se/Uploades/Scrum_eng_webb.pdf
Scrum Alliance
http://www.scrumalliance.org/
Agile Software development
with Scrum
Scrum and XP from the Trenches By Ken Schwaber
http://www.crisp.se/henrik.kniberg/ScrumAndXpFromTheTrenches.pdf
Scrum articles directory
http://www.softdevarticles.com/modules/weblinks/viewcat.php?cid=46
Agile Alliance's Scrum library User Stories Applied
http://www.agilealliance.org/article/articles_by_category/17
By Mike Cohn
InfoQ.com / Agile
http://www.infoq.com/Agile
Agilo for Scrum
http://www.agile42.com/cms/pages/download/ Agile Estimating
And Planning
The New New Product Development Game By Mike Cohn
http://apln-richmond.pbwiki.com/f/New%20New%20Prod%20Devel%20Game.pdf
Jeff Sutherland, Agile development: lessons learned from the first
Scrum, 2004
http://jeffsutherland.com/scrum/FirstScrum2004.pdf
© iLean

67. Questions?
People boosting your business
© iLean

68. Thank you!
Feel free to contact me!
Jef Cumps
jef@ilean.be
People boosting your business
© iLean