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),

Slides:



Advertisements
Similar presentations
FCMAT Response & Preparation: Process Outline October 25, 2006.
Advertisements

MODELING THE TESTING PROCESS Formal Testing (1.0) Requirements Software Design Risk Data Approved, Debugged, Eng. Tested Code Automated Test Tools Tested.
Planning for Certification in Plan your project In this presentation we present the tasks that must be completed in order to achieve certification.
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Sponsored by the U.S. Department of Defense © 2002 by Carnegie Mellon University July 2002 Pittsburgh, PA Lecture 6: Team Planning.
Gu & Maher University of Sydney, October 2004 DECO2005 Monitoring Team Process.
Stepan Potiyenko ISS Sr.SW Developer.
6/19/2007SE _6_19_TSPImp_SVT_Lecture.ppt1 Implementation Phase Inputs: Development strategy & plan Completed, inspected & baselined SRS & SDS.
5/29/2007SE TSP Launch1 Team Software Project (TSP) May 29, 2007 Launch/Strategy Team Formation.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
8/7/2007SE _8_07_Misc_PostMortem.ppt1 Additional Topics & Team Project Post-Mortem.
ESC/EN Engineering Process Compliance Procedures August 2002.
@ Industrial Engineering by Bopaya Bidanda David I. Cleland.
Professional Development Programs
Process: A Generic View
© 1999 Prentice-Hall, Inc. Chap Level 3: Key Processes Defined Group 9: LaTanya Moore Ali Imajat Asim Eldaroty.
INFO 637Lecture #31 Software Engineering Process II Launching & Strategy INFO 637 Glenn Booker.
IS-700.A: National Incident Management System, An Introduction
By, David Anderson.  Determine team members to collaborate on assessment.  Create a written AT assessment plan:  Determine assessment questions  Expected.
Team Launch Introduction. Real projects are large and complex, and most software is created by teams Merely throwing people together does not result in.
CHAPTER 5 Infrastructure Components PART I. 2 ESGD5125 SEM II 2009/2010 Dr. Samy Abu Naser 2 Learning Objectives: To discuss: The need for SQA procedures.
CS 350, slide set 6 M. Overstreet Old Dominion University Fall 2005.
Project Management Tools A Loose Guideline on how to use shovels and rakes at AIAA A presentation for New Hires October 6, 1999.
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
Best Practices By Gabriel Rodriguez
Overview of the Department’s ABET Criterion 3 Assessment Process.
CS 350, slide set 7 M. Overstreet Old Dominion University Spring 2005.
Visual 5.1 Planning Process Army Delivery Unit 5: Planning Process.
Chapter 2 Process: A Generic View
LOGO “ Add your company slogan ” Software Measurement & Analysis Team Assignment 2.
PP 650: Public Policy Analysis Unit One Seminar Kris R. Foote, J.D., M.P.A., M.S.W. Kaplan University.
INFO 637Lecture #21 Software Engineering Process II TSP Roles and Overview INFO 637 Glenn Booker.
Team Assignment 15 Team 04 Class K15T2. Agenda 1. Introduction 2. Measurement process 3. GQM 4. Strength Weakness of metrics.
ADEPT 1 SAFE-T Evidence. SAFE-T 2 What are the stages of SAFE-T? Stage I: Preparation  Stage I: Preparation  Stage II: Collection.
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.
INFO 424 Team Project Practicum Week 2 - Launch report, Project tracking, Review report Glenn Booker Notes largely from Prof. Hislop.
Establishing an Assessment Process for a Computing Program Cheryl Aasheim, Georgia Southern University Art Gowan, Georgia Southern University Han Reichgelt,
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
1 | 2010 Lecture 3: Project processes. Covered in this lecture Project processes Project Planning (PP) Project Assessment & Control (PAC) Risk Management.
Copyright 2010, The World Bank Group. All Rights Reserved. Statistical Project Monitoring Section A 1.
Sponsored by the U.S. Department of Defense © 2002 by Carnegie Mellon University July 2002 PSP-TSPi Faculty Workshop Pittsburgh, PA Lecture.
1 EMS Fundamentals An Introduction to the EMS Process Roadmap AASHTO EMS Workshop.
THE POSTMORTEM Chapter 10 Introduction to Team Software Process.
How do You Fit within the Process? Roles and Responsibilities – Pre CAB (1/2) 1 Change Requestor Initiates the Change Request (CR) in Service-now Includes.
Team-Based Development ISYS321 Managing the Information Systems Project.
TA Meetings ECE 445: Senior Design - 09/15/15. Overview  Meeting expectations  How to prepare  Evaluation.
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
TMP3413 Software Engineering Lab Lab 01: TSPi Tool Support.
ACC 542 Entire Course For more classes visit ACC 542 Week 1 Individual Assignment Computer Information System Brief ACC 542 Week.
CSC 480 Software Engineering Team Issues. Essence of a Successful Team To be successful, teams must  Plan their projects  Track their progress  Coordinate.
Chapter 10 Understanding and Planning Reports and Proposals 10-1.
ACC 542 Entire Course FOR MORE CLASSES VISIT ACC 542 Week 1 Individual Assignment Computer Information System Brief ACC 542 Week.
Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.
Chapter 6: Database Project Management
Software Configuration Management
CSC 480 Software Engineering
Software and Systems Integration
Software Subcontractor
TechStambha PMP Certification Training
CPMGT 300 Competitive Success/snaptutorial.com
CPMGT 300 Education for Service/snaptutorial.com.
CPMGT 300 Teaching Effectively-- snaptutorial.com.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 2 Process: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Adaptive Product Development Process Framework
Approximate Time Allocations For the Activity-Based Costing Analysis
Your agenda should answer WHEN, WHO, WHY, WHAT, PREPARE, HOW.
Approximate Time Allocations For the Activity-Based Costing Analysis
Team Software Process (TSP)
Presentation transcript:

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), and involve the following steps: – Course overview by instructor – Collect student information – Sate the product objectives – Form teams and assign roles

