[355] in Tooltime
Scopus Status Report 12/13/96
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Mon Dec 16 17:38:22 1996
Date: Mon, 16 Dec 1996 14:41:11 +0100
To: tooltime@MIT.EDU
From: Steven Wade Neiterman <wade@MIT.EDU>
Working On Milestone:
- Transition to rollout continues with minor release 1.0 changes,
review of migration and activity tasks, release 2.0 pre-planning
- Customer decided best rollout window is early in IAP (January, 1997)
- Next milestone after rollout is a transition of Release 1.0 from
Delivery to Service.
Accomplishments:
- Completed refinement of Filemaker data load (linefeed problem) 11/25
and identification of Filemaker software/hardware codes (11/17)
- Acknowledged update of Scopus documentation (Scopedia) (11/25) and
design tools (ScopusWorks) 12/3 and installation of Oracle tables (12/6)
required by ScopusWorks
- Completed first pass at work breakdown structure for rollout tasks (12/3)
- Completed first pass at release 1.0 bug/comment list (12/5)
- Completed install of SGI Scopus and Design Team clients (12/13)
- Completed re-location for release 1.0 development resource (12/13)
- Completed rev 6 of training guide and 1.0b8 of programmers Guide (12/13)
- These items are in progress:
- Began installing password changing program and reviewing process
- Progress made towards migration issues - notification 12/10,
continued with minor changes to release 1.0b8 for taken field and
child status errors, .. as described in rollout plan
- Began work on cleaning and preparing Filemaker data for load
- Began installing ScopusWorks on 32bit platform (12/10)
- Refined checklist and training plan for technology transfer (12/10)
and conducted dev. team meet (12/9, 12/11) - continue with training
- Created next rev of Programmer's Guide and had dev. team review (12/13),
continue with final version of guide 12/31
- Training document revision 6 completed (12/10), waiting for feedback,
produced final version by 1/7/97
- Research into Brio Query for procurement and assessment of needs and
creation of reports continues
- Continued with data gathering for reported release 1.0 bugs/comments
- Continued with evaluation of production machine, e.g. account cleanup
- Continued with work environment evaluation, technology transfer with
additional development resource
Goals:
- Complete release 1.0 by 12/20, with warehouse lookup bug to be resolved
- Remaining migration tasks include finalize training format, follow up
on four outstanding Macintosh client issues with Scopus, post release
1.0 issues of client deployment refinement, warehouse feed automation,
training and programmers document, begin service plan document.
- Investigate purchase of Customer Care Maintenance contract
- Continue technology transfer implementation
- Continue building tasks, issues and problem resolution items for R2.0,
including charter, vision statement, scope and work breakdown
- Continue with production and test machine management -
cleanup, data export/import, automated warehouse feed, refine
SLA with Facilities Management on production machine, installing SNS
- Continue to refine criteria for rollout and migration tasks/schedule
- Continue with problem resolution, Macintosh client, InformTEAM,
obtain latest documentation/software
Longer Term Goal:
- Gather enough information to build a scope statement and work breakdown
for release 2.0.
- Continue to build release 2.0 implementation team
Issues:
- Conversations with Scopus on Secure Network Services have been escalated.
Last word is that it would be corrected before end of year.
- Identified problem with Macintosh OpenTransport 1.1.1 and higher with
SQL*Net 1.5 and thus the Macintosh Scopus client
- Increased development staff requires greater emphasis on source control
and items involved in release management, such as testing, quality
assurance, customer acceptance and release cycle.
- Possible visit by Scopus Customer Care Representative in January '97 to
review outstanding issues and evaluate futures.
- Post release 1.0 issue is to determine if Scopus a good value? This is
based on cost, functions provided, skills required to maintain and develop
the product, other departments/processes that may want to implement Scopus,
future direction of the company.
