Welcome to the 'Plogging' World
Roland Piquepaille writes "No, it's not a typo. A plog is short for 'project log' like a blog is short for 'web log.' And plogs start to be used as tools to manage projects, especially in the IT world, as discovered Michael Schrage of the MIT. He reports his findings in an article published by CIO Magazine, "The Virtues of Chitchat." Schrage found that if plogs are not really commonplace, they're not exactly rare. And they are even used to manage large IT projects, such as ERP rollouts. I totally agree with him that a plog is of great value to integrate people in a team or to keep track of the advancement of a project. And you, what's your view? If you're a project manager, do you use a plog for better control? And if not today, will you use one in the future? This overview contains selected excerpts from Schage's article which will help you to answer the above questions."
See this interesting short piece in FP about how military contractors, the Office of Naval Research and Law enforcement agencies are testing plogs on their projects and networks.
Tcd004
I recently started using Basecamp from 37Signals for tracking projects. It's basically a "plogging" system with to-do lists, milestones, file uploading, and one of the most intuitive interfaces I've ever used on the web. I've been tracking internal projects in the way described in the article--I think it's great.
It also makes it really easy to make client-extranet plogs where clients can comment on your entries. Really slick.
I'm much funnier now that I'm a subscriber.
We already have blogs, flogs, photologs, moblogs and now these plogs? Someone needs to stop making new terms up and just call them all logs.
EVERYDAY IS CATURDAY
Brings back memories, when we would check out each others' .project files... Hopefully this tool will be a little easier to manage.
Quidquid latine dictum sit, altum sonatur.
pwiki.
They make for excellent documentation both for old and for new developers/users
Richard Stallman's page would be a Freedom Log, one of many in the new flogging scene.
Could you consider SourceForge a 'plog'?
Palm Plog, pLog
Never heard James T. Kirk put an entry in the clog.
Omnis amans amens
O.K. it's time to shut off the internet. Thanks for your participation everybody.
If a web log is a blog, then shouldn't project log be a tlog?
-m
#
# Modus Ponens
#
People have been project blogging for a while. So someone comes up with the term PLOG and gets on slashdot? sigh.
-Imidazole2
I've found that WIKIs can be useful as a collaboration tool in the workplace.
It can be a free form tool to coordinate various teams and projects. Its important to bear in mind though that even the best tool is no replacement for good management.
The WIKI I'm currently using is TWIKI which is GPL'd.
all make me think of Barf's (John Candy) line in Spaceballs:
"I'm a mog. Half-man, half-dog. I'm my own best friend."
Jason Lotito
For small projects, a "Wiki" system is nice because it is informal. It is kind of like a bunch of named note-pads where anyone (given access) can edit content. It has simplified editing conventions to avoid having to type HTML. For example, a bullet point can be created (upon rendering) simply by including an asterisk at the begginning of a paragraph. (Different wikis have different conventions.)
But for larger groups a more formal "discussion group" may be more appropriate to keep track of who wrote what. These are generally hierarchical, AKA "threaded". The problem many of them have is that it is difficult to reference stuff outside of the hierarchy. They should use some kind of message numbering system so that one can easily make cross-branch references by typing in message numbers.
However, many managers are not used to such systems and are sometimes intimidated by them. Some tend to be "verbal-oriented".
Table-ized A.I.
A few months back i setup a blog to help out our team to help manage the knowledge we acquire throughtout the projects duration. My managers fourtunately approved it. Though it was well recieved throught the team, very few knew what a blog actually is and very few have actually used it. It is rather unfortunate that some employees do not do anything other than things which are manadatory. I'm sure people would have used it much more if it was made mandatory to record all their experiences but we know that it's not possible. An oft quoted excuse is time. Blogging does take time and i totally agree with that but what is not being considered is the time that would be saved by someone else who would come across the same problems after a month or two.
- a) tlog
My logic would tell me a project log was a tlog (+ it sounds way cooler =)b) plog
c) clog
I used to be able to tell when someone was fingering me. My .plan was a named pipe fed by a shell script. The script would netstat looking for fingerd connections, rsh to the source host, "ps -aux" for finger processes, and send me the results. I'd then send email to the person, asking "why are you fingering me?".