More on Wikis: Wikis for Requirements

March 6, 2007

I’ve been working on a section about gathering requirements when you’re acquiring technology, and it occurred to me that this might be another place where a Wiki could be useful.

The basic idea would be to use the Wiki as a place to gather and prioritize “raw” requirements and carry on a discussion about them.

I see several benefits:

  • You keep everyone up-to-date on what you’re doing, so there’s no excuse for anyone to complain about requirements being developed in secret.
  • You’re less likely to miss an important requirement.
  • You get a broad-based view of priorities.
  • You start the buy-in/change management process early.

I see two potential downsides:

  • It may be harder to get negative comments unless you provide an alternate, private mechanism for people to give input.
  • You run the danger of channeling people into a “Group Think” situation, where alternate opinions get buried or never spoken. That might argue for starting the Wiki only after you’ve gathered an initial set of requirements through interviews or other more traditional processes, and for providing a private mechanism for comments as described above.

Has anyone tried using a Wiki for writing requirements? Comments on your experience or thoughts in this area are welcome.


One comment

  1. […] Wikis can be used for a lot of things, including requirements. […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: