NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Page info
title
title

Panel
titleContents of this Page
Table of Contents
minLevel2

Project Summary

Project Name

Knowledge Repository

Start Date

March 1, 2010

Primary Contractor

SemanticBits, LLC

Current Stage of Project

Version 1

Related Documentation

Include Page
seminfra:Knowledge Repository Documentation Table
seminfra:Knowledge Repository Documentation Table

Points of Contact

Role

Name

Organization

Phone

Principle Investigator

Ram Chilukuri

SemanticBits

703-787-9656 x247

Project Director

Joshua Phillips

SemanticBits

410-624-9155

Project Manager

Beate Mahious

SemanticBits

443-797-5462

Vision and Scope

See our Vision and Scope Document

Success Factors

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

...

  • 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. Checkout 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:

image of project schedule timelineImage Modified  

Deliverable Schedule

Include Page
seminfra:Knowledge Repository Deliverable Schedule
seminfra:Knowledge Repository Deliverable Schedule

Deliverable Artifacts

Include Page
seminfra:Knowledge Repository Deliverable Artifacts
seminfra:Knowledge Repository Deliverable Artifacts

Estimated Cost at Completion

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

Staffing

Include Page
seminfra:Knowledge Repository Team
seminfra:Knowledge Repository Team

Risk Identification

Include Page
seminfra:Knowledge Repository Risk Matrix
seminfra:Knowledge Repository Risk Matrix

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

diagram of change control processImage Modified
 

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.

...