Methodology Madness—DPM:UK, Manchester 2016

Agile? Waterfall? Kanban? Wagile?! With the obsession around methodologies and following certain processes ever present in the DPM world, Suze takes a look at the core ones used in digital and how they can help and hinder.

She’ll answer those all important questions like: What are the core principles of the different methodologies? How are they similar and how do they differ? How appropriate are they for digital projects? How can you work with their strengths and can you incorporate them into your way of working? And do you really need them to succeed?

Transcript

1. M E T H O D O L O G Y M A D N E S S S U Z E H A W O R T H @suzehaworth
2. QUIZ OF METHODOLOGIES
4. WATERFALL
6. SCRUM
8. 2 PRINCE2
9. -D
10. -D KANBAN
11. PROJECT MANAGEMENT METHODOLOGIES
12. Waterfall PRINCE2 Critical Chain Management Agile Lean Benefits Realisation Management PROJECT MANAGEMENT METHODOLOGIES Rapid Application Development Six Sigma Scrum DMAIC Kanban
13. H O W D O Y O U D E C I D E ?
14. H O W D O Y O U D E C I D E ? Size Framework for your lovely digital project Text goes here Duration Complexity Organisation Clients
15. A N D P O S S I B LY T H E M A I N O N E … Your lovely digital project Text goes here Existing processes
16. W A T E R F A L L
17. W A T E R F A L L v s
18. W A T E R F A L L v s A G I L E
19. “Agile is best, right?”
20. “Agile is best, right?”
21. WATERFALL
22. Upfront requirements gathering Work completed sequentially in phases Testing occurs at end of development Client doesn’t need to be heavily involved C O R E P R I N C I P L E S O F W A T E R F A L L
23. Upfront requirements gathering Work completed sequentially in phases Testing occurs at end of development Client doesn’t need to be heavily involved C O R E P R I N C I P L E S O F W A T E R F A L L
24. Upfront requirements gathering Work completed sequentially in phases Testing occurs at end of development Client doesn’t need to be heavily involved C O R E P R I N C I P L E S O F W A T E R F A L L
25. Upfront requirements gathering Work completed sequentially in phases Testing occurs at end of development Client doesn’t need to be heavily involved C O R E P R I N C I P L E S O F W A T E R F A L L
26. Client doesn’t need to be heavily involved Your lovely digital project Projects where you’re working with other organisations or remote workers 01 02 03 04 Projects with a fixed scope, time and budget Smaller, well-defined and simpler projects Projects with an absent client W A T E R F A L L P R O J E C T S A R E …
27. SCRUM
28. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan C O R E P R I N C I P L E S O F A G I L E & S C R U M
29. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan C O R E P R I N C I P L E S O F A G I L E & S C R U M Scrum: Self-organising, cross-functional team
30. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan C O R E P R I N C I P L E S O F A G I L E & S C R U M
31. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan C O R E P R I N C I P L E S O F A G I L E & S C R U M Scrum: Time-boxed sprints of work with a shippable product
32. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan C O R E P R I N C I P L E S O F A G I L E & S C R U M
33. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan C O R E P R I N C I P L E S O F A G I L E & S C R U M Scrum: Consistent, regular client involvement
34. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan C O R E P R I N C I P L E S O F A G I L E & S C R U M
35. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan C O R E P R I N C I P L E S O F A G I L E & S C R U M Scrum: Constantly evolving requirements
36. Client doesn’t need to be heavily involved Your lovely digital project Projects where your organisation is responsible for the whole process 01 02 03 04 Projects with scope for changing requirements Larger, undefined, complex projects Projects with an involved client A G I L E P R O J E C T S A R E …
37. SO COME ON, WHICH IS BETTER?
38. S O C O M E O N , W H I C H I S B E T T E R ? Your lovely digital project Text goes here R E G U L A R I T E R A T I O N S
39. S O C O M E O N , W H I C H I S B E T T E R ? Your lovely digital project Text goes here C L I E N T I N V O LV E M E N T
40. S O C O M E O N , W H I C H I S B E T T E R ? Your lovely digital project Text goes here T E A M C O L L A B O R A T I O N
41. S O C O M E O N , W H I C H I S B E T T E R ? Your lovely digital project Text goes here E V O LV I N G R E Q U I R E M E N T S
42. Over a 5 year period, an average of 53% of projects ran over on cost, and 76% ran over on time THE CHAOS MANIFESTO, 2013 https://www.versionone.com/assets/img/files/CHAOSManifesto2013.pdf
43. Here’s a great example…
44. Your lovely digital project Text goes here W H A T A B O U T A H Y B R I D ?
45. Wagile…
46. “WAgile, as [we] all know, stands for "Waterfall-Agile", and is the pinnacle of dysfunctional development methodologies. Yes, folks: literally thousands of projects have failed the WAgile way” JASON GORMAN http://www.codemanship.co.uk/parlezuml/blog/?postid=708 9
47. “We’re Agile because we do a daily stand-up”
48. “We’re Agile because we do a daily stand-up”
49. W H A T A B O U T A H Y B R I D ? Text goes here Discover Review Build Your lovely digital project Plan
50. W H A T A B O U T A H Y B R I D ? Discover Plan Build Review Build Review Build Review
51. W H A T A B O U T A H Y B R I D ? Discover Build Review Plan Discover Build Review Plan Discover Build Review Plan
52. W H A T A B O U T A H Y B R I D ? Discover Plan Build Review Plan Build Review Plan Build Review
53. YES, I SAID LET’S USE A HYBRID
54. W H A T A B O U T A H Y B R I D ? Your lovely digital project Text goes here
55. W H A T A B O U T A H Y B R I D ? Your lovely digital project Text goes here Ideal: Empowered, available Product Owner
56. W H A T A B O U T A H Y B R I D ? Your lovely digital project Text goes here Ideal: Empowered, available Product Owner Hybrid: Help bridge the gap between client and team
57. W H A T A B O U T A H Y B R I D ? Your lovely digital project Text goes here Ideal: Cross-functional, dedicated team
58. W H A T A B O U T A H Y B R I D ? Your lovely digital project Text goes here Ideal: Cross-functional, dedicated team Hybrid: Team members working together and collaborating
59. W H A T A B O U T A H Y B R I D ? Your lovely digital project Text goes here Ideal: Planning requirements per sprint
60. W H A T A B O U T A H Y B R I D ? Your lovely digital project Text goes here Ideal: Planning requirements per sprint Hybrid: Some upfront shaping, but leave detailed planning to the sprint
61. W H A T A B O U T A H Y B R I D ? Your lovely digital project Text goes here Ideal: Design within each sprint
62. W H A T A B O U T A H Y B R I D ? Your lovely digital project Text goes here Ideal: Design within each sprint Hybrid: Design at the last responsible moment
63. Your lovely digital project Text goes here Get help W H A T A B O U T A H Y B R I D ?
64. Your lovely digital project Text goes here Get management buy in W H A T A B O U T A H Y B R I D ?
65. Your lovely digital project Text goes here Get real W H A T A B O U T A H Y B R I D ?
66. Your lovely digital project Text goes here If you fail, fail fast and move on W H A T A B O U T A H Y B R I D ?
67. C O M M O N F A U L T S T O L O O K O U T F O R Your lovely digital project Text goes here
68. C O M M O N F A U L T S T O L O O K O U T F O R Your lovely digital project Text goes here No process or structure 01
69. C O M M O N F A U L T S T O L O O K O U T F O R Your lovely digital project Text goes here People on team doing different things No process or structure 01 02
70. C O M M O N F A U L T S T O L O O K O U T F O R Your lovely digital project Text goes here Processes for the sake of processes People on team doing different things No process or structure 01 02 03
71. C O M M O N F A U L T S T O L O O K O U T F O R Your lovely digital project Text goes here Processes for the sake of processes People on team doing different things No process or structure 01 02 03 One size fits all approach 04
72. “A methodology guarantees project success”
73. “A methodology guarantees project success”
74. P E R S O N A L
75. P E R S O N A L P R A C T I C A L A N D
76. f Y g W f C O M M U N I C A T I O N L E A D E R S H I P F L E X I B I L I T Y P R O B L E M S O LV E R P E R S O N A L
77. f } ( @ c T I M E & C O S T E S T I M A T I O N T E C H N I C A L K N O W L E D G E R I S K A S S E S S M E N T P R O J E C T P R O C E S S P R A C T I C A L
78. f } ( @ c T I M E & C O S T E S T I M A T I O N T E C H N I C A L K N O W L E D G E R I S K A S S E S S M E N T P R O J E C T P R O C E S S P R A C T I C A L Here it is!
79. Lastly…
80. CAKE
82. Deliverables
83. Personal Deliverables
84. Personal Practical Deliverables
85. T H A N K S ! S U Z E H A W O R T H @suzehaworth