Software Process Training

Similar documents
Software Process Training

Software Process Training

Software Process Training

Software Process Training

Software Process Training

Software Process Training

Project QA and Collaboration Plan for <project name>

CMMI: Specific Goals and Practices

<name of project> Software Project Management Plan

Project Plan for <project name>

Knowledge Area Inputs, Tools, and Outputs. Knowledge area Process group/process Inputs Tools Outputs

CPM -100: Principles of Project Management

Risikomanagement mit der Success Driver Analyse (SDA) - Erfahrungen bei Grossprojekten und Programmen

21. Earned Value deals with: a. EV Scope b. PV Time c. AC Cost 22. Portfolios are organized around business goals. 23. Take stern action against

Implementing Measurement and Risk Management in CMMI

Software and Systems Engineering. Software and Systems Engineering Process Improvement at Oerlikon Aerospace

Project Lifecycle Management (PLM)

Aligning CMMI & ITIL. Where Am I and Which Way Do I Go? cognence, inc.

Creating A Risk Management Plan

Initiating Forms COPYRIGHTED MATERIAL 1.0 INITIATING PROCESS GROUP

CMMI and IBM Rational Unified Process

Project Scheduling & Tracking

Managing Process Architecture and Requirements in a CMMI based SPI project 1

Applied Software Project Management

Iterative Software Development -

COMMONWEALTH OF MASSACHUSETTS EXECUTIVE OFFICE OF HEALTH AND HUMAN SERVICES

From the light to the full application form focus on work plan

Copyright 2013 wolfssl Inc. All rights reserved. 2

Mission Oriented Business Integrated Services (MOBIS) Schedule 874

ATTACHMENT 3 SPS PROJECT SENIOR PROGRAM MANAGER (SPM) DUTIES & RESPONSIBILITIES

Project Start Up. Start-Up Check List. Why a Project Check List? What is a Project Check List? Initial Release 1.0 Date: January 1997

Managing Change in Organizations. Sonja Streuber, PMP, SSBB

Optimization of Software Quality using Management and Technical Review Techniques

INTRODUCTION: Plan and Schedule Development Create a Work Breakdown Structure (WBS) The detailed guidelines and examples start on the following page.

PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME >

Software Test Plan (STP) Template

KMS Implementation Roadmap

Fax No: (0360) , Academic Plan

- ATTACHMENT - PROGRAM MANAGER DUTIES & RESPONSIBILITIES MARYLAND STATE POLICE W00B

Introduction to the ITS Project Management Methodology

An Application of an Iterative Approach to DoD Software Migration Planning

SWEN 256 Software Process & Project Management

VAIL-Plant Asset Integrity Management System. Software Development Process

HKITPC Competency Definition

Colorado Department of Health Care Policy and Financing

CHANGE MANAGEMENT for Continuous Improvement. Guidance Document

Template K Implementation Requirements Instructions for RFP Response RFP #

COMMUNICATION MANAGEMENT PLAN Outline VERSION 0.0 STATUS: OUTLINE DATE:

PROJECT CHARTER GUIDE

U.S. Department of Education Federal Student Aid

LESSON 4: Strategic planning to prevent corruption

DEVELOPMENT OF BEST MANAGEMENT PRACTICES TO EXECUTE A SUCCESSFUL CAPITAL IMPROVEMENT PROGRAM

Role and Skill Descriptions. For An ITIL Implementation Project

8. Master Test Plan (MTP)

Best Practices for Adopting Visualization Into Your Software Process. Mitch Bishop Johann Mendoza

Architecture Description Framework for Enterprise Systems - A Layered Approach

WHY DO I NEED A PROGRAM MANAGEMENT OFFICE (AND HOW DO I GET ONE)?

Netstar Strategic Solutions Practice Development Methodology

Information Technology Project Oversight Framework

Agenda. 0 Agenda review 2 minutes. 0 Chapter of the week 50 minutes. 0 Q&A of chapter 10 minutes. 0 Break 10 minutes. 0 Exercises 25 minutes

Interpreting the Management Process in IEEE/EIA with the Help of PMBOK

PHASE 5: DESIGN PHASE

IEEE Software Engineering Risk Management: Measurement-Based Life Cycle Risk Management PSM 2001 Aspen, Colorado

SWX: The Software Extension to the PMBOK Guide for Project Management

Automated Office Systems Support Quality Assurance Plan. A Model DRAFT. December 1996

RTI Software Development Methodology and CMMI

Department of Finance and Deregulation 2011/004 Portfolio Panels for IT Services ATTACHMENT A

Best Practices Statement Project Management. Best Practices for Managing State Information Technology Projects

