http://greyfiti.com/2009/evolutionary-documentation/ life as a tech writer on the cusp of the diamond age Sat, 04 Sep 2010 13:30:41 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://greyfiti.com/2009/evolutionary-documentation/comment-page-1/#comment-165 Greyfiti » Blog Archive » Why minimalist documentation is not always a good match for agile development Fri, 12 Feb 2010 19:51:52 +0000 http://greyfiti.com/?p=87#comment-165 [...] I’ve detailed in my Evolutionary Documentation post on this blog, agile development forces your user documentation to grow and evolve alongside [...] [...] I’ve detailed in my Evolutionary Documentation post on this blog, agile development forces your user documentation to grow and evolve alongside [...]

]]> http://greyfiti.com/2009/evolutionary-documentation/comment-page-1/#comment-52 Greyfiti » Blog Archive » Why minimalist documentation is not a good match for Agile development Mon, 07 Dec 2009 21:10:35 +0000 http://greyfiti.com/?p=87#comment-52 [...] I’ve detailed in my Evolutionary Documentation post on this blog, agile development forces your user documentation to grow and evolve alongside [...] [...] I’ve detailed in my Evolutionary Documentation post on this blog, agile development forces your user documentation to grow and evolve alongside [...]

]]> http://greyfiti.com/2009/evolutionary-documentation/comment-page-1/#comment-49 Kat Kuvinka Tue, 25 Aug 2009 18:06:16 +0000 http://greyfiti.com/?p=87#comment-49 Hi Shannon, the way we are doing Scrum, and it seems pretty logical to me, is that Marketing/Product Management *has* defined the product to the point where the high-level description is in place. Furthermore, the whole team spends time planning and prioritizing...so there really is no mystery about the conclusion, just maybe some fog around how it will unfold. The challenge for documentation is to reach the finish line at the same time, so that we can meet the goal of a releasable product each sprint. I have heard that it works better in some environements to allow the document to lag one sprint behnd. Hi Shannon, the way we are doing Scrum, and it seems pretty logical to me, is that Marketing/Product Management *has* defined the product to the point where the high-level description is in place. Furthermore, the whole team spends time planning and prioritizing…so there really is no mystery about the conclusion, just maybe some fog around how it will unfold. The challenge for documentation is to reach the finish line at the same time, so that we can meet the goal of a releasable product each sprint. I have heard that it works better in some environements to allow the document to lag one sprint behnd.

]]>