Skip to content

Comment on Software Checklist

Comments

Using wiki's in two different companies provided us with these checklist like capabilities. We used MoinMoin at a prior company and now use MediaWiki, but the technology isn't the point.

Everyone contributes to the wiki and it accrues knowledge from experience. Some process documentation is carefully reviewed for accuracy, but it also left a bit free-form so as to accommodate situation specific variations from the norm.

The verification team (I dislike the term QA) encapsulates as much as possible into the testing framework, but since the wiki based descriptions are so much more rich, they remain a go to resource.

Recently I moved the IT/Networking staff to start making their project plans in the wiki. Their defect rate has plummeted to nearly zero - mostly because they are making plans! But what they've discovered is that they now have frameworks of plans (checklists) from which they can derive their next plan.

Others have mentioned Dr. Gawande and I would recommend his book http://atulgawande.com/book/the-checklist-manifesto/

Good discussion. Don't have an internal wiki? Start one, you'll never go back.

You can also read Gawande's original article in the New Yorker magazine that his book was based on:

http://www.newyorker.com/reporting/2007/12/10/071210fa_fact_...

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.