Change Agile. Ben Linders, André Heijstek. veranderproject.nl

Transcription

1 Change Agile Ben Linders, André Heijstek veranderproject.nl

2 Change Projects Characteris<cs No SMART goal SoB factors Con<nuous Process Adapt

3 Agile or Waterfall? Methods well defined Ja Nee Type 2 Projects Product Development Type 1 Projects Engineering waterfall Type 4 Projects agile Research & Changemanagement Type 3 Projects Software Development Ja Goals well defined Nee 3

4 Release Backlog TO-DO DOING DONE Release Planning Sprint Planning Sprint Execution 4

5 Sprint 1 Backlog TO-DO DOING DONE Theory Practice Reflection 5

6 Agile Manifesto MoreAgile 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: by Geert Bossuyt Individuals and interactions over processes and tools Teamwork & responsibility over Individuals and Interaction Working software over comprehensive documentation Deliver Value over Working software Partnership elaboration over Customer collaboration Customer collaboration over contract negotiation Embrace change over Respond to Change Responding to change over following a plan While we value the Agile Manifesto, we state that MoreAgile is more Agile. That is, while there is value in the items on the right, we value the items on the left more. 6

7 7 Scrum in a Nutshell

8 Three pillars Transparency Inspection Adaptation 8

9 Roles Scrum framework Product Change owner ScrumMaster Team Events (Release planning) Sprint planning meeting Daily scrum meeting Sprint review meeting Sprint retrospective Artifacts Product backlog Sprint backlog (Burndown charts) Definition of Done 9

10 Roles Change owner ScrumMaster Team Scrum framework Events (Release planning) Sprint planning meeting Daily scrum meeting Sprint review meeting Sprint retrospective Artifacts Product backlog Sprint backlog (Burndown charts) Definition of Done 10

11 Change owner Define the content of the change change (ROI) needed Accept or reject work results Decide on release date and content Be responsible for the profitability of the Prioritize features according to (market) value Adjust features and priority every iteration, as 11

12 Roles Change owner ScrumMaster Team Scrum framework Events (Release planning) Sprint planning meeting Daily scrum meeting Sprint review meeting Sprint retrospective Artifacts Product backlog Sprint backlog (Burndown charts) Definition of Done 12

13 Change Release Planning Product Vision stories are the Agile way of documenting Epic Epic requirements. As a <user role> I want <something> So I can achieve <value> Epic Epic 13

14 Rough Estimation 14 High Medium Low

15 Rough Estimation High 15

16 Rough Estimation 16 High Medium Low 1 Point

17 Vertical Slicing Software Development Change Management Presentation Layer Coaching Business Layer Training Database Layer Process Artefacts 17

18 Definition of Done in Software Development Tested & bugfree Deployed to test server, so PO can test All user actions All supported browsers IE7/8 Chrome Firefox Safari on Mac Comments in code Refactoring Code reviewed when needed Remember to check the Style_guideline Maintain wiki page Maintain ERD document Versions of components License overview Check the constraints 18

19 Definition of Done in Change Management New methods defined Employees trained Change initiated in at least 1 pilot project Positive feedback of users Ownership transfered First round of improvement suggestions processed Plan defined for further improvements Regression-test (after care) on previous sprints 19

20 Sprint 1 Backlog TO-DO DOING DONE Theory Practice Reflection 20

21 Ben Linders Advies Agile Process Improvement Expected benefits: Collaboration PI team and stakeholders Deployment (over defining) processes Adopt to changes Incrementaly, ROI Learn to work Agile 3

22 Golden Rules for PI Ben Linders Advies Dare to share, early and frequently Result depends on team, not individuals The one who checks out a task is not necessarily the one who has to finish it The one s working on a task are the right people You may critique anything, but never criticize anyone BenLinders.com/GoldenRules 4

23 Case: Making agile fit! Ben Linders Advies SW product development, project based org. Started Agile some months ago with 3 teams Teams signal impediments with the Product owners Project leader Line Managers Change needed, but the agile show must go on! 5

24 Create a Roadmap 1 Change steps ( Stories) break up the project in concrete steps (each having value) 15 minutes Defini<on of Done? (Value/DoD) 10 minutes Es<mates business value story points Release Planning Assign stories to sprints