RE: [scrumdevelopment] daily status blogs
- Andrew, I really loved your story about the toy maker.
I'd say what we needed was a really good defect/issue tracking tool - and
there are several out there; plus a good library with check-in/check-out and
version control for project documents which were not source code. Again,
good tools like this exist. In trying to get more 'stuff' in a
'collaboration package', we got weak versions of everything.
Beyond defect tracking and document management, good old e-mail, IM, video
conferences and being in the same room (yes, travel!) would have been
adequate for everything else.
Lean Development: An Agile Toolkit
From: "Andrew Gilmartin" <andrew.gilmartin@...>
Once upon a time, long long ago, I once asked a toy maker how he could use
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.
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
- Mary, Andrew & list members,
Thank you very much for this intriguing thread. It's
exhilerating to be part of this discussion with an
experienced and articulate group.
The toy story and summarized list of essential needs
solidify points which I'm now glad to have words for.
They are the "round pegs for a round hole" of product
development, and factors which new tools should
compliment, not crowd or interfere. For example, an
issue tracker that immediately mails out status
changes provides localization the communication tool,
but interferance due the interruption. This
information should be available at any time, but
mailing should be configurable to a regular interval
through "digest-mode", or other summary mechanism. I
like Scrum's daily meeting for this kind of
consistency, also. Being able to change issue status
or append comments via email is another complement.
Within the past few months weblogs have gained
features for update & edit through email. Many wiki's
have had this for awhile.
I've realized that the use of weblogs and wikis more
benefit efforts of the team(community?) development
factors of knowlege management and posterity rather
than essentials for product development. I'm looking
forward to the p-log spin-off.
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
- I agree.
My current p-log plans focus on zwiki as a platform. see
http://webseitz.fluxent.com/wiki/ProjectManagementSoftware for linky
--- In email@example.com, Dean Goodmanson
> I've realized that the use of weblogs and wikis more
> benefit efforts of the team(community?) development
> factors of knowlege management and posterity rather
> than essentials for product development. I'm looking
> forward to the p-log spin-off.
- Months 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. seeMarco Abis - CEO & Chairman
>http://webseitz.fluxent.com/wiki/ProjectManagementSoftware for linky
Agility SPI: Software Process Improvement
abis@... - abis@...