Page info
title title

Project Summary

Related Documentation

Points of Contact

Vision and Scope

See our Vision and Scope Document

Success Factors

Factors that should be met to achieve overall success of the project include:

• Meet all the use cases laid out in the proposal and the use case document.
• Deliver a system that is deployable and usable by the community.
• Meet all deliverables on-time and on-budget.
• Meet all requirements in the SRS document.

In the Elaboration Phase, we met the following high-level goals:

• Elaborated high-level use cases for the majority of the system.
• Created an architectural baseline that involved industry standard software platforms.
• Implemented the high priority use cases.
• Began the testing process.

In the Construction Phase, we have the following high-level goals that will determine success:

• Flesh out the rest of the use cases with detailed requirements.
• Complete the architecture.
• Complete the implementation.
• Complete the core testing process.

In the Transition Phase, we have the following high-level goals that will determine success:

• Deploy the production version of the project at NCI.
• Complete the user acceptance/system testing.
• Train end-users where appropriate.
• Complete all end-user documents.

Project Dependencies

TBD

Activity List and Schedule

In line with our Agile development methodology, we have adopted a modified version of Scrum. Check out our Product Backlog of prioritized features and our Sprint Backlogs. We also maintain a Microsoft Project Plan.

The following is a high-level overview of the schedule:

Deliverable Schedule

Refer to Knowledge Repository Deliverables.

Deliverable Artifacts

Refer to Knowledge Repository Deliverables.

Estimated Cost at Completion

This is a time and materials project. Consult the SOW and contract proposal for budgetary items.

Staffing

Risk Identification

Configuration/Change Management Plan

Change Control Process

Change requests will be directed to the CM manager. They will be documented in a single Excel file sorted by date and coded/annotated for the type of change requested, the reason for the request, impact of the change requested to current phase of project, original and estimated new timeline, resources and cost and the requester's name. The outcome of the review of the request will also be documented, including from whom input was sought, if necessary, and the decision to grant the request or make a compromise. The Technical Point of Contact is considered a stakeholder, and so all modifications will be reviewed with him during regularly scheduled C3PR teleconferences. The NCI CCB is not considered a stakeholder. It is expected that changes with high impact will be identified as risks and will be elevated to SAIC/NCI by the TPOC as he sees fit.

Change Control Workflow

Technical Change Control

Prior to a release, the CM manager will review the deliverables leading to the release and ensure that issues identified in the testing phase have been addressed. This review will be presented to the project PI and the additional CM staff members, who will suggest potential problem areas to be tested.

Weekly JIRA Exports

We are using JIRA (v4.0.2#472) instance that is hosted at SemanticBits (http://krjira.semanticbits.com) until the NCI's Jira server is ready. Weekly exports of that instance are below.

• Week of April 4th