Managing and Leading Software Projects

Informationen zum Autor Richard E. (Dick) Fairley , PhD, is founder and Principal Associate of Software Engineering Management Associates (SEMA), a firm specializing in consulting services and training in software systems engineering, software project management, cost estimation, project planning and control techniques, risk management, and process assessment and improvement. He is also an Adjunct Professor of Computer Science and Engineering at Colorado Technical University in Colorado Springs, Colorado. He is a former associate dean, department head, director of software engineering, and professor of computer science at the OGI School of Science and Engineering in Beaverton, Oregon. Dr. Fairley has designed and implemented educational programs in universities and in industry, headed research programs in software engineering, and lectured to and consulted with many companies worldwide. Klappentext * The book is organized around basic principles of software project management: planning and estimating, measuring and controlling, leading and communicating, and managing risk.* Introduces software development methods, from traditional (hacking, requirements to code, and waterfall) to iterative (incremental build, evolutionary, agile, and spiral).* Illustrates and emphasizes tailoring the development process to each project, with a foundation in the fundamentals that are true for all development methods.* Topics such as the WBS, estimation, schedule networks, organizing the project team, and performance reporting are integrated, rather than being relegating to appendices.* Each chapter in the book includes an appendix that covers the relevant topics from CMMI-DEV-v1.2, IEEE/ISO Standards 12207, IEEE Standard 1058, and the PMI Body of Knowledge. Zusammenfassung The book is organized around basic principles of software project management: planning and estimating, measuring and controlling, leading and communicating, and managing risk. Introduces software development methods, from traditional (hacking, requirements to code, and waterfall) to iterative (incremental build, evolutionary, agile, and spiral). Inhaltsverzeichnis Preface xv 1 Introduction 1 1.1 Introduction to Software Project Management 1 1.2 Objectives of This Chapter 2 1.3 Why Managing and Leading Software Projects Is Difficult 2 1.3.1 Software Complexity 3 1.3.2 Software Conformity 4 1.3.3 Software Changeability 4 1.3.4 Software Invisibility 5 1.3.5 Team-Oriented Intellect-Intensive Work 6 1.4 The Nature of Project Constraints 9 1.5 A Workflow Model for Managing Software Projects 13 1.6 Organizational Structures for Software Projects 16 1.6.1 Functional Structures 16 1.6.2 Project Structures 17 1.6.3 Matrix Structures 17 1.6.4 Hybrid Structures 18 1.7 Organizing the Project Team 19 1.7.1 The System Engineering Team 19 1.7.2 The Software Engineering Team 20 1.8 Maintaining the Project Vision and the Product Vision 21 1.9 Frameworks Standards and Guidelines 22 1.10 Key Points of Chapter 1 23 1.11 Overview of the Text 23 References 24 Exercises 25 Appendix 1A: Frameworks Standards and Guidelines for Managing Software Projects 28 1A.1 The CMMI-DEV-v1.2 Process Framework 28 1A.2 ISO/IEC and IEEE/EIA Standards 12207 34 1A.3 IEEE/EIA Standard 1058 36 1A.4 The PMI Body of Knowledge 37 2 Process Models for Software Development 39 2.1 Introduction to Process Models 39 2.2 Objectives of This Chapter 42 2.3 A Development-Process Framework 42 2.3.1 Users Customers and Acquirers 43 2.3.2 System Requirements and System Design 46 2.3.3 Software Requirements Architecture and Implementation 47 2.3.4 Verification and Validation 50 2.4 Tailoring the System ...

List of contents

Preface.
 
1 Introduction.
 
1.1 Introduction to Software Project Management.
 
1.2 Objectives of This Chapter.
 
1.3 Why Managing and Leading Software Projects Is Difficult.
 
1.4 The Nature of Project Constraints.
 
1.5 A Workflow Model for Managing Software Projects.
 
1.6 Organizational Structures for Software Projects.
 
1.7 Organizing the Project Team.
 
1.8 Maintaining the Project Vision and the Product Vision.
 
1.9 Frameworks, Standards, and Guidelines.
 
1.10 Key Points of Chapter 1.
 
1.11 Overview of the Text.
 
References.
 
Exercises.
 
