1. 1 Software Reviews - FTR SWENET Module QUA2

2. Formal Technical Review u Features – Formal v Scheduled event v Defined procedure v Reported result – Technical v Not schedule v Not budget – Independent review team v Producers not present

3. Formal Technical Review u Implications – More preparation time – Less material per meeting – Product must stand or fall on its own

4. The Players Managers Review TeamProducer

5. Team Selection u Manager assigns – Vested interest in a good outcome – Review as delegation of manager’s responsibility u Technical competence – Current technology u Objectivity – Best buddies and “outsiders” u User involvement

6. Team Size u Smaller for – Focus – Scheduling – Reasonable output volume per person-hour u Larger for – Expertise – Making review public u Non-participating observers 37

7. Managers’ Participation u “Review is a manager’s job” u Technical competence – Managers who are not current – Managers who think they are current u Chain of authority – Review of product Vs. review of person

8. Managers’ Participation u Active participation – As an “Outsider” – As a team leader (and outsider) v providing general competence u Post facto participation – Review materials – Review report

9. What and When to Review u Any software artifact – requirements, designs, code, documentation, procedures, interfaces,... u Design for review – Controlling product complexity – Controlling review length u Scheduling reviews 2 Hours Weeks 10 AM

10. Review Process u Producers provide materials u Leader schedules meeting u Individuals prepare u Team holds review meeting u Manager gets report

11. Team Task Overview u Provide a good review – The team is responsible for the review, not the product (Don’t shoot the messenger) u Find issues – Raise them, don’t solve them u Render an assessment decision – Accept, Accept with minor revision, Revision needed, Reject – Unanimous approval required v Product rejection by individual veto

12. The Review Team LeaderReviewersRecorder

13. Team Leader - Traits u Technical competence – General strength – Credibility – Able to understand the issues u Personal skills – Willing to confront people – Willing to report failure – Able to step back from the heat of discussion u Administrative skills

14. Team Leader - Tasks u Avoid premature reviews u Coordinate arrangements – Materials distribution – Meeting schedule – Meeting location and facilities u Ensure a good review – Or report the reason for failure v Materials missing v Reviewers missing or not prepared

15. Team Leader - Run the Meeting u Act as chairperson – Opening and introductions – Procedure guide – Closing u Act as facilitator – Controlling level of participation v Enough but not too much – Conflict resolution u Terminate the meeting if unproductive

16. Reviewers - Tasks u Prepare before – Thorough review of materials u Participate – Be there v Coming late; leaving early – Act professionally v Personal agendas v Big egos and shyness – Positive and negative comments v Balance; courtesy; preserving what’s good

17. Recorder u Selection – Any competent reviewer – Single or multiple recorders – Rotating responsibility within a meeting – Leaders as recorders v Having too much to do v Separation of power u Task: Get it in writing – Basis for report

18. Recording Medium u Issues – Public Vs. private notes – Speed and accuracy – Usefulness after the meeting u Media – Flip charts; posting prior pages – Blackboards, overheads, PC and projector – Video and audio recording

19. Managers - Tasks u Stay out of reviews in your own area u Support reviews – Talk about it – Provide resources v Time, the right people, place, materials – Change the reward system u Abide by the review results

20. Review Report u Purpose – Tell managers the outcome – Early warning system for major problems – Provide historical record v For process improvement v For tracking people involved with projects u Contents – Summary – Product issues – Other related issues

21. Summary u Highly effective technique u Low technology u Not used nearly enough u DO IT! – Personal review u Do it now for the project – Guidelines for report – Two copies

22. In Your Future... u Do a design review