1 Software Reviews - FTR SWENET Module QUA2. Formal Technical Review u Features – Formal v Scheduled event v Defined procedure v Reported result – Technical.

Slides:



Advertisements
Similar presentations
Designing School Level Professional Development. Overview Assessing prior knowledge of professional development Defining professional development Designing.
Advertisements

Defining Leadership Roles and Delegation
OPSM 639, C. Akkan Project Closure Conditions for project closure. –Normal –Premature: early completion due to some parts of the project being eliminated.
Lecture 2 Team Coordination 1 ICS 126 Team Coordination Team Formation and Organization Group Management Meeting Techniques Large software systems require.
New Supervisor: Skills for Success
Software Project Management Lecture # 11. Outline Quality Management ( chapter 26 - Pressman )  Software reviews  Formal Inspections & Technical Reviews.
Gateway Engineering Education Coalition1 Team Agreements or How to get teams moving in the right direction…
Formal Technical Reviews
CSE 308 Project Management. SWE Communication Skills Management: Run a team meeting Presentation: Present aspects of your project during its development.
Irwin/McGraw-Hill 16-1 Chapter 16 Planning and Running Effective Meetings.
Code Inspections CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 22, 2007.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Project Work and Administration
SE 555 Software Requirements & Specification Requirements Validation.
Course Technology Chapter 3: Project Integration Management.
Chapter 11 Requirements Workshops
Implementation. We we came from… Planning Analysis Design Implementation Identify Problem/Value. Feasibility Analysis. Project Management. Understand.
Collecting Basic Evaluation Information Chapter Six cont…
Facilitating Focus Groups Insert date Insert presenters.
The Systems Analysis Toolkit Project Management Tools.
Working in Groups: 5 th edition This multimedia product and its contents are protected under copyright law. The following are prohibited by law: - any.
Project Communications Management J. S. Chou Assistant Professor.
Design Reviews Peer Reviews. Agenda Peer Reviews Participants of Peer Review Preparation for a Peer Review Session The Peer Review Session Post-peer Review.
QUALITY ASSURANCE PROJECT Improvement Coach The purpose of this session is to introduce participants to the role of the improvement coach and prepare for.
Diploma of Project Management Course Outline NSW Course Number Qualification Code BSB51407.
S ECRETARIAT Division Secretariat Advisory Preparing Meeting Agendas & Minutes Presented by Myron Iseminger.
Presented by: Insert Name Safety Management Consultant
Diploma of Project Management Course Outline NSW Course Number Qualification Code BSB51407.
Copyright c 2006 Oxford University Press 1 Chapter 11 Managing Group Meetings Importance of meeting procedures Reduces wasted time Helps members coordinate.
S oftware Q uality A ssurance Part One Reviews and Inspections.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 10: Testing and Inspecting to Ensure High Quality Part 4:
S Q A.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Slide 1 Project Management Chapter 4. Slide 2 Objectives ■ Become familiar with estimation. ■ Be able to create a project workplan. ■ Become familiar.
Chapter 23 Project Development Team © 2013 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible.
Chapter 15 Introduction to Systems Development. Learning Objectives Learn how information systems are developed Understand importance of managing SD process.
Software Testing and Maintenance 1 Code Review  Introduction  How to Conduct Code Review  Practical Tips  Tool Support  Summary.
Reviews and Inspections. Types of Evaluations Formal Design Reviews conducted by senior personnel or outside experts uncover potential problems Inspections.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
Design and Delivery of Adult Learning Programs Fall 2015 Dr. Robin Hurst.
William Sanborn Pfeiffer Kaye Adkins
Team Assessment In software development, teams are how we accomplish more and better than what can be accomplished by an individual.
Meeting Management USAMPS Captain’s Career Course.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 Project Communications Management Lecture 11. Learning Objectives Describe the importance of good communication on projects and major components of.
© Michael Crosby and Charles Sacker, 2001 Systematic Software Reviews Software reviews are a “quality improvement process for written material”.
Chapter 9* Managing Meetings. Chapter 10/Managing Meetings Hilgert & Leonard © Explain why meetings, committees, and being able to lead meetings.
Region 1 The Center of Technology Region 1 The Center of Technology IEEE Region 1 Leadership Workshop How to Run an Effective Meeting Harold Belson August.
Meetings Managers are people who do things right, while leaders are people who do the right thing. Warren Bennis, Ph.D. “On Becoming a Leader”
Getting Useful Reviews
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
Quality Assurance at CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
SQA COMPONENTS IN THE PROJECT LIFE CYCLE C HAPTER 8 Dr. Ahmad F. Shubita.
Chapter 11: Software Configuration Management
Software and Systems Integration
Planning Phase: Project Control and Deliverables
Project Management PTM721S
Chapter 11 Requirements Workshops
Before During After Follow-up Resolve Review Pre-review Familiarize
Software Reviews - Overview
Chapter 11: Software Configuration Management
Team Meetings Unit 3 Employability and Professional Development
CSC 492 – Senior Design – Spring 2019
Teaming Class 2 Notes – Section 1
QA Reviews Lecture # 6.
Teaming Class 2 Notes – Sections 2 & 3
Effective Meeting.
The roles and the process
3. Software Quality Management
Presentation transcript:

1 Software Reviews - FTR SWENET Module QUA2

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

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

The Players Managers Review TeamProducer

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

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

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

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

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

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

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

The Review Team LeaderReviewersRecorder

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

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

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

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

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

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

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

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

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

In Your Future... u Do a design review