• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Change agile for XP Days 2012 benelux v1.0
 

Change agile for XP Days 2012 benelux v1.0

on

  • 611 views

Workshop done on november 30 at XP Days 2012 Benelux by Andre Heijstek and Ben Linders

Workshop done on november 30 at XP Days 2012 Benelux by Andre Heijstek and Ben Linders

Statistics

Views

Total Views
611
Views on SlideShare
610
Embed Views
1

Actions

Likes
0
Downloads
5
Comments
0

1 Embed 1

http://www.slashdocs.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Change agile for XP Days 2012 benelux v1.0 Change agile for XP Days 2012 benelux v1.0 Presentation Transcript

    • Change  Agile      Ben  Linders,  André  Heijstek veranderproject.nl
    • Change  ProjectsCharacteris<cs√No  SMART  goal√SoB  factors√Con<nuous  Process√Adapt
    • Agile  or  Waterfall? Nee Type 2 Projects Type 4 Projects Product Development ag & Research ileMethods well defined Changemanagement Type 1 Projects Type 3 Projects Engineering waterfall Software Development Ja Ja Nee Goals well defined 3
    • Release Backlog TO-DO DOING DONE Release Planning Sprint Planning Sprint Execution4
    • Sprint 1 Backlog TO-DO DOING DONE Theory Practice Reflection5
    • Agile Manifesto MoreAgile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. by Geert Bossuyt Through this work we have come to value: Individuals and interactions over processes and tools Teamwork & responsibility over Individuals and Interaction WorkingDeliver Value over Working software documentation software over comprehensive Partnership elaboration over Customer collaboration Customer collaboration over contract negotiation Embrace change over Respond to Change Responding to change over Agile Manifesto,plan While we value the following a 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
    • Scrum in a Nutshell7
    • Three pillars • Transparency • Inspection • Adaptation8
    • Scrum framework Roles • Product owner Change • ScrumMaster Events • Team • (Release planning) • Sprint planning meeting • Daily scrum meeting • Sprint review meeting • Sprint retrospective Artifacts • Product backlog • Sprint backlog • (Burndown charts) • Definition of Done9
    • Scrum framework Roles • Change owner • ScrumMaster Events • Team • (Release planning) • Sprint planning meeting • Daily scrum meeting Sprint review meeting • Sprint retrospective Artifacts • Product backlog • Sprint backlog • (Burndown charts) • Definition of Done10
    • 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 results11
    • Scrum framework Roles • Change owner • ScrumMaster Events • Team • (Release planning) • Sprint planning meeting • Daily scrum meeting • Sprint review meeting • Sprint retrospective Artifacts • Product backlog • Sprint backlog • (Burndown charts) • Definition of Done12
    • Release Planning Product Vision 1 2 3 4 5 6 7 8 User Change User User User Story Story Story User stories are the Story Epic Agile way of documenting User User User User Story Story Story requirements. Epic Story As a <user role> Epic Epic User User User User User Story Story Story I want <something> Story Story So I can achieve <value> User User User User User User Story Story Story Story Story Story13
    • Rough Estimation High Medium Low User User User User User User User User Story User Story User Story Story User Story User Story Story Story Story Story User User User User Story Story User User User Story User User Story Story Story User Story Story User Story Story Story User Story User User Story User User Story Story User Story Story Story Story14
    • Rough Estimation High User User User User Story Story Story Story User Story15
    • Rough Estimation High Medium Low User User User User User User User User Story Story Story Story Story Story Story Story User User User User User User User Story Story Story Story Story Story Story User User User User Story Story Story Story User User 1 Story Story Story Point16
    • Vertical Slicing Software Development Change Management Presentation Layer Coaching Business Layer Training Database Layer Process Artefacts17
    • Definition of Done in Software Development • Tested & bugfree • Refactoring • Deployed to test server, • Code reviewed when so PO can test needed • All user actions • Remember to check • All supported browsers the Style_guideline • IE7/8 • Maintain wiki page • Chrome • Maintain ERD document • Firefox • Versions of components • Safari on Mac • License overview • Comments in code • Check the constraints18
    • Definition of Done in Change Management • Ownership transfered • New methods defined • First round of • Employees trained improvement suggestions • Change initiated in at processed least 1 pilot project • Plan defined for further • Positive feedback of improvements users • “Regression-test” (after care) on previous sprints19
    • Sprint 1 Backlog TO-DO DOING DONE Theory Practice Reflection20
    • Ben Linders Advies Agile Process ImprovementExpected benefits:• Collaboration PI team and stakeholders• Deployment (over defining) processes• Adopt to changes• Incrementaly, ROI• Learn to work Agile 3
    • Ben Linders Advies 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 4
    • Ben Linders Advies 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 ManagersChange needed, but the “agile” show must go on! 5
    • Create  a  Roadmap 1• 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