1. Proposal for a SW-PM Extension to the PMI PMBOK © Developed by Richard E. (Dick) Fairley for S2ESC, 2/10/2010 1

2. Dick Fairley Principal Associate of SEMA Consulting Adjunct Professor at Colorado Tech Author: Software Engineering Concepts & Managing and Leading Software Projects Member: PAB-Planning, PAB-IT, and EAB Former member of SESC & principal author (with Dick Thayer) of: o IEEE Std. 1058-1998: SPMP o IEEE Std. 1362-1998: ConOps 2

3. Motivations for Developing a SW-PM Extension to PMBOK (1) Many PMI certified project managers (PMPs) could improve their ability to manage projects that include development or modification of software by increasing their understanding of the methods, tools, and techniques used to manage projects that involve development or modification of software. note: this is the pitch to PMI 3

4. Motivations for Developing a SW-PM Extension to PMBOK (2) A SW-PM extension to PMBOK could: o provide a set of recommended practices for nascent and practicing software-systems project managers o provide a curriculum model for teaching training classes and courses in software project management o raise the visibility of and help promote the professional standing of software-systems project management 4

5. PMBOK Knowledge Areas* PMBOK has 9 Knowledge Areas: 1.Project Integration Management 2.Project Scope Management 3.Project Time Management 4.Project Cost Management 5.Project Quality Management 6.Project Human Resources Management 7.Project Communications Management 8.Project Risk Management 9.Project Procurement Management * The PMBOK GUIDE, Project Management Institute, 2008 5

6. PMBOK Process Areas Elements of the 9 KAs are grouped into 5 Process Groups: 1.Initiating Process Group 2.Planning Process Group 3.Executing Process Group 4.Monitoring and Controlling Process Group 5.Closing Process Group Process Group elements are specified in terms of Inputs; Tools and Techniques; and Outputs 6

7. Application Area Extensions PMI recognizes the need for application area extensions to PMBOK Topics in Appendix D of PMBOK include: o Need for Application Area Extensions o Criteria for Development of AAEs o Publishing and Format of AAEs o Process for Development and Maintenance of AAEs 7

8. Some Proposed Elements of a SW-PM AAE Develop a mapping of 16326 elements to KAs and process groups in PMBOK Develop a mapping of relevant topics in PMBOK to SWEBOK Provide an overview of and references to SW development process models in the Project Integration KA; cite 1074 and other relevant standards Cite system engineering considerations and cite 15288 in Scope Definition Add agile development to augment the WBS-based approach of PMBOK Include size measurement & regression-based estimation models to the Planning process group Indicate issues related to using Earned Value for tracking software projects in the Executing process group 8

9. Some Proposed Elements of a SW-PM AAE (2) Include typical metrics for software projects in the Executing process group; cite 1045 and other relevant standards Cite productivity factors and ranges of productivity in the Human Resources KA; cite relevant standards Add issues in risk management for software projects to the Risk Management KA; cite 16085 Specify typical software-specific inputs, tools and techniques, and outputs for elements of the process groups Include the 8 supporting processes from 12207, 1058, and 16326 Include an appendix of relevant IEEE Standards with annotations 9 note: this is a preliminary list of topics

10. Proposal Develop an S2ESC-sponsored proposal to PMI for a SW-PM application area extension to PMBOK Develop the SW-PM extension o with mappings and references to relevant IEEE Standards Make SW-PM an IEEE Recommended Practice o with or without PMI endorsement Note: this is not a proposal rewrite PMBOK but rather to augment it in various ways 10

11. Subsequent Activities? Develop augmented materials (EAB?) Offer training classes (PAB?) Provide SW-PM certification? 11