Attendees
Sarah, Dan, Aaron H, Dave, Kevin, Rina, Butch, Tony, Steve S
Objective
Develop a schedule for execution of the work necessary to successfully launch the PPI-1
Notes
Bodies of work to content with:
- Communication
- Security, provisioning
- Identity Service Integration
- Data Conversion
- Data Mapping
- Environment(s)
- Batch Processing
- QA
- Testing
- Implementation and operations
- User Training
- ID&R and reporting
- Feedback
Communication
- Identify stakeholders
- Dave's contacts (users), liasions
- Communicate launch, progress, schedule
- User expectation setting
- Validation process
- Time and effort commitments
- Issue vetting, response time
- Roles and Tasks (who will do what)
Security, provisioning
- Define roles (new PPI-1 role)
- Identify users (see functional requirements document for current list, number may increase)
- Alter data conversion (impact to be assessed)
- No workflow
- Testing
- Can users do what they need to do?
- Can users NOT do what they are not supposed to do?
Identity Service Integration
- Validate stand alone Cynergy with Identity
- Roll out validated build and test
- Deal with related OI (Data conversion etc)
Data Conversion
- Complete rules for converting balances
- Endowment underway
- Plant account next
- Validation of these rules for converting balances
- Complete mappings and rules for other required chart attributes
- Account, object code etc
- Validation of these rules for other required chart attributes
- Deal with any user provisioning
- Rules for other charts (post PPI-1 launch)
- Plan for future customizations
Data Mapping
- Define end-user need
- Fit gap against existing spreadsheets and audit tables
- Do something, deliver something, operationalize
Environment(s)
- Cynergy (stand alone) latest build deployment
- Data conversion automation
- Data Movement
- Snapshot after data conversion, after batch, move to PPI-1 and ID&R staging
- Automation of this snapshot
- Validation process
- Build and deploy DCP
- Roll back process
- Dev (done?), prove, practice
Batch Processing
- Run two batches (Nominal Close, Beginning Balance Fund)
- Determine if they'll be run via GUI or automate using comment line
- Who is going to run it?
- Add in automated script in the data conversion?
- Validation
- Logs and reports generated- interpreting them
- Define success critetia
QA
- For all functional processes, define success criteria, ID stakeholders
- For all technical processes, define success criteria, ID stakeholders
- Define use cases that will prove success criteria
- QA tools (JIRA, test management, environment)
- Identify and create test cases
- Load testing - whether it is required
User Training
- Identify users
- Define use cases
- Determine training requirements
- Develop required material
- Execute
ID&R and reporting
- Define requirements
- Modeling
- ETL
- Dashboard development
- Validation
- Training
- Rollout
- Support/ Maintenance
- Feedback process
Feedback
- Process for end user service
- KFS and OBIEE
- Tools (JIRA, special mailbox)
- Issue management and customer service plan
Action Items
Action Required |
Responsibility |
Target Date |
---|---|---|
Acceptance criteria for PPI-1 functionality |
Dave, Tony, Rina |
5/17 |
Specific list of required chart attributes that must be validated for PPI by the date of rollout |
Steve, Dave |
5/13 |
Rina, Dave |
5/13 |
|
Review notes from refresh process (ie, the repeatable process we'll follow each time we update the balances) meetings. |
All attendees |
5/11 |
Publish FY10 accounting calendar with respect to our conversion process |
Dave |
5/11 |
Identify which ADW balances to pull and when |
Dave, Steve, Rayna, Rina |
5/17 |
Dave |
5/10 |
|
Production support Plan |
Open |
|
Attendees to work on own milestones and deliverables based on review of these meeting notes |
All attendees |
5/11? |
Schedule and Milestones
Date |
Milestone |
Notes |
---|---|---|
5/10/2010 |
Today |
|
Week 1 |
Data conversion mapping rules complete, including chart attributes and balances |
|
Week 2 |
Balance tables populated according to rules |
|
Week 3 |
|
|
Week 4 |
PPI-1 Functionally validated |
Major Milestone |
Week 5 |
|
|
6/01-6/15 |
Slush |
|
Week 6 |
Data Mapping freeze |
|
6/15-6/25 |
Functional validation (QA and UAT period) |
|
Week 7 |
Validated conversion for 7/01/2010 release |
|
6/25/2010 |
UAT Completed, Real freeze |
|
6/25-7/1 |
Stasis period |
|
Week 8 |
PPI-1 Launch Date (beginning balances not available) |
Major Milestone |
7/28/2010 |
Functional FY10 Close, creation of FY11 Beginning Balances |
|
7/30/2010 |
|
|
Open Issues (responsible persons)
- Data conversion and user provisioning (Sarah, Steve, Aaron)
- one data conversion process
- convert all as we do for current environment and remove roles after
- Data Mapping for end user requirements (Rina, Dave)
- Load test for PPI-1? (Tony)
- Sort out issues for data mapping freeze 6/15 (Steve)
- Define ID&R milestones (Dave, Rayna, Butch)
Parking Lot
None