[22] in Project_DB
Re: restrict issue categories?
daemon@ATHENA.MIT.EDU (Bill Cattey)
Mon Feb 24 16:30:57 1997
Date: Mon, 24 Feb 1997 16:29:26 -0500 (EST)
From: Bill Cattey <wdc@MIT.EDU>
To: tjm@MIT.EDU (Tim McGovern), brlewis@MIT.EDU (Bruce R. Lewis)
Cc: project-db@MIT.EDU
In-Reply-To: <nm9vi7iar9v.fsf@kindness.MIT.EDU>
I am the one who specified a restricted set of categories for the issues log.
What made it in the database was a mis-transcription of what I specified.
Hanging a category off an issue was something that came in from the IPS
project management methodology I studied. The two categories given were
"Customer" and "Supplier". What they are about is: Did WE think of
this issue as we began implementing it? or Did THEY (the customer) come
think of this issue as they watched the project unfold.
In the course of evolving the project database, somebody must have
thought that "category" was a nice way to sort out issues.
Tim: Do you think we should have a category for issues?
Do you think it makes sense to even make a distinction of the
developer/supplier versus the customer in naming issues?
Sorry to leave such a philosophical question for so long. I should have
checked in on these little things earlier.
-wdc
