Article Idea:
Using wiki’s for design specifications: Mistakes Made and Lessons Learned
suggested by Peter Gremett on 2007/09/13
Agile has gained a lot of attention in recent years and claims to help companies accelerate revenue, reduce costs, improve quality, ensure compliance, and drive innovation throughout the product lifecycle. The methodology focuses on processes that are light and sufficient for the teams to quickly bring product to market. Design is an important part of the product life cycle and as designers, we often find ourselves working with teams that are using these processes. The documentation of the design, its behaviors, and other design requirements are best documented through a wiki when working in agile environments. This method is both adaptive and sufficient for teams to build and deliver product to customers.
Want to see this idea turned into a story?
5 people said yes. | 0 people said no.
Ben Tremblay
0 Reputation points
Posted 2007/11/07 @ 20:37PM with
Without the “Mistakes Made and Lessons Learned” my comment would have been something like “Fill your boots!” in the sense of giving you enough rope to uhhhhhhh end up doing macrame.
But yaa … heaven knows I /adore/ things Wiki, so when and where and how it fails or falls short I think is significant for all sentient beings.
(FWIW I find “design” too broad; there are aspects of decision making, to my way of thinking, where wiki fails spectacularly.)