SIGIA-L Mail Archives: RE: SIGIA-L: Re: jumping in on sitemaps
RE: SIGIA-L: Re: jumping in on sitemaps
From: Surla, Stacy (SSurla_at_aspensys.com)
Date: Fri May 04 2001 - 09:44:39 EDT
Well stated. Thanks for articulating this particular role the documentation
plays. Yes, part of the purpose of diagramming the information (flow,
hierarchy, relationships) is to make a structure out of the chaos.
After reading this interchange so far, it occurred to me that back in the
old days "deliverables" were contract-specified products that we actually
delivered to the client. The work of a given project (plane trips,
meetings, data collection, memoranda, etc.) resulted ultimately in, for
instance, a "Final Report," which was the project deliverable. Okay, "Work
Plan" was usually an early deliverable too. But "project notes" and "SPSS
data runs" and "logical frameworks" were not deliverables. Nor were our
methodologies called deliverables.
Perhaps some of the tools and methods we are talking about are mis-labled if
we call them deliverables. Maybe mis-labeling them is leading to
unnecessary confusion about how best to use them.
From: Perrin Rowland [mailto:prowland_at_novocorp.com]
Sent: Thursday, May 03, 2001 6:40 PM
Subject: RE: SIGIA-L: Re: jumping in on sitemaps
... the deliverables all serve the same purpose: presenting the information
you do have so you can move to the next deliverable that shows a greater
level of detail .
... All of our deliverable are almost milestones in understanding your
information in order to push you and your team ahead in the next round of
detail. Sitemaps (etc) are high level interpretations of your data so you
can understand what loopholes or missing pieces of info you have and where
you have to pay attention to move forward.
List archives are available at:
To subscribe or unsubscribe, send mail to majordomo_at_asis.org with the
appropriate command from the list below in the body of the message:
This archive was generated by hypermail 2.1.2
: Sun Nov 23 2003 - 22:54:38 EST