Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Close The Feedback Loop. Using Application Ana...

Close The Feedback Loop. Using Application Analytics To Improve Agile Development - CodepaLOUsa 2014

From CodepaLOUsa 2014, http://www.codepalousa.com

One of the major tenants of Agile development is customer involvement. This is usually achieved by working with representative customers or proxies during design and development. While there are limitations on how many stakeholders can effectively participate, application analytics can add a new dimension to customer collaboration. By easily tracking and analyzing how every user actually uses your application you can zoom in to the usage hotspots of your application and maximize your development efficiency. This session will use the freely available Gibraltar Loupe to gather useful information from every single user of your application, such as which features they really do or don't use and all errors that they encounter. By leveraging the data provided by proper analytics you will be able to gather usable information with minimal development investment.

Joe Kuemerle

February 26, 2014
Tweet

More Decks by Joe Kuemerle

Other Decks in Programming

Transcript

  1. Close The Feedback Loop Using Application Analytics To Improve Agile

    Development Joe Kuemerle www.kuemerle.com @jkuemerle
  2. @jkuemerle / www.kuemerle.com Joe Kuemerle • Over 15 years of

    development experience with a broad range of technologies • Focused on application and data security, coding best practices and regulatory compliance • Presenter at community, regional and national events.
  3. @jkuemerle / www.kuemerle.com Manifesto for Agile Software Development http://www.agilemanifesto.org/ 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.
  4. @jkuemerle / www.kuemerle.com Manifesto for Software Craftsmanship http://manifesto.softwarecraftsmanship.org/ As aspiring

    Software Craftsmen we are raising the bar of professional software development by practicing it and helping others learn the craft. Through this work we have come to value: Not only working software, but also well-crafted software Not only responding to change, but also steadily adding value Not only individuals and interactions, but also a community of professionals Not only customer collaboration, but also productive partnerships That is, in pursuit of the items on the left we have found the items on the right to be indispensable.
  5. @jkuemerle / www.kuemerle.com 10 Key Principles of Agile http://www.allaboutagile.com/what-is-agile-10-key-principles/ 1.

    Active user involvement is imperative 2. The team must be empowered to make decisions 3. Requirements evolve but the timescale is fixed 4. Capture requirements at a high level; lightweight & visual 5. Develop small, incremental releases and iterate 6. Focus on frequent delivery of products 7. Complete each feature before moving on to the next 8. Apply the 80/20 rule 9. Testing is integrated throughout the project lifecycle – test early and often 10. A collaborative & cooperative approach between all stakeholders is essential
  6. @jkuemerle / www.kuemerle.com “People in both fields operate with beliefs

    and biases. To the extent you can eliminate both and replace them with data, you gain a clear advantage.” ― Michael Lewis, Moneyball: The Art of Winning an Unfair Game
  7. @jkuemerle / www.kuemerle.com “... The Census report, like most such

    surveys, had cost an awful lot of money and told nobody anything they didn't already know -- except that every single person in the Galaxy had 2.4 legs and owned a hyena. Since this was clearly not true the whole thing eventually had to be scrapped.” ― Douglas Adams, So Long, And Thanks For All The Fish
  8. @jkuemerle / www.kuemerle.com “It is a capital mistake to theorize

    before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts.” Sherlock Holmes, A Scandal in Bohemia
  9. @jkuemerle / www.kuemerle.com Resources • http://gibraltarsoftware.com/ • https://github.com/jkuemerle/DoorComp • http://www.statisticsdonewrong.com/

    • http://www.bbc.co.uk/podcasts/series/moreorless • http://www.agilemanifesto.org/ • http://manifesto.softwarecraftsmanship.org/ • http://www.allaboutagile.com/what-is-agile-10-key- principles/