Launch Major Tasks  Set team and member goals  Explain how team meetings are conducted (purpose, scheduling and reporting)  Team leaders hold the first meeting  The planning manager reviews for the team the data required from every member every week, and the reports to be generated

Goal Setting  It is important to set goals for the whole team and for individual members. Three types of goals are expected: – Team goals – Member goals – Role goals  The goals should be measurable  See pages in the book

Roles: The Team Leader  Lead meetings.  Review agenda.  Make sure that the meeting achieves its goals.  Assess risks.  Report to instructor.

Development Manager:  Criteria for an effective strategy.  Conceptual design.  Propose and evaluate alternative strategies.  Allocate functions to each cycle.  How to subdivide and then integrate the product.

Quality Manager:  Document the strategy criteria.  Document the strategy.  Document the meeting.

Planning Manager:  Size and time estimates for all the current cycle products.  Rough estimates for the products of subsequent cycles.

Support Manager:  Identify the configuration control board and procedures.  Specify any needed support tools and facilities.  Reviews the procedures with the team members for their agreement.

Weekly Meetings  Fix a weekly time and place for team meetings  Follow the week script (table 3.5), page 44 to conduct meetings  Before the meeting update your personal TASK and SCHEDULE forms and summarize them in the WEEK form (table 3.6)

Weekly Meetings  The most important purpose of the meeting is to gather and analyze team’s data for the prior week and the development cycle to data  All engineers must submit individual data to the planning manager who compiles team WEEK, TASK and SCHEDULE forms

Preparation for meetings:  Each engineer should fill and submit to the planning manager the WEEK, TASK and SCHEDULE forms.  Planning manager prepares the weekly status report from the individual reports.  Meeting agenda has been issued.

The First Meeting  Discuss Roles: Every member should be aware about his role  Discuss cycle 1 goals  Set a weekly time and place for meetings  Agree on a time to submit the required data to the planning manager

Project Notebook  Establish a project Notebook for the team using recommendations in appendix G.  The team leader is responsible for maintaining the notebook

Some Forms  TSPi Weekly Status Reports.doc TSPi Weekly Status Reports.doc  TSPi Task Planning Template.doc TSPi Task Planning Template.doc  TSPi Schedule Planning Template.doc TSPi Schedule Planning Template.doc