Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Co-ordination Support for Managing Progress of Distributed Agile Projects <br /> Sultan Alyahya, Wendy K. Ivins, W. A. Gra...
Contents<br />Tracking Progress in Agile Development<br />Co-located Projects<br />Distributed Projects<br />Current Agile...
Tracking Progress in Agile Development<br />“WORKING SOFTWAREIS THE PRIMARY MEASURE OF PROGRESS”<br />(Agile Manifesto Pri...
Tracking Progress in Agile Development<br />Implementation ≠ “Working Software”<br />Measuring progress of tasks producing...
What Affects “WORKING SOFTWARE”?<br />Unit Testing (UT): Un-tested Code causes defects.<br />Continuous Integration: Code ...
What Affects “WORKING SOFTWARE”?<br />
Tracking Progress of Co-located Agile Projects <br />Face-to-Face Communication<br />Stand-up Meetings<br />
Tracking Progress of Distributed Agile Projects<br />Temporal Distance<br />Geographical Distance<br />Socio-Cultural Dist...
Tracking Progress of Distributed Agile Projects<br />Temporal Distance<br />Geographical Distance<br />Socio-Cultural Dist...
Current Agile Progress Tracking Systems<br />Rally, TargetProcess, VersionOne .. etc<br />provide detailed information abo...
Current Agile Progress Tracking Systems<br />There is an inconsistency between the progress information shown in the track...
Example: <br />Modifying a shared source code artefact belonging to completed story may require a new AT for the story.<br...
  Finding affected team members.
  Notifying affected team members.</li></li></ul><li>The Holistic Approach<br />
The Holistic Approach<br />Tightly integrating task/story progress data with the versioning data<br />
The Holistic Approach<br />Tightly integrating task/story progress data with the versioning data<br />
The Holistic Approach<br />Linking the UT tool, AT tool and CI tool with the tracking system<br />
The Holistic Approach<br />Providing a detailed user story’s progress model<br />
The Holistic Approach- Data Model<br />
The Holistic Approach- Process Models<br />A set of change process models, covering all the technical activities.<br />pro...
Discussion<br />The Holistic Approach helps team members in minimising the inconsistency between the progress information ...
Upcoming SlideShare
Loading in …5
×

Co-ordination Support for Managing Progress of Distributed Agile Projects

619 views

Published on

My presentation in Globagile Workshop (15/8/2011), ICGSE 2011 conference, Helsinki, Finland

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

Co-ordination Support for Managing Progress of Distributed Agile Projects

  1. 1. Co-ordination Support for Managing Progress of Distributed Agile Projects <br /> Sultan Alyahya, Wendy K. Ivins, W. A. Gray<br />(Cardiff University, UK)<br />ICGSE 15-18 Aug 2011<br />
  2. 2. Contents<br />Tracking Progress in Agile Development<br />Co-located Projects<br />Distributed Projects<br />Current Agile Progress Tracking Systems<br />The Holistic Approach<br />Discussion<br />
  3. 3. Tracking Progress in Agile Development<br />“WORKING SOFTWAREIS THE PRIMARY MEASURE OF PROGRESS”<br />(Agile Manifesto Principles)<br />
  4. 4. Tracking Progress in Agile Development<br />Implementation ≠ “Working Software”<br />Measuring progress of tasks producing code ≠ Measuring Progress in Agile<br />
  5. 5. What Affects “WORKING SOFTWARE”?<br />Unit Testing (UT): Un-tested Code causes defects.<br />Continuous Integration: Code must be built & integration-tested to make AT.<br />Acceptance Testing (AT): Failed AT means produced code work improperly.<br />Source Code versioning: Creating, modifying & deleting code affect progress.<br />
  6. 6. What Affects “WORKING SOFTWARE”?<br />
  7. 7. Tracking Progress of Co-located Agile Projects <br />Face-to-Face Communication<br />Stand-up Meetings<br />
  8. 8. Tracking Progress of Distributed Agile Projects<br />Temporal Distance<br />Geographical Distance<br />Socio-Cultural Distance<br />
  9. 9. Tracking Progress of Distributed Agile Projects<br />Temporal Distance<br />Geographical Distance<br />Socio-Cultural Distance<br />Less Communication<br /> Weak Co-ordination<br />
  10. 10. Current Agile Progress Tracking Systems<br />Rally, TargetProcess, VersionOne .. etc<br />provide detailed information about iterations’ tasks/stories.<br />Static, receive progress information from team members only<br />
  11. 11. Current Agile Progress Tracking Systems<br />There is an inconsistency between the progress information shown in the tracking system and the real software produced.<br />
  12. 12.
  13. 13. Example: <br />Modifying a shared source code artefact belonging to completed story may require a new AT for the story.<br />What is the Co-ordination Required?<br /><ul><li> Finding affected stories.
  14. 14. Finding affected team members.
  15. 15. Notifying affected team members.</li></li></ul><li>The Holistic Approach<br />
  16. 16. The Holistic Approach<br />Tightly integrating task/story progress data with the versioning data<br />
  17. 17. The Holistic Approach<br />Tightly integrating task/story progress data with the versioning data<br />
  18. 18. The Holistic Approach<br />Linking the UT tool, AT tool and CI tool with the tracking system<br />
  19. 19. The Holistic Approach<br />Providing a detailed user story’s progress model<br />
  20. 20. The Holistic Approach- Data Model<br />
  21. 21. The Holistic Approach- Process Models<br />A set of change process models, covering all the technical activities.<br />providing co-ordination support including:<br />identifying the potential sources of progress change<br />checking progress constraints<br />finding and notifying affected team members<br />reflecting progress change in the tracking system<br />
  22. 22.
  23. 23. Discussion<br />The Holistic Approach helps team members in minimising the inconsistency between the progress information shown in the tracking system and the real software produced.<br />It can potentially reduce the testing bottlenecks at the end of each iteration and release.<br />(>2/3 of agile community do not use any automated AT tools, VersionOne, Dec 2010 ).<br />
  24. 24. Questions<br />

×