Robert Gomes — Tue, 11 Aug 2009 23:48:00 GMT

OK, another interesting view, when we speak about agile, I am hoping it is Agile, agile enough to allow proper documentation. the bigest issue with software development id propper documentation, it’s just not htere. FROM EXPERIENCE, twikies are basically used as in the case of Share Point, a repository for Project Overviews, Mission, Deliverable, List and contact info for Team members, Documents, Prototypes and anything related to a project. A basic requirement can live in the actual twiki. For complex requirements we still use WORD. We post to the twiki, instead of emailing out the documents. TWIKIS have natural version control of the twiki page that changed as well as the actual documents you update. Complex user flows and interaction documentation requires the ability to perform more formatting, we are not just talking about making the document look pretty, but to actually format the document so it makes sense to an EXPERIENCED developer and software architect. TWIKIS SIMPLY CAN NOT DO THAT. (yet :-) )

It’s a nice idea, to create documents on a (twiki) web page and Google may make it possible with their online version of office one day. But until then, I would not risk a mission critical application project to a technology that is simply not intended for this purpose.

Good luck and keep us posted on how it goes.

Regards
Rob…

Boxes and Arrows: Comments by Robert Gomes