Agile documentation

Agile documentation

9f40c41cec8ab0f4fd1e7900a69b1d3d?s=128

Soenke Ruempler

May 14, 2013
Tweet

Transcript

  1. 2.

    About me "Chief Trolling Officer" at Jimdo Passionate about the

    web, open source, agile software development and knowledge management (and everything combined) Twitter: @s0enke Blog: http://ruempler.eu/
  2. 3.

    About Jimdo • WYSIWYG Website creator in 12 languages •

    currently 8 million registrations • ~150 employees in Offices in Hamburg, San Fransisco, Shanghai, Tokyo
  3. 5.

    Agenda - What to expect? • What can be documented

    in software engineering and IT operations • Documentation antipatterns • Documentation patterns • Agile documentation to the extreme!
  4. 6.
  5. 7.

    Rules • Listen • Ask whenever you want • Think

    • Discuss - it's a highly controversial topic!
  6. 28.
  7. 34.
  8. 39.
  9. 46.
  10. 48.

    Business value low high Total cost of ownership low high

    Wikis Executable High level feature / behavior specs (e. g. cucumber) Static documents Unit tests
  11. 49.
  12. 56.

    Rationale / Business value Executable Specification of the feature Monitors:

    Working Jimdo website, Login, Upload to webserver, Background-Upload to S3, and S3 ;-)
  13. 62.
  14. 63.

    ?

  15. 64.

    Links and Literature • My diploma thesis • Scott Ambler

    on Agile Documentation • Specification by Example • cucumber-nagios • "Software Engineering Rationale: Wissen über Software erheben und erhalten"