CONTENTS. Preface. Acknowledgements. 1. Introduction and Overview 1 Introduction 1 Whatis the CMMI"? 2 What the CMMI* is Not 3 What are Standards?

Using Rational Software Solutions to Achieve CMMI Level 2

Crosswalk Between Current and New PMP Task Classifications

Input, Output and Tools of all Processes

SECTION I PROJECT SUMMARY (TRW)

PROJECT PLAN FOR. Project Name Here

INTRODUCTION: How to Develop Project Management Procedures and Skills. The Guideline Content Starts on the Following Page

CRM For Internal Services Copyright 2011, Saudi Aramco. All rights reserved.

Subject Area 1 Project Initiation and Management

Software Project Management and Support - Practical Support for CMMI -SW Project Documentation: Using IEEE Software Engineering Standards

Draft Requirements Management Plan

MGMT 4135 Project Management. Chapter-16. Project Oversight

Sparx Systems Enterprise Architect for Team Players

PROJECT HUMAN RESOURCE MANAGEMENT

Comparing PMBOK Guide 4 th Edition, PMBOK Guide 5 th Edition and ISO 21500

PROJECT RISK MANAGEMENT

SOFTWARE QUALITY & SYSTEMS ENGINEERING PROGRAM. Quality Assurance Checklist

Process Improvement Plan

Teacher Training Concept

Minnesota Health Insurance Exchange (MNHIX)

Leveraging SharePoint for Project, Program, and Portfolio Management

Big Data Analytics; The value of the right action. April 1 st, 2014 Edwin Steenvoorden VP Business Analytics & Information Strategy

Transcription:

Dr. Ernest Wallmüller Wolfgang Höh Rule 16 Integrated Project Management Qualität & Informatik www.itq.ch Copyright Qualität & Informatik 2005

Context QA Management process areas Engineering & Support process areas Organization s Std. es Lessons Learned, Performance Data Project s Defined Coordination, commitments, issues; Product Architecture for Structuring Teams Coordination & collaboration; Shared vision & IT structure IT mgmt for engineering processes; Integrated work environment people & practices Identified risks IT Risk Taxonomies & Parameters, Status, Mitigation, and Corrective Action Basic Project Management process areas Copyright Qualität & Informatik / www.itq.ch 2

- Policy / Scope / Purpose QA! Policy For AVL it is important to establish a project management which works according to defined processes. To improve the uniformity of project s defined processes these should be deviated from the organizational standard processes.! Scope All SW producing units in AVL SBU MES.! Purpose The purpose of is to establish and manage the project and the involvement of the relevant stakeholders according to an integrated and defined project s process, which is tailored from the organization s set of standard process rules. Copyright Qualität & Informatik / www.itq.ch 3

Exercise: Familiarization QA! Method: Plenum! Timing: 20! Form: Brainstorming and discussion! Documents: none! Deliverable: Documentation on flipchart (trainer)! Questions: I. How do we know that the process is performing well? II. Who of you has experiences with this process? Which one? III. What are the most relevant work products? Copyright Qualität & Informatik / www.itq.ch 4

Exercise: Roles, Activities, Work Products QA! Method: Individual! Timing: 10! Form: Individual elaboration! Documents: Rule 16; form: next foil! Deliverable: Filled in form Question: I. Based on your experience, the prior discussion and the process definition list the involved roles, the performed activities, and the produced work products. Copyright Qualität & Informatik / www.itq.ch 5

Roles, Activities, Work Products QA Roles Activities Work Products Copyright Qualität & Informatik / www.itq.ch 6

Roles, Activities, Work Products QA Roles PL-DP HOD Stakeholders Activities Establish the Project s defined Use Organizational Assets for Planning Project Activities Integrate Plans Manage the Project using the Integrated Plans Contribute to the Organizational Assets Manage Stakeholder Involvement Manage Dependencies Resolve Coordination Issues Work Products Project work product plan Lessons learned report Findings and actions list Copyright Qualität & Informatik / www.itq.ch 7

with Practices QA Contribute to the OPAL Use Org. Assets for Planning Proj. Activities Manage the Project using the Integrated Plans Establish the Project s def. Integrate Plans Manage Stakeholder Involvement Manage Dependencies Resolve Coordination Issues Copyright Qualität & Informatik / www.itq.ch 8

QA Tasks Practice Task Work Products Establish the Project s def. Contribute to the OPAL Use the Project s defined Tailor the selected Software Development Contribute to the OPAL Project work product plan Lessons learned report Copyright Qualität & Informatik / www.itq.ch 9

