It has been trial and error in my attempt to uncover the many ways wikis can help gather and consolidate data for my blog, and my team project.
In business, I can see where this tool would be very beneficial as a manager or a team leader. Leadership is an over-all structure that relates to virtually every manufacturing and commercial type setting. Service companies have a tendency to look at managers/leaders, from beginning to end, for quickly assisting their customers, while “manufactured goods” corporations use strategies and plans to execute their core goals.
In both types of business, gizmos assist in the automation of all means of communication, organizational skills and overseeing all phases of a project. The majorities of these devices stem from innovations like project software, and transport network tools like email, teleconferencing, and other social networking systems.
As most core business processes, these instruments aid in what has now become a necessity for these companies: These systems are comprises of an information source that assist in a whole lot of communication through many channels. A lot of businesses use the shared email inboxes in their workforce, and maybe a communal folder on a network server, as we did at my previous job. We stored what seemed to be never-ending documents, accounts and comments generated during the development of a project.
Believe it or not one of the vital features of a project is the inspiration of a team. As we work together we will find many new ideas and work through the failures of other ideas. All of the team members need contact to a central source of files and comments concerning the project they are developing. As we have discovered a wiki creates a "text"book answer to that requirement.
Here are some ways that you may find viable to use a wiki in your project. Use a group project wiki, as the main source of info for the project. It is someplace team members can submit material and see what each other has proposed. Use it as a file to keep minutes, project details, and work products these can all be searched and edited when updated. All members of the team can have a page on the wiki where they can revise ideas and phases of the project daily or weekly. When the teams are not together they can still work together in their PB wiki sites. This can significantly increase the progress and improve the proficiency of the face to face meetings we will have. I can see that particularly for web projects, wikis generate an unlimited way to create screens right inside the wiki, remind yourself using comments on the page, or for personal or group feedback. I also read about a tool called Balsamiq it is a proto type tool that allows you to easily drop in images, I have not tried this yet but it could be an adventure. Another idea is to use the wiki as the mailing list for the project, if every person on the team is registered on the wiki, use the built-in "email all users” like in blackboard as an alternative to doing it manually from email. Encourage your teammates to use the wiki as an alternative to the back-and-forth process over email.
Have fun and wiki away!
