Building a Project Website the Easy Way
March 18th, 2003 by HalBuilding a project Web site the easy way by William T. Kelly. Covers all the basics. Encourages the use of standard templates from MS FrontPage and Macromedia Contribute.
Kelly offers these three reasons to create a project website:
- A central user interface connects project team members to such project information as the requirements and design documents, functional specifications, and other documentation. The site provides a repository that is available to all team members.
- It provides centralized scheduling information.
- A library of project information is available for ready inspection/review by senior management and other selected stakeholders.
The author misses one of the most important issues. Teams tend to drift off of purpose. A project website is a place for maintaining the "story" of the project.
The author makes no mention of daily status weblogs or project weblogs. What could be easier than a weblog? See my posting and the P-Log specification.
Related Posts
- Start Sharing Your QnEKs The Quick-n-Easy-Kaizen community website is ready for wide use. Stop by to see what others have posted. Share one o...
- The QnEK Horse Has Left the Barn The QnEK Horse Has Left the Barn Quick and Easy Kaizen is said to be the direct inheritor of kaizen teian -- a progr...
- Almost Done Is 100% Not Done Marlon Sanders, the father, the inventor of the two-page website, and one of the more successful online marketers, has...
- Quick ‘n Easy Kaizen: Winning with Project Kaizen The team that shoots more through the season wins more games. There isn't an easier project kaizen approach than Quic...
- QnEK, It’s a Community Thanks go out to Joe Ely for spreading the word on the Quick-n-Easy-Kaizen community. A few people have been sharing ...
March 20th, 2003 at 4:10 pm
A wiki-powered intranet makes it muchmore likely that such documents gets refined and kept current.
http://webseitz.fluxent.com/wiki/WikiForCollaborationWare
March 21st, 2003 at 1:44 am
Bill,
Thanks. I’ve read your paper before. I’ll go back and read it again. In the meantime, what is it in particular about Wikis that make them more suitable for the project environment than group blogs? Also, blogging has exploded. Are we seeing in your opinion a VHS vs Betamax thing going on here? Wikis are technincaly better, but the world is moving to blogs?
Hal
March 28th, 2003 at 6:43 am
I see the key advantages of Wiki being
* it encourages you to put all project docs right in the docspace, whereas blogs often drive longer documents to attachments. This allows/encourages any team member to makes changes as appropriate. It also encourages breaking up longer documents into logical pieces which are more easily scanned. And a single Search returns both reference docs and blog entries.
* all such documents get cross-linked more heavily than in blogs. Likewise, blog entries can refer to a number of longer documents.
* more naturally multi-user
I’m not sure the VHS/Betamax analogy works. A single team won’t use both at the same time, but other than that I don’t see a big lock-in or networking-effect issue.
April 1st, 2003 at 6:22 pm
Thanks Bill. It’s time for me to update my p-log comments. I’ll direct folks to your comments and Twicki.