Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

CIBER QA & Testing Practice


Published on

CIBER QA & Testing Practice

  • Login to see the comments

  • Be the first to like this

CIBER QA & Testing Practice

  1. 1. CIBER QA & Testing Practice <br />
  2. 2. Distributed Delivery of QA & Testing Services<br />
  3. 3. Testing’s Place in Lifecycle Quality<br />
  4. 4. Major Testing Activites and Labor Categories<br />Preparing<br />Running Tests & Evaluating Results<br />Extending<br />Planning<br />Production Readiness Review <br />Test Readiness Review <br />Test Plan Review<br />Test Management Metrics and Reporting<br /> Requirements Analysis<br />Test Leadership<br /> Risk Analysis & Test Strategy<br />Defect Management<br /> Test Planning<br /> Operational Readiness Tests<br />Test Case Development<br /> Production <br /> Support<br />Testers<br />Integration Tests<br /> Functional Tests<br /> Environment Shakedown<br /> Rollover Scripts<br /> to Regression<br />Automation Specialist<br />Apply Regression Scripts<br />Build Scripts<br /> Performance Testing & Tuning<br /> Sustainment<br /> of Test Data<br />Test Data Specialists<br />Test Data Prep<br />Test Data Support<br />Environment Support<br /> Environment<br /> Carryover<br /> Environment Planning<br /> Environment Prep<br /> Environment Support<br />
  5. 5. A Master Test Strategy Controls Testing Activities<br />Test Plans operate under a Test Strategy<br />A Master Test Strategy covers Development and Maintenance activities, establishes standards, methods, and procedures, and puts Testing into Continuous Improvement.<br />It is not project-specific. It is the foundation of all necessary Test Controls, Support, and Interactions. <br />CONTENT OF A TEST STRATEGY:<br />Test Organization: Roles & Responsibilities, Communications<br />Test Approach: Levels, Types, Entry & Exit Criteria, Triage<br />Test Management: Milestones, Deliverables, Metrics, Risk Mitigations and Contingency Plans, Root Cause Analysis<br />Test Infrastructure: Environments, Test Data, Test Tools (including Automation, Planning, Repository, and Defect Tracking)<br />Defect Management: Rules, Flows, Roles & Responsibilities<br />
  6. 6. The QA of Lifecycle Movement and Control<br />
  7. 7. Service Catalogue of Testing Services<br />
  8. 8. Portfolio Management Approach to Right-shoring<br />Strong<br />High<br />Technical Condition<br />Weak<br />Low<br />Thorough<br />Business Value<br />Test Case Coverage<br />Poor<br />Low<br />Degree of Difficulty<br />Business Value – the economic value derived from the test coverage in terms of defect prevention, revenue protection, productivity yield, and cost savings.<br />Technical Condition – the degree of validity, volatility, and obsolesce of an application’s test coverage and involved data controls.<br />Objective criteria are used to assist in prioritizing and preparing for off-shore transitions. <br />Test Coverage ratings are based on the following criteria: Adequacy, Benefits, Impact, Risks, and Value.<br />Identify<br />Prioritize<br />Group<br />Support Plan<br />Application Portfolio<br /><ul><li>First Tier
  9. 9. ________
  10. 10. ________
  11. 11. ________
  12. 12. Second Tier
  13. 13. ________
  14. 14. ________
  15. 15. ________
  16. 16. Third Tier
  17. 17. ________
  18. 18. ________
  19. 19. ________</li></ul>5<br />Reconsider<br />& Sequence<br />Transition 1<br />1<br />4<br />“Prep-n-Go”<br />2<br />8<br />7<br />Transition 2<br />6<br />Transition 3<br />3<br />May retire or re-plan coverage if no value added<br />Improve condition before Offshoring<br />9<br />High<br />Resources<br />Timing<br /><ul><li>Once strategic value has been identified and prioritized, application coverage components can be grouped into tiered “releases” and sequentially planned for transition support.</li></li></ul><li>Transition Planning, Responsibility Transfer and Stabilization<br />Transition Planning<br /><ul><li>Onsite Core Leadership Team of </li></ul> collocated and future offsite Leads<br /><ul><li>Structures the Responsibility Transitions</li></ul> by applying Portfolio Management principles<br /><ul><li>Prioritizes the Knowledge Acquisition</li></ul>Knowledge Acquisition & Continuance<br /><ul><li>Utilizes proven Knowledge Capture Methods and Techniques
  20. 20. Our testers presently hold much of the application and process expertise needed to sustain business continuity
  21. 21. Prioritized to mitigate risk of loss of knowledge sparsity</li></ul>Grouped Responsibility Transitions <br /><ul><li>Begins onsite with knowledge and leadership handoffs
  22. 22. Identifies “early wins” for more rapid utilization of offsite resources and stabilization of unique processes and methods
  23. 23. Continue offsite with oversight, communications, and support structure ensuring success thru Stabilization
  24. 24. Becomes the steady state way of performing stable, ongoing efforts</li></ul>Stabilization<br /><ul><li>Enables stronger more focused offsite responsiveness by aligning “common services” into a centralized hub serving team needs with a consolidation of specialized skills: (e.g. Test Data Management, Automation, Troubleshooting)
  25. 25. Shakedown-style process drills structured to find and fix weaknesses before they become an issue</li>