1. Communication/Reporting PM

2. Why is it important?

3. PM Reporting/Communications Software Development PM Upper management Reports, presentations, meetings, Q&A Team Meetings, Action Items, CC, Minutes, Q&A Clients Requirements, visits, demos, Q&A, development updates, tests

5. The Agenda Bell Modest decision items Announcements Minutes Moderate decision items Most difficult item Discussion items Small, trivial item Source : Tropman, 1985 TIME SPENT

9. Software Reviews Developer. A reader, TL. Development team representative. Software PM or project representative. Presenter Lead auditor. Facilitator or developer. Trained facilitator, technical/QA leadership. TL / Lead engineer. Responsible manager or Senior Software PM. Group leadership Auditors, management and technical personnel. Technical leadership and software team mix. Software team mix, Software QA. Technical leadership and development team mix. Management, TL, software team mix. Group attendance Management, Software PM, development team. Team agrees on changes to be made by the developer. Review team request changes and defects removals. Review team requests management or TL to act on recommendations. Made at the meetings; online pooling/email, or as a result of recommendations. Decision-making Independently evaluate compliance with objective standards and regulations. Find errors, code readings, conformance to specifications. Find errors; verify resolution and product quality. Conformance to specifications, development issues. Tracking / milestones, issues, resources, action items. Objective Audit Walk-through Inspection Technical Review Management Review Characteristic

13. Technical Review Chart Software Product Statement of Objectives Other Inputs Technical Review Report Planning Overview of Review Procedures Overview Meeting Preparation Overview of Review Procedures Review Meeting(s) Review software product and record errors Rework/Follow-up Management Follow-up Development Team Management Preparation Overview of Review Procedures Overview of software product

15. Inspection Review Chart Software Product Statement of Objectives Other Inputs Management Review Report Planning Overview Session Preparations Review general items Examination Review software product and record errors Management Follow-up Management Preparation Introduce meeting Establish preparedness Review error list Decision making Rework/Follow-up Software Developer More preparation required Re-inspect Accept

18. Audits Chart Software Product Purpose and Scope Other Inputs Audit Report Planning Examination Reporting Management Follow-up Audited entity Management Preparation Preparations Closing Meeting Evidence collection Opening Meeting

19. Technical Review, Inspection, Walk-Through Installation Configuration Audit Audit Source Code and Source Code Documentation Evaluation Technical Review, Inspection, Walk-Through Software Design Evaluation Technical Review, Inspection, Walk-Through Software Requirements Evaluation Technical Review Concept Documentation Evaluation Management Review, Technical Review Contract Verification Technical Review System Requirements Review Management Review Management Review of V&V Audit QA Audit Technical Review, Inspection, Walk-Through User Documentation Review Management Review, Technical Review Post-mortem Review Management Review Software Configuration Management Plan Review Management Review Managerial Reviews Audit In-Process Audits Audit Physical Audit Audit Functional Audit Management Review Software V&V Plan Review Technical Review Critical Design Review Technical Review Preliminary Design Review Technical Review Software Requirements Review Corresponding IEEE Std 1028 Review Type Review name