A recent thread started by Perry (see: here), who's working on defining the process and guidelines for his current employer, got met thinking again about "live" specs.
The agile camp tends to favor less documentation in favor of well commented code while the more traditional camp favors detailed documentation upfront. For those of you, who create detailed documentation, say for a brand new system: do you plan to maintain that documentation?
Do you maintain "live" specs?
- Adrian
FYI: This thread is marked as a Poll Thread. Logged-in users can participate in the poll and view the results.
Adrian
A friend of mine just ran an agile project and they used a bunch of whiteboards as their requirements and spcecification repository. They were kept fairly up to date. Especially his personal list of "things the buisiness has forgotton about but we need to deal with."
My experience is that it totally depends on the complexity of the sytem under development. If it is small to mid sized projects, the process tends to be Agile. But, for complex systems and involves multiple cross-functional teams, it makes work a lot easier to have all the documents live and updated.
Thanks,
Achyut Dhakal
Hi Craig,
That's very interesting... I wonder how long those white boards are going to stay up as compared to how long the system is supposed to be in use. What's going to happen when the cleaning staff decides to be helpful and clean up the boards? My definition of keeping the documents "live" was to keep them up to date as long as the system is in use.
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: