Comments on: Deep Agile Panel Questions – Documentation http://www.renaissancesoftware.net/blog/archives/44 Blogging about Agile Development, especially embedded. Follow me on twitter: jwgrenning Thu, 02 Feb 2012 07:09:14 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: wikitried http://www.renaissancesoftware.net/blog/archives/44/comment-page-1#comment-597 wikitried Mon, 25 May 2009 08:35:02 +0000 http://www.renaissancesoftware.net/blog/?p=44#comment-597 We have also tried wiki, but it depends on personal commitment to update the wiki , as any other documentation. And when the environment is conservative and not friendly the developers prefer to do old type of documentation once, instead of regulary updating dynamic documentation :( We have also tried wiki, but it depends on personal commitment to update the wiki , as any other documentation. And when the environment is conservative and not friendly the developers prefer to do old type of documentation once, instead of regulary updating dynamic documentation :(

]]> By: James Martin http://www.renaissancesoftware.net/blog/archives/44/comment-page-1#comment-587 James Martin Thu, 14 May 2009 01:08:43 +0000 http://www.renaissancesoftware.net/blog/?p=44#comment-587 This is good practical advice. I have come to love and use Robert Martin's first law of documentation, from the PPP book: "Create no document unless its need is immediate and significant." It's the first thing I think of and comment on when someone hands me a document for "review". This is good practical advice.

I have come to love and use Robert Martin’s first law of documentation, from the PPP book:

“Create no document unless its need is immediate and significant.”

It’s the first thing I think of and comment on when someone hands me a document for “review”.

]]> By: jwgrenning http://www.renaissancesoftware.net/blog/archives/44/comment-page-1#comment-586 jwgrenning Wed, 13 May 2009 19:30:45 +0000 http://www.renaissancesoftware.net/blog/?p=44#comment-586 Sounds like a really good application for a wiki. You can collect the important ideas as you go, and roll out the official version as needed. Sounds like a good approach when you may have some phase gates to navigate. Sounds like a really good application for a wiki. You can collect the important ideas as you go, and roll out the official version as needed. Sounds like a good approach when you may have some phase gates to navigate.

]]> By: Mark VanderVoord http://www.renaissancesoftware.net/blog/archives/44/comment-page-1#comment-585 Mark VanderVoord Wed, 13 May 2009 19:08:00 +0000 http://www.renaissancesoftware.net/blog/?p=44#comment-585 One handy trick: We have used a wiki for all of our design and API documentation. This allows the docs to be updated easily as the software evolves, and avoids the complications of rolling out "official docs" every iteration and making sure everyone has the latest version. One handy trick: We have used a wiki for all of our design and API documentation. This allows the docs to be updated easily as the software evolves, and avoids the complications of rolling out “official docs” every iteration and making sure everyone has the latest version.

]]>