|
As I
mentioned during today's call, I have the following problems with the Technical
Writer Statement of Work.
- The
nature of the work to be completed far exceeds the role of a Technical Writer.
A Tech Writer ("scribe") is undoubtedly needed for a project of this scope,
but it will also require an architect, designer, or someone with a
broader grasp of the technology (which I note isn't specified) and how it can
be applied to the business problem.
- The
deliverables described in the SOW are dependent on things to be produced
by the TC (see for instance tasks 1a, 1b, 2a, 2b, and 3b). I suggest the TC
deliver these things before hiring anyone because (1) they are
essentially on the critical path for the project, so any delays will affect
project deadlines, (2) many of them should probably be reviewed and approved
by the TC as a whole, and (3) they could be useful in screening
candidates.
- The
SOW speaks of consolidating use cases, but by themselves use cases do not
constitute the formal requirements that I suggest are appropriate for a
project of this significance - which, after all, hopes to produce a national
standard. A requirements document normally specifies many things that aren't
made explicit by use cases.
- The
scope of the project's deliverables isn't clear: I assume it includes Filing
and some sort of Confirmation, but does it also include Policy,
Query-Response, or an API?
- Given
the above, I suspect the time frames are unrealistic.
TJS
I apologize for not including this
with the email for the teleconference meeting tomorrow.
John M.
Greacen
Greacen Associates,
LLC
HCR 78,
Box 23
Regina,
New Mexico
87046
505-289-2164
505-289-2163
(fax)
505-780-1450
(cell)
|