|
|
| (5 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | Project managers can benefit from a powerful web service called wiki. Wiki, which means quick in Hawaiian, is simply a website that allows people to edit its contents. One common wiki application is the free internet encyclopedia, Wikipedia.<br>Unlike traditional static web pages, that can only be read, a wiki can be readily accessed by everyone, everywhere and they can add, edit, delete, append and update content. <br>Project managers can utilize this tool to transform the project office into a live and ubiquitous environment. A project wiki can facilitate the following tasks:
| |
| | | | |
| − | <br> | + | = About Wikis<br/> = |
| | | | |
| − | *Project Meeting Agendas and Minutes
| + | Project managers can benefit from a powerful web service called wiki. Wiki, which means quick in Hawaiian, is simply a website that allows people to edit its contents. One common wiki application is the free internet encyclopedia, [http://www.wikipedia.org/ Wikipedia].<br/>Unlike traditional static web pages, that can only be read, a wiki can be readily accessed by everyone, everywhere and they can add, edit, delete, append and update content.<br/> |
| − | *Collaboration on Project Documentation
| + | |
| − | *Solicit and Keep Track of Ideas
| + | |
| − | *Project Dashboard (Project Vital Signs)
| + | |
| − | *Calendars
| + | |
| − | *Project Photo Albums
| + | |
| − | *To-Do Lists
| + | |
| − | *Establish a Project Office Intranet
| + | |
| | | | |
| − | <br>'''Project Transformation'''<br>To demonstrate the power of wikis, a project manager can post to the wiki a proposed meeting agenda, inviting direct input from team members, thus saving tedious e-mail messages and phone calls or preliminary meetings. Once the meeting is conducted, proposed minutes are posted for input and comments, almost eliminating the need for a PM meeting scribe. In one case, this resulted in reducing e-mail traffic volume by 75%, and slashed meeting time in half, thanks to group input and collaboration.<br>''Table 1 shows a comparison between traditional PM emphasis and the one offered by the wiki collaborative environment.'' | + | <br/> |
| | | | |
| − | {| border="1"
| + | |
| − | |-
| + | = How to Use a Project Wiki<br/> = |
| − | | Table 1
| + | |
| − | | <br>
| + | Project managers can utilize this tool to transform the project office into a live and ubiquitous environment.<br/> |
| | + | |
| | + | <u>A project wiki can facilitate the following tasks:</u><br/> |
| | + | *Project meeting agendas and minutes<br/> |
| | + | *Collaboration on project documentation<br/> |
| | + | *Solicit and keep track of ideas<br/> |
| | + | *Project dashboard (project vital signs)<br/> |
| | + | *Calendars |
| | + | *Project photo albums<br/> |
| | + | *To-Do lists<br/> |
| | + | *Establish a project office intranet<br/> |
| | + | |
| | + | |
| | + | = <br/>Project Transformation<br/> = |
| | + | |
| | + | To demonstrate the power of wikis, a project manager can post to the wiki a proposed meeting agenda, inviting direct input from team members, thus saving tedious e-mail messages and phone calls or preliminary meetings. Once the meeting is conducted, proposed minutes are posted for input and comments, almost eliminating the need for a PM meeting scribe. In one case, this resulted in reducing e-mail traffic volume by 75%, and slashed meeting time in half, thanks to group input and collaboration.<br/> |
| | + | |
| | + | <br/><u>The table shows a comparison between traditional PM emphasis and the one offered by the wiki collaborative environment:</u><br/> |
| | + | |
| | + | {| border="0" style="width: 100%" |
| | |- | | |- |
| − | | Traditional PM Emphasis | + | | style="background-color: rgb(204, 204, 204)" | Traditional PM Emphasis<br/> |
| − | | Project Wiki Emphasis | + | | style="background-color: rgb(204, 204, 204)" | Project Wiki Emphasis<br/> |
| | |- | | |- |
| − | | Centralization | + | | Centralization |
| | | Decentralization | | | Decentralization |
| | |- | | |- |
| − | | Authoritarian | + | | Authoritarian |
| | | Collaborative | | | Collaborative |
| | |- | | |- |
| − | | Hierarchy Organization | + | | Hierarchy Organization |
| | | Flat Organization | | | Flat Organization |
| | |- | | |- |
| − | | Project Manager | + | | Project Manager |
| | | Project Team | | | Project Team |
| | |- | | |- |
| − | | Permission Required | + | | Permission Required<br/> |
| | | Empowerment | | | Empowerment |
| | |- | | |- |
| − | | Central Files | + | | Central Files |
| | | Project Intranet File Cabinet | | | Project Intranet File Cabinet |
| | |- | | |- |
| − | | Hard Copy Documents | + | | Hard Copy Documents |
| | | Documented Digital Media | | | Documented Digital Media |
| | |- | | |- |
| − | | Limited/Restricted Access | + | | Limited/Restricted Access |
| | | Organized/Unlimited Access | | | Organized/Unlimited Access |
| | |- | | |- |
| − | | Local Access | + | | Local Access |
| | | Global/Live Access | | | Global/Live Access |
| | |- | | |- |
| − | | Rigid PM Policies | + | | Rigid PM Policies |
| | | Flexible/Adaptable Policies | | | Flexible/Adaptable Policies |
| | |- | | |- |
| − | | Limited Communication | + | | Limited Communication |
| | | Unlimited Communication | | | Unlimited Communication |
| | |} | | |} |
| | | | |
| − | We should stop viewing projects as merely an opportunity for management authority but rather model them and interact with them as empowered teams in a live and realistic view. The proposed transformation is shown in the following figures:<br> | + | <br/> |
| | + | |
| | + | We should stop viewing projects as merely an opportunity for management authority but rather model them and interact with them as empowered teams in a live and realistic view. |
| | + | |
| | + | <u>The proposed transformation is shown in the following figures<ref name="Project Management Wiki! Everything, Everywhere and Everybody’s Project By Dr. Kifah Jayyousi">Project Management Wiki! Everything, Everywhere and Everybody’s Project By Dr. Kifah Jayyousi</ref>:</u><br/> |
| | + | |
| | + | {| cellspacing="1" cellpadding="5" border="1" style="width: 100%" |
| | + | |- |
| | + | | [[File:Authoritative Model - Traditional Team.JPG|center|299px|Authoritative Model - Traditional Team|alt=Authoritative Model - Traditional Team]] |
| | + | | [[File:Collaborative Model - Empowered Team.JPG|center|359px|Collaborative Model - Empowered Team|alt=Image:Project_wiki_2.gif]] |
| | + | |} |
| | + | |
| | + | {| cellspacing="1" cellpadding="5" border="1" style="width: 100%" |
| | + | |- |
| | + | | style="width: 332px" | Authoratative Model - Traditional Team<br/> |
| | + | | style="width: 401px" | Collaborative Model - Empowered Team<br/> |
| | + | |} |
| | + | |
| | + | <br/> |
| | | | |
| − | [[Image:Project wiki 1.gif|Image:Project_wiki_1.gif]][[Image:Project wiki 2.gif|Image:Project_wiki_2.gif]] | + | [http://www.allpm.com/modules.php?op=modload&name=News&file=article&sid=1606&mode=thread&order=0&thold=0 -> Find more Information here: Project Management Wiki! Everything, Everywhere and Everybody’s Project] By Dr. Kifah Jayyousi |
| | | | |
| − | Source: [http://www.allpm.com/modules.php?op=modload&name=News&file=article&sid=1606&mode=thread&order=0&thold=0 Project Management Wiki! Everything, Everywhere and Everybody’s Project] By Dr. Kifah Jayyousi
| + | == A Picture says more than 1000 words - Wiki collaboration<ref name="wikinomics.com by Anthony D. Williams">wikinomics.com by Anthony D. Williams</ref> == |
| | | | |
| − | == A Picture says more than 1000 words - Wiki collaboration ==
| + | [[File:Wiki collaboration2 1 wikinomics.jpg|center|450px|Wiki collaboration]] |
| | | | |
| − | [[Image:Wiki collaboration2 1 wikinomics.jpg]] | + | -> Further Information: |
| | + | *[http://www.wikinomics.com/blog/index.php/2008/03/26/wiki-collaboration-leads-to-happiness/ wikinomics.com] by <span class="author_name">Anthony D. Williams</span> |
| | + | *Interesting [http://www.gartner.com/it/page.jsp?id=1215930 Article] regarding file-oriented and document-based vs. web 2.0 and wikis. __NOAUTHORLIST__ |
| | + | <br/> |
| | | | |
| − | Source: [http://www.wikinomics.com/blog/index.php/2008/03/26/wiki-collaboration-leads-to-happiness/ wikinomics.com] by <span class="author_name">Anthony D. Williams</span>
| |
| | | | |
| − | <br>
| |
| | | | |
| − | Interesting [http://www.gartner.com/it/page.jsp?id=1215930 Article] regarding file-oriented and document-based vs. web 2.0 and wikis.
| + | <references /> |
| | | | |
| − | [[Category:Basics]] | + | [[Category:MyWiki]] |
Project managers can benefit from a powerful web service called wiki. Wiki, which means quick in Hawaiian, is simply a website that allows people to edit its contents. One common wiki application is the free internet encyclopedia, Wikipedia.
Unlike traditional static web pages, that can only be read, a wiki can be readily accessed by everyone, everywhere and they can add, edit, delete, append and update content.
Project managers can utilize this tool to transform the project office into a live and ubiquitous environment.
To demonstrate the power of wikis, a project manager can post to the wiki a proposed meeting agenda, inviting direct input from team members, thus saving tedious e-mail messages and phone calls or preliminary meetings. Once the meeting is conducted, proposed minutes are posted for input and comments, almost eliminating the need for a PM meeting scribe. In one case, this resulted in reducing e-mail traffic volume by 75%, and slashed meeting time in half, thanks to group input and collaboration.
We should stop viewing projects as merely an opportunity for management authority but rather model them and interact with them as empowered teams in a live and realistic view.
