8/7/2007SE 652 - 2007_8_07_Misc_PostMortem.ppt1 Additional Topics & Team Project Post-Mortem.

Slides:



Advertisements
Similar presentations
Project Cycle Management
Advertisements

Facilitated by Joanne Fraser RiverSystems
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
More CMM Part Two : Details.
Sponsored by the U.S. Department of Defense © 2002 by Carnegie Mellon University July 2002 Pittsburgh, PA Lecture 6: Team Planning.
Stepan Potiyenko ISS Sr.SW Developer.
Effective Project Management: Traditional, Agile, Extreme
Personal Software Process
The Soft Topics in Software Engineering Mark Ardis Stephen Chenoweth Frank Young.
6/19/2007SE _6_19_TSPImp_SVT_Lecture.ppt1 Implementation Phase Inputs: Development strategy & plan Completed, inspected & baselined SRS & SDS.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
SE652 Project Post Mortem Team Presentation & Course Review.
7/31/2007SE _7_31_CMMI_Software_Quality.ppt 1 Standards & Assessments CMMI, ISO 9000, TL9000 Sources: ASQ CSQE Primer Introduction to CMMI CMMI.
SE 555 Software Requirements & Specification Requirements Validation.
6/26/2007SE _6_26_TestResults_PSMp1.ppt1 Team Software Project (TSP) June 26, 2006 System Test.
SE 652 Software Quality Management Summer 2007 Lee Vallone.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
INFO 637Lecture #31 Software Engineering Process II Launching & Strategy INFO 637 Glenn Booker.
Process: A Generic View n A software process  is a roadmap to building high quality software products.  provides a framework for managing activities.
Team Launch Introduction. Real projects are large and complex, and most software is created by teams Merely throwing people together does not result in.
CS 350, slide set 6 M. Overstreet Old Dominion University Fall 2005.
PMP® Exam Preparation Course
Project Management Tools A Loose Guideline on how to use shovels and rakes at AIAA A presentation for New Hires October 6, 1999.
Competency Area A: Communicating with Paraprofessionals.
Software Quality Assurance Activities
CS 350, slide set 7 M. Overstreet Old Dominion University Spring 2005.
INFO 637Lecture #41 Software Engineering Process II Development Plan INFO 637 Glenn Booker.
Software System Engineering: A tutorial
Software Quality Assurance Lecture #2 By: Faraz Ahmed.
By Touseef Tahir Software Testing Basics. Today's Agenda Software Quality assurance Software Testing Software Test cases Software Test Plans Software.
Preparing for the Launch Mohammed El- Affendi. Launch Major Tasks  The Launch is performed according to script “LAU1”, table 3.1 in the book (page 39),
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
INFO 637Lecture #21 Software Engineering Process II TSP Roles and Overview INFO 637 Glenn Booker.
Improving engineering productivity APEGGA. Improving Productivity Mega Projects  History  What is needed  How will it be done  Division of Labour.
HIVQUAL Group Learning Guide – New York State DOH AIDS Institute 1 Team Roles Learning Objectives  To understand the roles and responsibilities of project.
Effective Project Management: Traditional, Agile, Extreme Presented by (facilitator name) Managing Complexity in the Face of Uncertainty Ch08: How to Close.
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.
© 1998 Carnegie Mellon UniversityTutorial The Personal Software Process (PSP) The overview of the PSP that follows has been built from material made.
CMM Level 2: Repeatable Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Quality Activity Matrix Presented by Sandra Toalston President, SanSeek 1.
Georgia Institute of Technology CS 4320 Fall 2003.
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
Team Software Process (TSPi) CS4320 Fall TSP Strategy Provide a simple process framework based on the PSP. Use modest, well-defined problems. Develop.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Business & Enterprise Systems The Integrated Master Plan (IMP) and the Integrated Master Schedule.
Develop Project Charter
Implementation Phase CS4311 – Spring 2008 References: Shach, Object Oriented and Classical Software Engineering E. Braude, Software Engineering, an Object-Oriented.
Sponsored by the U.S. Department of Defense © 2002 by Carnegie Mellon University July 2002 PSP-TSPi Faculty Workshop Pittsburgh, PA Lecture.
Chapter 8. The Process Phases 1. Launching teams 2. The development strategy 3. Team planning 4. The requirements process 5. Designing with teams 6. Implementation.
THE POSTMORTEM Chapter 10 Introduction to Team Software Process.
PRODUCT IMPLEMENTATION Chapter 8 Tawatchai Iempairote September 23, 2041.
Focus on design principles and on a process for doing design = To produce a precise, complete, high- quality foundation for product implementation.
BSBPMG508A Manage Project Risk 11.6 Monitor and Control Risks Adapted from PMBOK 4 th Edition InitiationPlanning ExecutionClose Monitor Control The process.
Timesheet training Version: Introduction Duration: 1.5 hours Purpose: Guide on how to use Timesheet.
CHAPTER 7 – Managing Project Schedules. “Plan the Work” “Work the Plan” “Endorse the Plan” + 10% of Project effort + 90% of Project effort “Align the.
Objectives Definition Instructions Mark Melanson 8 January 2012.
CS 350, slide set 10 M. Overstreet Old Dominion University Spring 2005.
TMP3413 Software Engineering Lab Lab 01: TSPi Tool Support.
CSC 480 Software Engineering Team Issues. Essence of a Successful Team To be successful, teams must  Plan their projects  Track their progress  Coordinate.
Applied Software Project Management SOFTWARE TESTING Applied Software Project Management 1.
Introduction to Project Management
Chapter 3, Project Organization and Communication
Applied Software Testing
CSC 480 Software Engineering
Introduction to Tech Communication & Project Management Arthur C.M. Chen , Rm
9/18/2018 Department of Software Engineering and IT Engineering
DOD’S PHASED SYSTEM DEVELOPMENT PROCESS
Using data for instructional decision-making
Effective Project Management: Traditional, Agile, Extreme
Team Software Process (TSP)
Joint Application Development (JAD)
Presentation transcript:

