Intranet Information
We should improve the level of communication we provide via
world.cwintra.com by keeping information about our current projects
up-to-date. Included in this should be contact numbers and email
addresses where appropriate.
I'll speak to Damien to find our area on world, and get working on it.
Would this be a useful thing to the business? To see us better
represented on the intranet?
posted by Adam @ 1:51 PM
5 Comments:
I've had this thought a number of times. Even got an area set up for us and author rights once. Especially the times when we are saying "we are the only developers in the world". But it never actually seems worth doing rather than say one of the other possible background tasks like fixing the Livelink bit of search on world which surely have more positive benefit and has been sitting in my inbox a few months.
I suppose what you're looking for is a nice, public reporting of activity, issues, resolution, etc. Perhaps tied in with weekly reports, even fault tracking. Somebody somewhere has solved all this with a nice bit of technology. I wonder if Google knows anything. So far I think the Wiki is the best we've done (better than using the goddamn CMS anyway).
A constructive way to think about this.
What five things am I going to put on our area of the intranet that will be useful to other people in the company.
1. Contact Details
2. Brief nontechnical description of what we do.
??
Fill in the next three please!
Alright, how about:
3) Current projects with status
4) Any available positions (link to intranet job site?)
5) Links to Service Delivery and other documentation for each project
Project status would have to pretty detailed though for it to be any use. Most people who would need/care about the status would be in the loop anyway. However the jobs section might be useful, especially if each project listed has a brief description of the technologies used... help people get a better understanding of what we do, if they're interested in development.
Not sure if theres enough people that would be interested to warrant the up-keep though?
What I see as a good solution would be a sort of message board, a section for each project, that way not only is it just a bit of information about the project (set on a template or something), but we can also use it for un-official brain storming, asking other developers if they have a solution for xxxxx etc. Or would that be too public for dev chatter? I know this can be done on the wiki, but its not a logical way to discuss something, more to provide information.
Yeah, that was one of the areas we saw the wiki covering when we first set it up, but you're right - the wiki's lack of consistant formatting means it's not as efficient as, say, a threaded discussion board. Funnily enough, me and Tom did set up a livelink discussion board ages ago, but it was never used. And thats the biggest problem something like this faces - the exposure to enough other people that it is useful. We'd really need to sell the fact that we had an intranet site and get visitors going there. If we could do that, then it'd be great
Post a Comment
<< Home