SCDDHS>PMO>TCOE: Formal Inspection Process

1. SCDDHS>PMO>TCOE: Formal Inspection Process Project Management Office January 30, 2017

2. The Spectrum of Review Formality Less Formal More Formal ad hoc review peer desk check, pass around pair programming walk through team review inspection

3. The Inspection Process • Been doing varying types of reviews for years • Maturing to the next level • Formal Inspections • Process is based on • The Fagan Inspection Process • High Impact Inspections™ • Overall goal is higher DRE

4. Who’s Involved in Inspections? • Business Analyst • Testers • Technical or Systems Analyst • Developer • Project Manager • Quality Assurance

5. What Do We Inspect? Initiation, Concept and Planning Requirements Analysis & Design Development & Testing Implementation & Post-Implementation Business Case *Required BRD -or- Product Backlog *Required FRS -or- Epic & User Stories *Required Code *Required for customer financial data Deploy & Transition Plan Project Plan Test Plan Tech Design Spec? *Required Test Case WBS Infrastruc – ture Tech Design? *Required

6. Inspection Roles • Author • The person whose work product is being inspected • Moderator • Administers the inspection • Reader • Key role during the inspection meeting • Inspector • Inspects- but not the Author, Moderator, or Reader • Observer • Does not participate

7. Planning Preparation Inspection Meeting Rework Follow Up The Inspection Process Initial Work Product Inspected Work Product

8. Moderator Attributes Inspection Skills People Skills Administrative Skills Planning Stage • Author finds a Moderator

9. Planning Stage • Author finds a Moderator • Moderator receives work product from Author • Moderator works through Entry Checklist

10. Inspection Entry Checklist Inspection Entry Checklist • Work product has been proof read • Conforms to standards, templates, and formats • Unique version identifier • No changes until after Inspection • Moderator found no flagrant problems in brief examination More tips… -Section names and/or line numbers -Identify portions to be inspected -Source documents available -Incomplete sections marked TBD -Spell checked!

11. Planning Stage • Author finds a Moderator • Moderator receives work product from Author • Moderator works through Entry Checklist • Determine the rest of the Inspection Team • Schedule Meeting(s) • Moderator distributes inspection package

12. The Inspection Package • Distribute documents to the team • Separate message from the meeting invite • Contents • Work product to inspect • Predecessor documents or specifications • Standards (or link to) for the document type • Defect checklist or rule set for this type of work product (link to) • Corresponding test documentation

13. Preparation Stage • Each inspector examines work product • Understand it • Look for errors • Use checklists or rules to find typical defects • OK to assign specific areas to different inspectors • Consistency of cross-references • User interface issues • Traceability to source documents • Similar time spent in prep as time spent in meeting • Record minor issues on work product or typo list

14. Typo List • Each inspector examines work product • Understand it • Look for errors • Use checklists or rules to find typical defects • OK to assign specific areas to different inspectors • Consistency of cross-references • User interface issues • Traceability to source documents • Record minor issues on work product or typo list

15. Preparation Techniques • Multiple passes • Use a Defect Checklist • Develop a common issue checklist • Develop test cases • Draw a model or diagram • Check if desired quality attributes are met

16. Evaluate Preparation Who Moderator What Collects and evaluates prep time Decides if meeting should continue Consolidates issue logs into Master Issue Log

17. Inspection Meeting Stage • This is the core meeting • Moderator schedules and runs the meeting

18. Present Work Product / Report Defects Who All inspectors Who Moderator Who Reader What Present work product Pause regularly What Report Defects Ask Questions What Document Defects Classify them Find defects, don’t fix them

19. Presenting the Work Product • Reader selects presentation method • Paraphrasing small chunks in her own words • Drawing diagrams • Walking through a scenario • Walking through test cases • Proceed at a reasonable speed • Describe the work product, don’t read the work product

20. How to Use the Issue Log • Collect “Inspection Summary Report” from all stakeholders prior to meeting • Consolidate issues into a single list eliminating duplicates and typo’s • Conduct meeting to determine what are real defects • Defects will be opened in Jira with a type of “verification” • Inspectors – focus on the work product

21. The Human Side of Inspections • Remember why we are doing this • Authors – be open to feedback • Inspectors – focus on the work product

22. Rework Stage • Items used by Author during rework: • The issue log from the inspection meeting • Typo lists • Marked up copies of the work product • His own notes from the meeting • Some defects may need to remain but should be tracked in Jira • Author reports back actual rework effort to the Moderator

23. Follow-up Stage • Moderator confirms rework was performed • Second inspection meeting setup if required • Moderator completes Exit Checklist • Open issues tracked to closure • All defects are logged in Quality Center • All major defects corrected • Summary submitted into Clarity

24. Who Should Inspect What?

25. Who Should Inspect What? Author: BA Moderator: BA (system SME) Reader: BA Inspector: Tester, TSA, PA, SA

26. Who Should Inspect What? Author: BA Moderator: BA (system SME) Reader: producer of the FDS Inspector: Tester, TSA, PA, SA

27. Who Should Inspect What? Author: SA Moderator: BA (system SME) Reader: producer of the TDS Inspector: Tester, TSA, PA, SA

28. Who Should Inspect What? Author: Developer Moderator: Developer (SME) Reader:developer source code Inspector: Tester, TSA, PA, SA

29. Who Should Inspect What? Author: Developer Moderator: Developer (system SME) Reader: Developer Inspector: Tester, TSA, PA, SA

30. Questions?