Difference between revisions of "Managing and Leading Software Projects"

From SEBoK
Jump to navigation Jump to search
 
m (Text replacement - "SEBoK v. 2.9, released 13 November 2023" to "SEBoK v. 2.9, released 20 November 2023")
 
(25 intermediate revisions by 4 users not shown)
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>
 +
 
 +
==Usage==
 +
This source is considered a primary reference for the following articles:
 +
*[[System Life Cycle Process Models: Vee]]
 +
*[[Team Capability]]
 +
*[[Systems Engineering and Software Engineering]]
 +
*[[The Nature of Software]]
 +
*[[Key Points a Systems Engineer Needs to Know about Software Engineering]]
 +
*[[Systems Engineering and Project Management]]
 +
*[[The Nature of Project Management]]
 +
*[[System Life Cycle Process Models: Iterative]]
  
 
==Annotation==
 
==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.
 
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)===
+
<center>'''SEBoK v. 2.9, released 20 November 2023'''</center>
 
 
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.
 
 
 
  
 
[[Category:Primary Reference]]
 
[[Category:Primary Reference]]

Latest revision as of 23:27, 18 November 2023

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

Usage

This source is considered a primary reference for the following articles:

Annotation

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.

SEBoK v. 2.9, released 20 November 2023