change agile for xp days 2012 benelux v1.0
DESCRIPTION
Workshop done on november 30 at XP Days 2012 Benelux by Andre Heijstek and Ben LindersTRANSCRIPT
veranderproject.nl
Ben Linders, André Heijstek
Change Agile
Change Projects
Characteris<cs√No SMART goal√SoB factors√Con<nuous Process√Adapt
Agile or Waterfall?
3
Type 2 Projects
Product Development
Type 4 Projects
Research & Changemanagement
Type 1 Projects
Engineering
Type 3 Projects
Software Development
Met
hods
wel
l def
ined
JaN
ee
Goals well definedJa Nee
waterfall
agile
Release Backlog
4
TO-DO DOING DONE
Release Planning
Sprint Planning
Sprint Execution
Sprint 1 Backlog
5
TO-DO DOING DONE
Theory
Practice
Reflection
Agile Manifesto
6
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
That is, while there is value in the items on the right, we value the items on the left more.
That is, while there is value in the items on the right, we value the items on the left more.
MoreAgile Manifesto
by Geert Bossuyt
Teamwork & responsibility over Individuals and Interaction
Deliver Value over Working software
Partnership elaboration over Customer collaboration
Embrace change over Respond to Change
While we value the Agile Manifesto, we state that MoreAgile is more Agile.
Scrum in a Nutshell
7
Three pillars
• Transparency
• Inspection
• Adaptation
8
Scrum framework•Product owner•ScrumMaster•Team
Roles
•(Release planning)•Sprint planning meeting•Daily scrum meeting•Sprint review meeting•Sprint retrospective
Events
•Product backlog•Sprint backlog•(Burndown charts)•Definition of Done
Artifacts
9
Change
Scrum framework•Change owner•ScrumMaster•Team
Roles
•(Release planning)•Sprint planning meeting•Daily scrum meeting Sprint review meeting
•Sprint retrospective
Events
•Product backlog•Sprint backlog•(Burndown charts)•Definition of Done
Artifacts
10
Change owner• Define the content of the change
• Decide on release date and content
• Be responsible for the “profitability” of the change (ROI)
• Prioritize features according to (market) value
• Adjust features and priority every iteration, as needed
• Accept or reject work results
11
Scrum framework•Change owner•ScrumMaster•Team
Roles
•(Release planning)•Sprint planning meeting•Daily scrum meeting•Sprint review meeting•Sprint retrospective
Events
•Product backlog•Sprint backlog•(Burndown charts)•Definition of Done
Artifacts
12
Release Planning
13
Product Vision
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
Epic
User Story
User Story
Epic
User Story
Epic Epic
1 2 3 4 5 6 7 8
User stories are the Agile way of documenting
requirements.As a <user role>
I want <something>So I can achieve <value>
Change
Rough Estimation
14
High Medium Low
User Story
User Story
User StoryUser StoryUser
Story
User StoryUser StoryUser StoryUser
StoryUser StoryUser StoryUser StoryUser
Story
User StoryUser StoryUser StoryUser
StoryUser StoryUser StoryUser StoryUser
StoryUser StoryUser Story
User StoryUser StoryUser
StoryUser StoryUser StoryUser Story
Rough Estimation
15
High
User Story
User Story
User StoryUser StoryUser
Story
Rough Estimation
16
High Medium Low
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
1 StoryPoint
Vertical Slicing
17
Software Development Change Management
Presentation Layer
Business Layer
Database Layer
Coaching
Training
Process Artefacts
Definition of Donein 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
18
• 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
Definition of Donein Change Management
• New methods defined• Employees trained• Change initiated in at
least 1 pilot project• Positive feedback of
users
19
• Ownership transfered• First round of
improvement suggestions processed
• Plan defined for further improvements
• “Regression-test” (after care) on previous sprints
Sprint 1 Backlog
20
TO-DO DOING DONE
Theory
Practice
Reflection
Ben Linders Advies
3
Agile Process Improvement
Expected benefits:• Collaboration PI team
and stakeholders• Deployment (over
defining) processes• Adopt to changes• Incrementaly, ROI• Learn to work Agile
Ben Linders Advies
4
Golden Rules for PI• 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
Ben Linders Advies
5
Case: Making agile fit!• 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!
1Create a Roadmap• Change steps (User Stories)
– break up the project in 10-‐20 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