P&RA Retrospective - R2

Get Started. It's Free
or sign up with your email address
Rocket clouds
P&RA Retrospective - R2 by Mind Map: P&RA Retrospective - R2

1. What went well?

1.1. Delivery

1.1.1. Team Work

1.1.2. Good Communication(BA <-> Test)

1.1.3. Commitment to deliver

1.1.4. Great Test Manager doing 3 jobs

1.2. Stand up works

1.3. Data Reconciliation(Pace -> DM -> Reports)

1.4. Resources

1.4.1. Lynx DI Work is effective

1.4.2. Jason Watts(IBM), great resource

1.5. Stakeholder management

1.6. Infrastructure Config Spreadsheet

1.7. Data Integration Design Docs

1.8. Support knowledge gone up

2. What did not go well?

2.1. Communication

2.1.1. Communication with Business

2.1.2. Communication with Eagle

2.2. Knowledge

2.3. Environment

2.3.1. Access to Hiport Env(Sandbox)

2.3.2. Lack of RCA - (Up skilling required)

2.3.3. Performance issues)

2.3.4. Appropriately raising severity on HDs

2.3.5. Retrieving archived logs

2.4. Data Integration Issues(Appropriate Data Extracts to be provided where possible by testers)

2.5. Vendors

2.5.1. GSS Knowledge/Turn around time)

2.5.2. Poor service by IBM team

2.6. Project Plan

2.6.1. Project support requirement to BAU Pilot team

2.6.2. Activities post Test Exec to Deployment not covered in Plan(E.g. Business shakeout)

2.6.3. Drops fell over post Drop 2

2.7. Sign offs

2.7.1. Time taken to sign off TCs(Key resource dependency)

2.7.2. Time taken to sign off Requirements

2.8. Change management

2.8.1. Requirement change post sign off

2.9. Processes

2.9.1. Lack of Design Docs

2.9.2. Lack of Dev Manager

2.9.3. Deployment process

2.9.4. Test Data prep

2.10. Not all Test cases are in ALM - Traceability issue

2.11. Permission and access approvals

2.12. Estimates provided by Project team

3. Lessons/Suggestions/Ideas

3.1. Design doc Walkthrough

3.2. Provide only high level plan to clients

3.3. Cross skilling

3.4. Tight communication process to ensure all teams are across the change

3.5. Walkthrough with Business SMEs

3.6. Communication to support BAU team when a functionality is rolled out