Sep
28

Medicaid PESP Status Report – Sept 27, 2012

Hi All: Hope everyone is having a good week.  Highlights for the week include:

1. Risk to the timeline due to the late provision of a significant number of provider organizations added recently.

2.  Topcoder is actively working to fix the judging bundle download issue, that is slowing down our ability to share final assembly (and other large contest files) with client.

3.  IBM license test suite requires significant time to build and test POC.  As well, there is always the possibility that the tests will show that further design/build work is required.

4.  UI wireframes do not yet reflect changes requested by client to remove items.  These changes will be made in the next 1-2 weeks via short bug races.

5.  There are a relatively large number of contests running in Sept and Oct that will require client and topcoder input jointly.

For the full report, please see below.  If you have any questions or comments, please let us know.
Thanks
Sarah

 

 

Project Status Report

Project   Name: Prepared   by: Period   Ending:
Medicaid Provider   Screening Portal Sarah   Ramkissoon/Andy LaMora 27-Sep-12


Executive Summary

Item Comments
Overall
  •   On track   to Q4 Implementation
Scope/Quality
  •   On track
Schedule
  •   Risks emerging – see details in Risks and Issues section
Budget/Resources
  • On track – see details in budget section
Contest Management
  • On track – approximately 25 contests remaining in Sept – Oct

Upcoming Milestones/Deliverables Summary

Project Milestones/Deliverables

Estimated End

Revised  End

Status

Reference

Complete Workflow   for All Providers

Mid-Oct

Stable

r1

Administrative   Workflow

Early-Oct

Stable

r1

UI wireframes (all)

Mid-October

Stable

r1

Prototype

October

Stable

Bugs

Ongoing

Stable


Upcoming Activities

Work Required  - Sponsor
Sep 28 – Oct 14:

  • Requires client time, input and assistance to:
    • Review of Services Module         (architecture) and integrated external sources assembly contests
    • Review of UI prototype and updated         wireframes
    • Review of Administrative features         and business rules specification contests
    • Discuss timing and skill set of         client resources required to support review of architecture proposal to         send and retrieve data from mainframe.
  • Monitor forums

Oct 14– Oct 21:

  • Continue review of UI components        (storyboards and prototype), architecture and assembly contests
  • Review proof of concept contest        results for JPBM 5 and WAS updates
  • Continue discussion on open issues.
Work Required –   Topcoder
Sep 28 – Oct 14:

  • Multiple architecture, UI, assembly and bug hunt contests in progress
  • Create        overall site design summary walk-through
  • Ensure client        SME resource alignment and availability to meet key milestone deadlines
  • Work with client to resolve        outstanding questions and issues.

 

 ISSUES and RISKs Summary

Ref #

Description

Reported Date

Action By Date

Status

i3

Issue: Client is   concerned that feedback to UI wireframes are not being reflected in the final   product (there are items to be removed).Action:  Topcoder plans to run a series of short bug   races to make the required changes.    The changes expected to be completed in the next two weeks, and will   be available for review then.

09-26-12

10-08-12

Open

r1

Risk: A significant   number of new provider organizations have been provided by client in mid-late   September timeframe.  As a result the   time to complete the UI wireframes that included these new organizational   types has increased.Action:  Run the required organizational wireframes   contests as aggressively as possible, including in parallel where possible,   or with very short periods between contests where parallel is not possible.

09-20-12

10-21-12

Open

r3

Risk:Topcoder is currently experiencing technical   difficulties with the software that allows for downloading of judging bundle packages.   In particular assembly contests results are affected.  It is slowing down our ability to provide   the client with the assembly contests results to reviewAction: Topcoder staff are working on getting the issue   resovled with highest priority. 

09-20-12

09-20-12

Open

r5

Risk:IBM License test requires time to conduct test and   review results. If the results are not as expected, a new/alternate   strategy/discussions may be requiredAction: Expedite testing by using an IBM copilot to set up   smart clouds, enabling POC testing on the IBM stack.

09-20-12

01-21-12

Open

i2

Issue:  Strategy to   address licensing for IBM assets requiredAction:  Feedback on the elements to port provided by   client.  Creation on contest to port   elements to IBM stack in progress 07-26-12

08-31-12

Closed

r2

Issue:  Developers   require API access to 3rd sites to check for licensing and other   authorization information.  Also concerns where there are expiration dates for licenses, licensing information is not available or if there is use of CAPTCH or other technologies that prevent easy reading of data on the 3rdparty external site. Update (Aug 16, 2012):  MN DHS and CMS (state and federal health agencies   respectively) are looking into getting API access.Alternate:  Create  well-formatted   private web pages that allows for screen-scraping, and query with querystring   tokens, post, etc 07-26-12

08-23-12

Closed

i1

Issue:  Strategy   required on IBM stack vs. generic stackResolution: Build two POCs ( “hello world”   applications) and implement open source stack version.  Client will then prioritize elements to   port to the IBM stack

07-12-12

07-31-12

 Closed

Project budget update  

Ref #

Description

Comments

1

-  Estimated   forecast for Sept – Oct: $95,000

n/a

2

Actual contest cost to date: $266,595

Budget   on Track as Expected

 

Completed Activities

Completed   Activities (Sept 14 -  Sept 28)
  •   Multiple   assembly, UI, architecture and bug hunt contests launched or in review
  •   Specification   contests launched to determine business rules and document use cases