8/7/2007SE _8_07_Misc_PostMortem.ppt1 Additional Topics & Team Project Post-Mortem

8/7/2007SE _8_07_Misc_PostMortem.ppt2 August 7 Class Various Topics –Test Issues (blocked test cases, diagreements) –Measurement Review –Other Deliverables for August 11 Project Postmortem (cycle report) Cycle 2 presentations Peer Feedback forms Completed project notebooks Audits Cycle Exit Completed project (source, documents & all quality records)

8/7/2007SE _8_07_Misc_PostMortem.ppt3 Team Project Postmortem Tracking process improvements during project Process Improvement Proposals (PIP) Port-Mortem Areas to consider Better personal practices Improved tools Process changes

8/7/2007SE _8_07_Misc_PostMortem.ppt4 Postmortem process Team discussion of project data Review & critique of roles

8/7/2007SE _8_07_Misc_PostMortem.ppt5 Postmortem process Review Process Data Review of cycle data including SUMP & SUMQ forms Examine data on team & team member activities & accomplishments Identify where process worked & where it didn’t Quality Review Analysis of team’s defect data Actual performance vs. plan Lessons learned Opportunities for improvement Problems to be corrected in future PIP forms for all improvement suggestions Role Evaluations What worked? Problems? Improvement areas? Improvement goals for next cycle / project?

8/7/2007SE _8_07_Misc_PostMortem.ppt6 Cycle Report Table of contents Summary Role Reports Leadership – leadership perspective Motivational & commitment issues, meeting facilitation, req’d instructor support Development Effectiveness of development strategy, design & implementation issues Planning Team’s performance vs. plan, improvements to planning process Quality / Process Process discipline, adherence, documentation, PIPs & analysis, inspections Cross-team system testing planning & execution Support Facilities, CM & Change Control, change activity data & change handling, ITL Engineer Reports – individual assessments

8/7/2007SE _8_07_Misc_PostMortem.ppt7 Role Evaluations & Peer Forms Consider & fill out PEER forms Ratings (1-5) on work, team & project performance, roles & team members Additional role evaluations suggestions Constructive feedback Discuss behaviors or product, not person Team feedback forms (Team Leaders)

8/7/2007SE _8_07_Misc_PostMortem.ppt8 Project Notebook Updated Requirements & Design documents Conceptual Design, SRS, SDS, System Test Plan, User Documentation* Updated Process descriptions Baseline processes, continuous process improvement, CM Tracking forms ITL, LOGD, Inspection forms, LOGTEST Planning & actual performance Team Task, Schedule, SUMP, SUMQ, SUMS, SUMTASK, CCR*