CONFIDENTIAL | COPYRIGHT 2001, PAR3 COMMUNICATIONS | ALL RIGHTS RESERVED Walk and Stagger Through Review Process Michael Ensminger

Slides:

Advertisements

Similar presentations

Chapter 24 Quality Management.

Advertisements

A method for addressing any large problem. Carefully consider the problem. Define the problem. Ask yourself the following questions: What is it that I.

IT Project Management Greg Dexter City of Los Angeles Cheng Li Cal State Los Angeles.

Project Presentation Group Manager: Hanna Chamoun Group Members: Alexandros Tsourtis Ke Jiang Xiaoyan Ni Yang Guo.

RightFoot Technology, Inc From Knowledge To… PM Coach Results.

© 2007 AT&T Knowledge Ventures. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Knowledge Ventures. Interactive Solutions & Design Group.

Topic 5 Facility Assessments and Environmental Audits Chapter 33.

1 reviews8 Software Reviews, Walkthroughs, and Inspections The standard technique to ensure quality in software development.

Code Inspections CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology January 23, 2003.

11 October Project Management Discipline of planning, organizing, and managing resources to bring about the successful completion of specific project.

Chapter 15 Design, Coding, and Testing. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Design Document The next step in the Software.

Week 7: Requirements validation Structured walkthroughs Why have walkthroughs When to have walkthroughs Who participates What procedures are helpful Thoughtless.

Oral Presentations Fundamental Objectives of Presentations Demonstrate what the team has learned Identify a specific design problem Present engineering.

CSC 395 – Software Engineering Lecture 9: Testing -or- How I Stopped Worrying and Learned to Love the Bug.

Project Management Tools and Techniques ISMC, October 23, 2001.

EPLC Deliverables Sherry Brown-Scoggins & Wanda Hall

The Impact Angel Group Real Impact. Real Returns..

Tietojärjestelmien peruskurssi Systeemisuunnittelu ja prototyyppimenetelmä Malin Brännback.

Software Quality Assurance Lecture #4 By: Faraz Ahmed.

