Re: [scrumdevelopment] Re: daily status blogs
- laughing I got so involved at looking in p-logs and blogs that I forgot that I am using sharepoint team services for a lot of my project and list tracking, and using the discussions like a mini blog.heh, talk about not seeing the forrest for the trees ;)Scott Worley,Blind in the fa----- Original Message -----From: Marco AbisSent: Wednesday, February 19, 2003 12:35 AMSubject: Re: [scrumdevelopment] Re: daily status blogsMonths ago I customized a wiki-engine to let a customer of mine use it for requirements management in a collaborative way. That tool is proprietary but I uploaded an alpha-version of an open source implementation here: http://armwiki.agilemovement.it/
Development of this OpenSource version has been stopped on August 2002.....
Just to let you know about it :-)
>My current p-log plans focus on zwiki as a platform. see
>http://webseitz.fluxent.com/wiki/ProjectManagementSoftware for linky
Marco Abis - CEO & Chairman
Agility SPI: Software Process Improvement
abis@... - abis@...
To Post a message, send it to: scrumdevelopment@...
To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@...
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
> But then again, it would seem to be really hard to provide ateams
> communication/cooperation tool that would fit all the needs of diverse
> working under different conditions. Maybe that's why there is nothing outOnce upon a time, long long ago, I once asked a toy maker how he could use
> there that has managed to stick...
an online tool to facilitate communication between all parties involved in
building a toy. (If the toy is a girl doll that talks then you have clothing
designers, mold makers, mechanical engineers (the leg bone is connected to
the thigh bone, etc), embedded systems engineers, toy brokers or companies,
parts suppliers, etc. There is a long list of specialists.) He told me that
he *would not* use it. The reason it added another means of communication to
the project. And further, the communication did not allow for the transfer
of all the artifacts of the project -- examples of molded pieces for
example. His current modes of communication worked well for him and his
business. Telephone calls where handled by his assistant, postal mail came
once a day at 1pm, and FedEx came once a day at 11am. These where the points
in his day when the vast majority of people working on the project contacted
him. His day was thus mostly uninterrupted time with which he could
concentrate on the project at hand.
The principles here are that the tools should not add another mode of
communication and should not frequently interrupt your day. Most tools out
there do both. (Software folk seem to be obsessed with the clock inside
In my office text email and instant messaging (im) are the tools of choice.
To facilitate projects in my office a tool should allow communication via
email and im. For example, want yesterday's project signature send a simple
request to a chat-bot via im and have it return the signature via email (or
perhaps a URL in the im response). For example, expect to receive a project
status summary in email each morning between 7am and 9am.
Most tools want you to be in the tool's interface. I want my project
management tools to be in my communication interface.