Objects by Design Forums Here you can view your subscribed threads, work with private messages and edit your profile and preferences Registration is free! Calendar Find other members Frequently Asked Questions Search Home  
Objects by Design Forums : Powered by vBulletin version 2.3.5 Objects by Design Forums > Main Forums > Agile Software Development > Agile Tip #3: Using a Wiki Thread Rating: 2 votes, 5.00 average.
  Last Thread   Next Thread
Thread Post New Thread    Post A Reply

Registered: Apr 2001
Location: New York
Posts: 492

Agile Tip #3: Using a Wiki

Agile development requires rapid, collaborative development.

We've found that one of the most effective mediums of communication for collaborative designs is the wiki.

A history of the wiki can be found at Ward Cunningham's site.

The most powerful example of the wiki's potential is Wikipedia, the largest online encyclopedia in the world.

A wiki allows users to rapidly create web pages using a simple editing notation, which is far easier to use than native HTML. The web pages may be hyperlinked and images may be embedded in pages. The wiki pages are stored in a database such as MySQL, allowing easy backup and maintenance.

We collect requirements, analyze data flows, make lists of refactorings, create database modeling designs, and analyze performance problems all using a wiki. In fact a wiki page is the first artifact created for any new development.

When combined with NetMeetings , wikis become even more powerful, allowing a group of people to jointly edit any of the above artifacts. Business owners love this combination because it allows them participate in the development process at a level in which they can contribute.

Report this post to a moderator | IP: Logged

Old Post 08-30-2005 04:29 AM
SZ is offline Click Here to See the Profile for SZ Click here to Send SZ a Private Message Visit SZ's homepage! Find more posts by SZ Add SZ to your buddy list Edit/Delete Message Reply w/Quote
Junior Member

Registered: Jan 2004
Location: Portugal, Algarve
Posts: 3

At my department (telco management software systems development) we started using an internal wiki some months ago, after a trial in one big project during one year. I've seen it being very productive in some projects (like in the original trial project) while in others it isn't, due to lack of participation of developers.

The main problem is that some sub-cultures consider anything other than code and human driven testing being wasted time and sign of under allocation of human resources... You also must have hard-writing sharing spirit. So, if a developer doesn't write commit (or check in) comments he probably won't contribute to the wiki.

As with many other things, a wiki is a tool, but, you must address first - or in parallel - the "being agile" and human training / convincing part of the equation first...

That said, in all the projects I'm involved since we setup a wiki infrastructure (based on tikiwiki), none lacks a wiki page! I work it out and cross my fingers waiting for others to find it useful and start contributing.

Report this post to a moderator | IP: Logged

Old Post 08-30-2005 08:53 AM
euluis is offline Click Here to See the Profile for euluis Click here to Send euluis a Private Message Find more posts by euluis Add euluis to your buddy list Edit/Delete Message Reply w/Quote
All times are GMT. The time now is 12:45 AM. Post New Thread    Post A Reply
  Last Thread   Next Thread
Show Printable Version | Email this Page | Subscribe to this Thread

Forum Jump:
Rate This Thread:

Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF

< Contact Us - Objects by Design >

Powered by: vBulletin Version 2.3.5
Copyright ©2000 - 2018, Jelsoft Enterprises Limited.
Copyright 1999-2005, Objects by Design, Inc.