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.

A Case Of Artful Exploration

517 views

Published on

Agiles 2009 presentation

Published in: Technology
  • Be the first to comment

  • Be the first to like this

A Case Of Artful Exploration

  1. 1. A Case of Artful Exploration An agile experience of extending free open  source software Diego Fontdevila Juan Gabardini
  2. 2. Index <ul><li>Project Case
  3. 3. Artful Making
  4. 4. Challenges
  5. 5. Conclusion </li></ul>
  6. 6. Project Case <ul><li>IT Manager Alejandro Borra
  7. 7. Tool Selection
  8. 8. Team Casting
  9. 9. Existing vs. New or modified functionality </li></ul>Business case video
  10. 10. Artful Making <ul><li>Qualities of Artful Making </li><ul><li>Release
  11. 11. Ensemble
  12. 12. Collaboration
  13. 13. Play </li></ul><li>Iteration Cost Structure </li><ul><li>Cost of Exploration
  14. 14. Cost of Reconfiguration </li></ul><li>New way of learning </li></ul>
  15. 15. Project Vision Issues <ul><li>Inception
  16. 16. Platform vs. Product (Site) Development
  17. 17. Prototyping </li><ul><li>Workshops
  18. 18. Killer features </li></ul></ul>
  19. 19. Whole team <ul><li>Whole team mindset was hard to reach
  20. 20. Content development -> Marketing team
  21. 21. Platform development -> Development team (vendor and customer IT)‏ </li></ul>
  22. 22. Iteration estimation and rythmn <ul><li>It converged as expected (around sprint 4).
  23. 23. Project has fixed price
  24. 24. Customer has great disposition to balance cost, effort and functionality
  25. 25. From the customer's point of view complexity is still unknown.
  26. 26. Customer planning participation improved with the impending soft launch (beta release). </li></ul>
  27. 27. Cost of iteration <ul><li>Exploration (Rehearsals & experiments)‏ </li><ul><li>Experiments and prototypes </li></ul><li>Reconfiguration </li><ul><li>Patches vs. Platform versions
  28. 28. Extensible platform
  29. 29. On site support for site developing </li></ul></ul>Workshop video
  30. 30. Free Open Source & Complexity <ul><li>Is this a package implementation? </li><ul><li>Modifications to the code base </li></ul><li>Role of the platform
  31. 31. Is it a Legacy System?
  32. 32. Application level platform </li></ul>
  33. 33. Design and Unit Test <ul><li>Contract Design vs Exploratory Design
  34. 34. Not useful to make test-first while exploring
  35. 35. Hard to get off the road
  36. 36. Where should we add our test?
  37. 37. Understanding test architecture
  38. 38. Hard to find the inflexion point (Michael Feathers)‏ </li></ul>
  39. 39. SCM & Continuous Integration <ul><li>Platform with superb extension support </li><ul><li>Hooks, independent deployment of modules, etc. </li></ul><li>But... implementing a CI process was hard
  40. 40. Identifying dependencies
  41. 41. What test should we run? (original, ours?)‏
  42. 42. All the same, the few tests that were implemented actually broke many times, thus helping maintain consistency. </li></ul>
  43. 43. Functional Testing <ul><li>How to validate coverage of requirements served by existing functionality? </li><ul><li>How to </li></ul><li>Product regression is hard </li><ul><li>And automating it harder </li></ul><li>Modifications to existing functionality require evidence of business value. </li><ul><li>Problem reaching a common language </li></ul></ul>
  44. 44. <ul><li>  Release October 15 </li></ul>Conclusion
  45. 45. Thanks!

×