(from Dr. Diane Pozeksky. “80% of software projects fail” Standish Report (1995) Standish Report 16.2% completed on-time and on-budget with all features.

Chapter 14: Inspection  Basic Concept and Generic Process  Fagan Inspection  Other Inspection and Related Activities.

Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent.

- Component Inspection. -Usability Testing. -Unit Testing. -System Testing.

Recap from last week Understand organizations, including the four frames, organizational structures. Explain why stakeholder management and top management.

Project Management for Software Engineering Starting at “I’ve got a project” How do you decide: –What do I need to do? –When should I do it? –How long.

Testing Basics of Testing Presented by: Vijay.C.G – Glister Tech.

Chapter 15 The Systems Development Life Cycle and Project Management: Addressing the Challenges of Building AIS Systems Copyright © 2014 McGraw-Hill Education.

Assessing Organizational Communication: Strategic Communication Audits Chapter 3 Conducting Team Audits.

Facilitation Principles and Techniques. 2 The Inside Facilitator Authorized by the Project Champion Invites project team members Announces the facilitator.

6. Testing and Verification

Formal Technical Reviews Matt Graham 18 November 2004 EECS 814 University of Kansas.

©Copyright OMRON Corporation All Rights Reserved A Step by Step Approach for Creating an Environment for Successful Projects IWFST2005 Nov. 8-10,

Project Proposal Document Optimization 15 February 2007 Team members: Chris Catalano Chun-Yu Chang Chris Joson David Matthes.

University of Palestine software engineering department Testing of Software Systems Program Inspections, Walkthroughs, and Reviews instructor: Tasneem.

Lecture 3 Title: Information Technology Project Methodology By: Mr Hashem Alaidaros MIS 434.

Software Testing and Maintenance 1 Code Review  Introduction  How to Conduct Code Review  Practical Tips  Tool Support  Summary.

Copyright © 2012 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin CHAPTER NINE SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT CHAPTER.

Chapter Fourteen Copyright © 2006 John Wiley & Sons, Inc. Communicating the Research Results.

Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.

1 Phase Implementation. Janice Regan, Overview of Implementation phase Create Class Skeletons Define Implementation Plan (+ determine subphases)

April 24, 2017 Agile BVIR.

Introducing Project Management Update December 2011.

 Definition of a quality Audit  Types of audit  Qualifications of quality auditors  The audit process.

Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.

KUFA UNIVERSITY Department of Computer Science 06/12/2015.

Copyright 2010, The World Bank Group. All Rights Reserved. Managing Data Processing Section B.

Project Management Inspections and Reviews 1 February.

Project Management Organization Scheduling 31 January.

Agile Practices Benchmarking Case Study ABC Company Logo by Company name – ABC.

Inspection and Review The main objective of an Inspection or a Review is to detect defects. This activity and procedure was first formalized by Mike Fagan.

© Michael Crosby and Charles Sacker, 2001 Systematic Software Reviews Software reviews are a “quality improvement process for written material”.

Exploring Algorithms PROGRAMMING FUNDAMENTALS. As you come in Find your section area. Find your team. One person from each team should get the team folder.

Information Technology Project Management, Seventh Edition Note: See the text itself for full citations.

1 540f07reviews9sep25 Pert and Reviews Reviews S&G Chapter 5.

Six Sigma Project Coding Performance Improvement Project Global Communication, Inc.

Chapter 3: The Project Management Process Groups: A Case Study Information Technology Project Management, Fourth Edition Project Execution & Closing Thursday,

B U D I L U H U R U N I V E R S I T Y POST GRADUATE PROGRAM MAGISTER ILMU KOMPUTER (M.Kom) IS PROJECT MANAGEMENT.

Adult education institution ‘DANTE’. About us...  Founded in first acknowledged language school in the city of Rijeka  Long experience and tradition.

Swyft Product Overview Small Business. Mobilized..

PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR

The Value of Managing the Review Process

Project Management The End Stage

Northwest Florida Region

Quicken Contact Help Number When you get such errors, you need to inspect the error carefully and then you should resolve it with step by step measures.

Peer Reviews 11/21/2018.

Dr. Rob Hasker SE 3800 Note 9 Reviews.

QA Reviews Lecture # 6.

(team representative name here)

© All Rights Reserved.

Presentation transcript:

CONFIDENTIAL | COPYRIGHT 2001, PAR3 COMMUNICATIONS | ALL RIGHTS RESERVED Walk and Stagger Through Review Process Michael Ensminger PAR3 Communications

CONFIDENTIAL | COPYRIGHT 2001, PAR3 COMMUNICATIONS | ALL RIGHTS RESERVED Traditional Review Methodologies  Desk Check  Walkthrough  Informal Review  Formal Review  Fagan Style Inspections  Pair Programming

CONFIDENTIAL | COPYRIGHT 2001, PAR3 COMMUNICATIONS | ALL RIGHTS RESERVED Challenges to Introducing Reviews to an Inexperienced Team  Background knowledge of the team  What are the responsibilities of the individual team members?  When is the review done?  What was the quality level of the review?

CONFIDENTIAL | COPYRIGHT 2001, PAR3 COMMUNICATIONS | ALL RIGHTS RESERVED Walk Through Defined The systematic review of a use case, design, code, etc. as the final system will execute it with a focus on the "normal" -- that is, non-error -- processing.

CONFIDENTIAL | COPYRIGHT 2001, PAR3 COMMUNICATIONS | ALL RIGHTS RESERVED Stagger Through Defined The systematic review of a use case, design, code, etc. as the final system will execute it with a focus on the "non- normal" -- that is error and uncommon execution paths -- processing.

CONFIDENTIAL | COPYRIGHT 2001, PAR3 COMMUNICATIONS | ALL RIGHTS RESERVED Walk Through Process 1.Determine Focus and Scope 2.Select Review Team 3.Pre-Read 4.Review Meeting 5.Record Issues 6.Make Changes 7.Follow-up Before Stagger Through

CONFIDENTIAL | COPYRIGHT 2001, PAR3 COMMUNICATIONS | ALL RIGHTS RESERVED Stagger Through Process 1.Prepare for Stagger Through Meeting 2.Review Meeting 3.Record Issues 4.Determine Next Steps 5.Make Changes

CONFIDENTIAL | COPYRIGHT 2001, PAR3 COMMUNICATIONS | ALL RIGHTS RESERVED Case Study: Partes Corporation  The Product  The Team  The Initial Schedule  The Review Process  Schedule Impact

CONFIDENTIAL | COPYRIGHT 2001, PAR3 COMMUNICATIONS | ALL RIGHTS RESERVED Questions?  Contact Information: Or