Appendix 1A: Frameworks, Standards, and Guidelines for Managing Software Projects.
 
2 Process Models for Software Development.
 
2.1 Introduction to Process Models.
 
2.2 Objectives of This Chapter.
 
2.3 A Development-Process Framework.
 
2.4 Tailoring the System Engineering Framework for Software-Only Projects.
 
2.5 Traditional Software Development Process Models.
 
2.6 Iterative-Development Process Models.
 
2.7 Designing an Iterative-Development Process.
 
2.8 The Role of Prototyping in Software Development.
 
2.9 Key Points of Chapter 2.
 
References.
 
Exercises.
 
Appendix 2A: Frameworks, Standards, and Guidelines for Software Development Process Models.
 
3 Establishing Project Foundations.
 
3.1 Introduction to Project Foundations.
 
3.2 Objectives of This Chapter.
 
3.3 Software Acquisition.
 
3.4 Requirements Engineering.
 
3.5 Process Foundations.
 
3.6 Key Points of Chapter 3.
 
References.
 
Exercises.
 
Appendix 3A: Frameworks, Standards, and Guidelines for Product Foundations.
 
4 Plans and Planning.
 
4.1 Introduction to the Planning Process.
 
4.2 Objectives of This Chapter.
 
4.3 The Planning Process.
 
4.4 The CMMI-DEV-v1.2 Process Area for Project Planning.
 
4.5 A Minimal Project Plan.
 
4.6 A Template for Software Project Management Plans.
 
4.7 Techniques for Preparing a Project Plan.
 
4.8 Key Points of Chapter 4.
 
References.
 
Exercises.
 
Appendix 4A: Frameworks, Standards, and Guidelines for Project Planning.
 
Appendix 4B: Annotated Outline for Software Project Management Plans, Based on IEEE Standard 1058.
 
5 Project Planning Techniques.
 
5.1 Introduction to Project Planning Techniques.
 
5.2 Objectives of This Chapter.
 
5.3 The Scope of Planning.
 
5.4 Rolling-Wave Planning.
 
5.5 Scenarios for Developing a Project Plan.
 
5.6 Developing the Architecture Decomposition View and the Work Breakdown Structure.
 
5.7 Guidelines for Designing Work Breakdown Structures.
 
5.8 Developing the Project Schedule.
 
5.9 Developing Resource Profiles.
 
5.10 Resource-Gantt Charts.
 
5.11 Estimating Project Effort, Cost, and Schedule.
 
5.12 Key Points of Chapter 5.
 
References.
 
Exercises.
 
Appendix 5A: Frameworks, Standards, and Guidelines for Project Planning Techniques.
 
6 Estimation Techniques.
 
6.1 Introduction to Estimation Techniques.
 
6.2 Objectives of This Chapter.
 
6.3 Fundamental Principles of Estimation.
 
6.4 Designing to Project Constraints.
 
6.5 Estimating Product Size.
 
6.6 Pragmatic Estimation Techniques.
 
6.7 Theory-Based Estimation Models.
 
6.8 Regression-Based Estimation Models.
 
6.9 Estimation T

Report

"This book is readable, informative, and well organized.... The material presented is up to date with respect to documents that were published at the time the book was written." (Computing Reviews, May 15, 2009)
 
"Mark it up and keep it on your bookshelf, and be sure to reference it frequently." (Computing Reviews, April 28, 2008)

Product details

• Authors: Re Fairley, Richard E Fairley, Richard E. Fairley, Richard E. (Software Engineering Manageme Fairley, FAIRLEY RICHARD E, Fairley Richard E.
• Publisher: Wiley, John and Sons Ltd
• Languages: English
• Product format: Hardback
• Released: 06.03.2009
• EAN: 9780470294550
• ISBN: 978-0-470-29455-0
• No. of pages: 512
• Subjects: Natural sciences, medicine, IT, technology > Technology > Electronics, electrical engineering, communications engineering; Informatik, Softwareentwicklung, computer science, Software Management, Electrical & Electronics Engineering, Elektrotechnik u. Elektronik, Programmierung u. Software-Entwicklung, Programming & Software Development, Software-Management, Programm- u. Projektmanagement, Program & Project Management