Presentation given at goudengids.be on May 13, 2014 to kick off the implementation of Scrum in all the delivery teams

1. WHY WE DOAGILE

2. 1. OUR REALITY
2. AGILE AND AGILE
HABITS
3. SCRUM

3. OUR DAY-TO-DAY REALITY

4. WE FACE A LOT OF CHANGES
REQUIREMENTS
NEEDS
PRIORITIES
TECHNOLOGY
FASHION

5. THREE THINGS WE WISHED TO BE TRUE
CUSTOMERS KNOW WHAT
THEY WANTS
DEVELOPERS KNOW HOW
TO BUILD IT
NOTHING CHANGES ALONG
THE WAY

6. THREE THINGS WE HAVE TO LIVE WITH
CUSTOMERS DISCOVER WHAT
THEY WANTS
DEVELOPERS DISCOVER HOW TO
BUILD IT
A LOT CHANGES ALONG THE WAY

7. TRADITIONAL APPROACHES DONOT WORK

8. THE WATERFALL MODEL

9. COSTOF CHANGE IN TRADITIONAL
APPROACHES

10. WHERE TRADITIONAL METHODS
SPEND EFFORT

11. TRADITIONAL APPROACHES ASK THE
WRONG QUESTIONS

12. TRADITIONAL APPROACHES PUT ALL
RISKS AT THE END

13. TRADITIONAL APPROACHES FAIL
MORE OFTEN

14. TRADITIONAL APPROACHES LEAD TO
BAD QUALITY

15. TRADITIONAL APPROACHES LEAD TO
SMALLER ROI

16. THEN, HOW CAN WE BE SUCCESFUL?

17. 1
SUPPORTFROM
EXECUTIVE
MANAGEMENT

18. 2
INVOLVE USERS

19. 3
OPTIMIZE PROJECTS

20. 4
SKILLED RESOURCES

21. 5
PROJECT MANAGEMENT
EXPERTISE

22. 6
USE AGILE PROCESSES

23. SO,AGILE IS THE SOLUTION ?

24. AGILE IS
Agileisthechoicetoworkwith
simple,iterativeprocesses, that
emphasizecreativityand
collaboration

25. AGILE IS
Agileischangingyourhabitsand
yourstate-of-mind

26. THE AGILE MIND-SHIFT

28. INDIVIDUALSAND INTERACTION
OVER PROCESSEN EN TOOLS

29. WORKINGSOFTWARE
OVER COMPREHENSIVEDOCUMENTATION

30. CUSTOMER COLLABORATION
OVER CONTRACT NEGOTIATIONS

31. RESPONDINGTO CHANGE
OVER FOLLOWINGA PLAN

33. THE 12 AGILE HABITS

34. 1
SATISFYTHE CUSTOMER

35. 2
COMMUNICATE FACE-
TO-FACE

36. 3
WELCOME CHANGE

37. 4
DELIVER FREQUENTLY

38. 5
WORK AS A TEAM

39. 6
MOTIVATEEACH OTHER

40. 7
MAINTAINA STEADY
PACE

41. 8
EXCEL IN QUALITY

42. 9
KEEP IT SIMPLE

43. 10
EVOLVE DESIGN

44. 11
REFLECT OFTEN

45. 12
MEASURERESULTS WITH
WORKING PRODUCTS

46. HOW SCRUM WORKS

47. SCRUM IS A PROJECT MANAGEMENT
FRAMEWORK
NOT A METHODOLOGY

48. TEAMAS A UNIT

49. SELF-ORGANIZED TEAMS

50. BUSINESSSETS PRIORITIES

51. AND ACCEPTS RESULTS

52. EVERYONE CAN SEE REAL WORKING
PRODUCTS

53. PIGS AND CHICKENS

54. THE SCRUM FRAMEWORK
4 ROLES
4 CEREMONIES
4 ARTIFACTS

55. SCRUM
ROLES
picture by exfordy

56. THE TEAM

57. THE TEAM
 Definetasks
 Estimateeffort
 Develop product
 Ensurequality
 Evolve process

58. SCRUM MASTER

59.  Remove impediments
 Prevent interruptions
 Facilitatethe team
 Support theprocess
 Managemanagement
SCRUM MASTER

60. PRODUCT OWNER

61. PRODUCT OWNER
 Definefeatures(accordingto vision)
 Prioritize features(according toROI)
 Pickrelease dates
 Give feedback
 Managestakeholders
 Accept or reject results

62. STAKEHOLDERS

63.  Interestedin the outcome
 Add itemsto the backlog
(throughproductowner)
 Everyone that’s not‘on the
team’
 Contributeto the project
(throughproductownerandsprintplanning
activities)
STAKEHOLDERS

64. SCRUM
CERE-
MONIES

65. SPRINTPLANNING

66. and
product owner The teamsetsthe sprint goal
 Selectssprint backlog
 Defines tasks
 And discusses design
 Negotiationbetweenteam
and product owner
SPRINTPLANNING

67. DAILY SCRUM

68. DAILY SCRUM
 Whatdid you
 achieve yesterday?
 Whatwill you
 achieve today?
 Whatis in your way?
 Everybody is welcome, only
pigs can speak

69. SPRINTDEMO

70.  Tellthe sprint story
 Let thestakeholders accept
your product
 Show thatyou have reached
your goal
SPRINTDEMO

71. RETROSPECTIVE

72. The team tells what
 they willkeep doing
 they willstart doing
 they will stop doing
 they willdo less of
 they will do more of
RETROSPECTIVE

73. SCRUM
ARTI-FACTS

74. PRODUCT BACKLOG

75. PRODUCT BACKLOG
 Toolof theproduct owner
 Business vision
 Deliverables, stories and
functionalities
 Prioritized and estimated
 Anyone can contribute
 Continuouslychanged

76. SPRINTBACKLOG

77.  Tool of theteam
 Selectedproduct backlog items
 Stories split into tasks
 Sprint planand goal
 Equals one product increment
 Never changedduring sprints
SPRINTBACKLOG

78. BURNDOWN CHART

79. BURNDOWN CHART
 Toolof theteam
 Work leftto do vs time
 Tracks progress and predicts
completion
 Actual work line vs Ideal work
line
 Updated every day

80. SCRUM BOARD

81.  Tool of theteam
 Statusof the sprint
 Tracks progress
 Only tasks are moved
 Visual management
 Updated continuously
SCRUM BOARD

82. SCRUM
PROCESS

84. PRODUCT BACKLOG AS PLANNING
TOOL

85. As a <user> I want<goal/desire>,
(so that <benefit>)
As a librarianI want tobe able to searchfor books by
publicationyear
VALUE DRIVEN
USER STORIES

86. PROS
AND
CONS

87.  Tested, workingfeatures
 Simple process
 Clearly defined rules
 Increasedproductivity
 Veryadaptive process
 The team is responsible
 Improvedcommunication
 Focus onproducts
PROS OF SCRUM

88.  Need of skilled staff
 Scalability
 Involves a lot of trust
 Can lead to quick and dirty approach
 Product owneris the critical role
 Product-orientation
CONS OF SCRUM

89. More Fun, Happy Teams