Difference between revisions of "Managing and Leading Software Projects"

From SEBoK
Jump to navigation Jump to search
 
Line 1: Line 1:
<blockquote>Fairley, R.E. 2009. Managing and Leading Software Projects. Hoboken, New Jersey:  John Wiley & Sons.</blockquote>
+
<blockquote>Fairley, R.E. 2009. ''Managing and Leading Software Projects''. Hoboken, NJ, USA:  John Wiley & Sons.</blockquote>
  
 
==Annotation==
 
==Annotation==

Revision as of 15:08, 14 September 2011

Fairley, R.E. 2009. Managing and Leading Software Projects. Hoboken, NJ, USA: John Wiley & Sons.

Annotation

Organizing Teams to Perform Systems Engineering (Knowledge Area)

This text is organized into four major themes of managing and leading engineering projects: 1) planning and estimating; 2) measuring and controlling; 3) risk management; and 4) leading, motivating, and communicating. Planning and estimating includes identifying roles, responsibilities, and authority of project personnel; estimating schedules and needed numbers of personnel; process models for software development; and organizing the project team. Measuring and controlling addresses product and process measures and the ways in which teams contribute to, and are affected by measurement and control. Risk management addresses risk identification techniques, risk analysis and prioritization, risk mitigation strategies, and risk management at the organization level. Leading, motivating, and communicating addresses teams, teamwork, motivation, leadership, communication, and organizational issues. The text concludes with 15 guidelines for organizing and leading software engineering teams. Although the context and examples in the text are based on software projects, the material is applicable to all kinds of systems engineering projects.

Systems Engineering and Project Management (Knowledge Area)

This text is organized into four major themes of managing and leading engineering projects: 1) planning and estimating; 2) measuring and controlling; 3) risk management; and 4) leading, motivating, and communicating. A major theme of the text is bridging the gap between engineers and project managers. Chapter topics include process models, project foundations, plans and planning, project planning techniques, estimation techniques, measuring and controlling work products, measuring and controlling work processes, managing project risk, teams and teamwork, and organizational issues. Each chapter includes an appendix that summarizes the topics relevant to the chapter from CMMI-DEV-v1.2; ISE/IEC/IEEE Standard 12207; IEEE/EIA Standard 1058; and the PMI Body of Knowledge. Although the context and examples in the text are based on software projects, the material is applicable to all kinds of systems engineering projects.

Systems Engineering and Software Engineering (Knowledge Area)

This text is organized into four major themes of managing and leading engineering projects: 1) planning and estimating; 2) measuring and controlling; 3) risk management; and 4) leading, motivating, and communicating. A major theme of the text is bridging the gap between engineers and project managers. Chapter topics include process models, project foundations, plans and planning, project planning techniques, estimation techniques, measuring and controlling work products, measuring and controlling work processes, managing project risk, teams and teamwork, and organizational issues. Each chapter includes an appendix that summarizes the topics relevant to the chapter from CMMI-DEV-v1.2; ISE/IEC/IEEE Standard 12207; IEEE/EIA Standard 1058; and the PMI Body of Knowledge. Although the context and examples in the text are based on software projects, the material is applicable to all kinds of systems engineering projects.