Malte Foegen Project Management 06 Management IT M a t u r i t y S e r v i c e s Good Practices for Teaching Groups Good Practices Discuss in the teams Ask and discuss immediately do not wait until the end of the presentation Slides should have numbers Have time keeper & moderator Provide references to sources Remember to bring VGA cables - 2-2007 wibas IT Maturity Services GmbH 1
The purpose of Management is to manage the requirements of the project's products and product components and to identify inconsistencies between those requirements and the project's plans and work products Manage (SG 1) - 3-2007 wibas IT Maturity Services GmbH Mange means that requirements are managed and inconsistencies with project plans and work products are identified Obtain an Understanding of (SP 1.1) Manage (SG 1) Identify Inconsistencies Between Project Work and (SP 1.5) Obtain Commitment to (SP 1.2) Manage Changes (SP 1.3) Maintain Bi-directional Tracebility of (SP 1.4) Tracebility Matrix or Tracking System - 4-2007 wibas IT Maturity Services GmbH 2
Management helps to answer important questions SP 1.1: Customer defines and agrees to requirements SP 1.2: Team agrees to requirements SP 1.3: Requirement changes are managed SP 1.4: are mapped to work products SP 1.5: The Mapping is used to identify inconsistencies between project work and requirements What are the requirements? Did we understand the requirements and can we build it? Anything new? What work products depend on which requirement? Which requirements have been included in this release? Any requirement not yet implemented? Any code that does not have a requirement? - 5-2007 wibas IT Maturity Services GmbH Management is the project s firewall Why do we do it? Define and control scope of the project. Gain consensus with customer on what to develop. Relate project s work to requirements Advice and Guidance Don't stay short on requirements and define them clearly. Define as early as possible, adding/changing later will always cost more. Customer involvement is mandatory. Set up change control early to control scope creep. Be sure to manage expectations (the project is successful if the expectations are met). Relate your work to your requirements - 6-2007 wibas IT Maturity Services GmbH 3
The project manager or the requirements manager is responsible for managing the requirements RUP: Project Manager The Project Manager plans, manages and allocates resources, shapes priorities, coordinates interactions with customers and users, and keeps the project team focused. RUP: Change Control Manager The Change Control Manager oversees the change control process and is also responsible for defining. He should understand configuration management principles. He should be skilled in estimating cost and schedule impacts of change requests. He should be able to communicate effectively in order to negotiate scope changes and in order to determine how each change request should be handled and by whom. - 7-2007 wibas IT Maturity Services GmbH Typical Work Products for Management SP 1.1 Obtain an Understanding of 1. Lists of criteria for distinguishing appropriate requirements providers 2. Criteria for evaluation and acceptance of requirements 3. Results of analyses against criteria 4. An agreed-to set of requirements SP 1.2 Obtain Commitment to 1. impact assessments 2. Documented commitments to requirements and requirements changes SP 1.3 Manage Changes 1. status 2. database 3. decision database Traceability Matrix or Tracking System SP 1.5 Identify Inconsistencies Between Project Work and Reqmts 1. Documentation of Inconsistencies including sources, conditions and rationale 2. Corrective actions SP 1.4 Maintain Bidirectional Traceability of 1. traceability matrix 2. tracking system - 8-2007 wibas IT Maturity Services GmbH 4
Generic Practices Important: Generic Practices must be applied and interpreted for each Process Area GP 2.10: Senior Management Reviews are real reviews, not just reading reports - 9-2007 wibas IT Maturity Services GmbH Levels 4 and 5 Statistical Process Control Identify the problem in the process or in the environment understand past process performance, past product quality, and past service quality predict future process performance, future product quality, and future service quality Capability control chart Original zone of quality control Chronic waste Quality Improvement New zone of quality control New zone of quality control Less chronic waste Quality improvement - 10-2007 wibas IT Maturity Services GmbH 5
CMMI is a tool for improvement not a goal in itself Do not ask what do we need to do to suffice CMMI? Do ask: What tips does CMMI provide us what we don t do or what we could improve? Solutions must be adequate that means: they must fulfill the business goals of the organization - 11-2007 wibas IT Maturity Services GmbH Management in context CM REQM PMC SP 1.1 Product and product component requirements RD Alternative solutions TS Product components PI Product Customer Product components, work products, verification and validation reports VER VAL Customer needs - 12-2007 wibas IT Maturity Services GmbH 6
Home shopping system: Read it Task: 1. 5 min: Explanation of exercise 2. 25 min: Download and read the exercise Goal: Understand the project task Exercise - 13-2007 wibas IT Maturity Services GmbH Home shopping system: Manage the requirements (80+30=110 min) Task and Results: 1. (15 min) Determine which work products you will establish and maintain for managing the requirements. List of work products 2. (45 min, Subteam 1) Define your change management process Template to handle a Change Request Definition of the change request procedure (activity diagram) 3. (45 min, Subteam 2) Produce a list of the initial requirements. Template to cover the initial requirements (SP 1.1, SP 1.2) Filled-out template with the requirements of the project simulator 4. (2x10=20 min) Review results in your team 5. Present selected results in class (30 min) Goal: Apply requirements management Exercise - 14-2007 wibas IT Maturity Services GmbH 7
Trademarks and Service Marks Capability Maturity Model; Capability Maturity Modeling; Carnegie Mellon, CMM; and CMMI are registered in the U. S. Patent and Trademark Office by Carnegie Mellon University. IDEAL; Personal Software Process; PSP; SCAMPI; SCAMPI Lead Assessor; SCAMPI Lead Appraiser; SEI; SEPG; Team Software Process; and TSP are service marks of Carnegie Mellon University. intacs is a registered trademark by the International Assessor Certification Scheme Special permission to use CMMI for Development, Version 1.2 (CMU/SEI-2006-TR-008 ESC-TR-2006-008), copyright 2006 by Carnegie Mellon University, in the combination of CMMI and ITIL is granted by the Software Engineering Institute. The SEI and CMU do not directly or indirectly endorse wibas IT Maturity Services GmbH s work. IT Maturity Services is a registered trademark by wibas IT Maturity Services GmbH wibas IT Maturity Services is official SEI Partner of the Software Engineering Institute of the Carnegie Mellon University for SCAMPI appraisals and CMMI training. For inquiries, call: wibas IT Maturity Services GmbH Yvonne Fischer Customer Relations Manager Otto-Hesse-Str. 19 B 64293 Darmstadt Germany Tel: 0049-6151 - 50 33 49-21 Fax: 0049-6151 - 50 33 49-33 yfischer@wibas.de - 15-2007 wibas IT Maturity Services GmbH Revision History Target status: finished Template-Version: 3.6 Rev. no. State Date Comments Responsible 1.0 Finished 03.10.2004 Initial version Malte Foegen 1.1 Finished 21.01.2006 Revision History added, current template Malte Foegen 1.2 Finished 23.12.2007 Layout update Malte Foegen 1.3 Finished 18.01.2008 Added some extra explanation Malte Foegen 1.4 Finished 23.01.2009 Updated exercise Malte Foegen - 16-2007 wibas IT Maturity Services GmbH 8
Otto-Hesse-Str. 19 B 64293 Darmstadt Germany Phone +49 / 6151 / 50 33 49-0 Fax +49 / 6151 / 50 33 49 33 www.wibas.de Hintermettlen 7 6318 Walchwil Suisse Phone +41 / 41 / 51122-90 Fax +41 / 41 / 51122-91 www.wibas.ch - 17-2007 wibas IT Maturity Services GmbH 9