QA Tasks Practice Task Work Products Coordinate and Collaborate with Relevant Stakeholders Manage Stakeholder Involvement Resolve Coordination Issues Collect and monitor all relevant commitments Resolve deviations from commitments Identify critical dependencies and address them to the relevant stakeholders Findings and actions list of relevant commitments Findings and actions list of resolved deviations Findings and actions list of critical dependencies Copyright Qualität & Informatik / www.itq.ch 10

Exercise: Task Description QA! Method: Group work! Timing: 30 group work, 15 presentation & discussion (comparative discussion of group results)! Form: Group elaboration! Documents: Rule 16: Rule 23: Rule 27:! Deliverable: Task description on flipchart! Question: I. Describe the selected task _T01 Tailor the selected Software Development according to the tailoring guidelines using the presented description technique ("next foil). Copyright Qualität & Informatik / www.itq.ch 11

Task Description Technique QA Input ID Task Name Description Roles Tools Method/Technique Output Copyright Qualität & Informatik / www.itq.ch 12

Task Details Tailor the selected Software Development QA Input OPAL Customer requirements Organizational process needs and objectives Operational environment Business environment _T01 Roles PL-DP: Tailor the selected Software Development Description Document the project s defined process: The Project work product plan documents which parts of the Software Development es are used and which are not. Project specific agreements and definitions are made. Responsible for task _T01 Tools Template Template Project_WorkProduct_Plan.xlt Method/Technique Base on P (ev. adapted to Rule 27 ) Rule 23 Best Practices/Lessons-learned/ Output Project work product plan (accepted Project s defined ) Copyright Qualität & Informatik / www.itq.ch 13

The ing QA Project Information Organization Inputs External Inputs Identify Project Characteristics Project Tech. Requirements Bldg Blocks & Tailoring Rules Acquisition Requirements Project Characteristics Choose & Tailor Building Blocks Project Defined Software Tailored Project Plan Specific Development Copyright Qualität & Informatik / www.itq.ch 14

Tailoring Guidance QA Characteristic Software Project Effort Project Type Number of Interfaces (External) Project Type Software Project Effort Project Risk Project Type Quantification < 20 MW Further Release 0 Further Rel. < 5 MY Low Further Release with dynamic Requirement Set Area URS, SRS: URS/SRS in a simple form, eg. descriptive text in CQ Entry or a simple Word document P is omitted Monitoring is done in project status meetings and documented in Meeting Reports P DR1 and DR2 are not necessary. Interface document (SID) no necessary P DR4 is omitted Effect on Task/WP URS in ClearQuest P DR4 is omitted P DR Protocols can be tailored Monitoring of requirements progress and efforts Copyright Qualität & Informatik / www.itq.ch 15

QA Tasks Practice Task Work Products Identify Project Characteristics Make Tailoring Decisions Identify Project Characteristics Make Tailoring Decisions Project Characteristics Document Tailored Project Plan (with rationales) Copyright Qualität & Informatik / www.itq.ch 16

Rule 16: Work Products and Templates QA WP Id Type Description Resp. Link to Template _W01 M Project Characteristics Document PL-DP Template Project_Characteristics.xlt _W02 M Tailored Project Plan PL-DP Template Project_WorkProduct_Plan.xlt Copyright Qualität & Informatik / www.itq.ch 17

Project Types 1/2 QA There are 4 ways to develop/deliver SW is for a customer project: a) Customer projects gets one or more already released SW product(s) b) Customer specific extensions in addition to standard SW products are required and developed with an upcoming SW development project (P for main- or subrelease) c) Customer specific extensions in addition to standard SW products are required, they are developed in a separate development environment (CSE branch in source code management system); Results are merged into the next subrelease/mainrelease of the affected product in order minimize future maintenance effort Copyright Qualität & Informatik / www.itq.ch 18

Project Types 2/2 QA a) Customer specific extensions in addition to standard SW products are required, they are developed in a separate development environment (CSE branch in source code management system); Results are N merged into the next subrelease/mainrelease of the affected product. In this case, maintenance is done by the team, who developed the CSE branch during warranty and if the customer ordered specific maintenance Copyright Qualität & Informatik / www.itq.ch 19

Rule 16: Work Products and Templates QA WP Id Type Description Task Id Resp. Link to Template _W01 M Project work product plan _T01 PL-DP Template Project_WorkProduct_Plan.xlt _W02 M Lessons Learned Report _T02 PL-DP Template Lessons_learned_and_best_practices.xls _W03 M Findings and Actions List _T03, _T04, _T05 PL-DP Template P_Projects_Action_List.xlt Copyright Qualität & Informatik / www.itq.ch 20

Rule 16: Concluding Discussion QA What was important for you concerning this Rule? Copyright Qualität & Informatik / www.itq.ch 21

Any Questions QA Copyright Qualität & Informatik / www.itq.ch 22