Applying IEEE Standard 1058 for Software Project Management Plans and IEEE Standard 1540 for Software Risk Management
1 day
Software project management plans are the backbone of a successful project. This course shows you how to make software project management plans a reality in your organization.
IEEE standard 1058-1998 is a standard that provides a framework for writing software project management plans (SPMPs). IEEE standard 1540-2001 is very helpful in assessing and managing the risks on a project.
This is a practical workshop with many exercises to help you immediately apply the concepts in the IEEE standards. Your instructor will be a certified instructor in the software engineering field.
You will learn the terminology, process, and challenges of standards in the real world. As a result of attending this seminar, you should have a good working knowledge of how to write good project plans and what it takes to to make them a reality in your organization. From this workshop, you will leave with a practical understanding of IEEE Standards 1058-1998 and 1540-2001 and how to tailor and apply them in your projects.
- Learn best practices in software engineering
- Learn how to write good project plans
- Understand the role of risks on project
- Understand the key issues in applying the standards
- Learn how to tailor the standards to fit your own needs
- Quit reinventing the wheel and use proven approaches that have already been fully described for you
- Advance your career by reinforcing your knowledge of standards.
- Process analysts
- Software engineers
- Project managers
- Documentation specialists
- QA analysts
- Testers and test team leaders
Prerequisites
-
The program requires IT knowledge or experience.
-
You will need to have a copy of the applicable IEEE Standards for your reference.
Program Information
This course is presented on an in-house basis only unless offered as a special public course. Contact us for information about how to bring this course into your organization.
Module STDA - Introducing the IEEE Standards
- Course Objectives
- What is Systems Engineering?
- What is Software Systems Engineering?
- Why Should We Use Standards?
- Basic Principles for Standards
- ISO Compared to IEEE
- How Standards are Developed
- Organization of the SESC Standards
- Clauses
- Normative vs. Informative
- What Is in a Standard?
- What Is Not in a Standard?
- Where Standards Can Be Obtained?
- How to Tailor and Apply Standards
- Final Thoughts
- Other Resources
Module STDG - Applying IEEE Standard 1058 for Software Project Management Plans
- SW Engineering Project Management Functions and Objectives
- Project Tradeoffs
- Project Planning
- Why is a Project Plan Important?
- Why is Planning Not Adequately Done?
- What is Project Planning?
- Project Planning Activities
- Setting Project Goals and Objectives
- Developing Policies
- Forecasting Future Situations
- Risk Assessment
- Determining Possible Courses of Action
- Making Planning Decisions
- Plans for Contractors and Subcontractors
- Preparing Budgets
- Documenting Project Plans
- Introducing IEEE 1058-1998
- The Purpose of the Standard
- Major Structure of the SPMP
- Managerial Process Plans
- Start-up Plan
- Work plan
- Work Breakdown Structure
- Control Plan
- Risk Management Plan
- Project Closeout Plan
- Technical Process Plan
- Development Process Model
- Technical Methods, Tools and Techniques
- Infrastructure Plan
- Product Acceptance Plan
- Supporting Process Plans
- Configuration Management
- Verification and Validation Plan
- Software Documentation Plan
- Quality Assurance Plan
- Reviews and Audits Plan
- Problem Resolution Plan
- Subcontractor Management Plan
- Process Improvement Plan
- Additional Plans
- Plan Annexes
- Plan Index
- Levels of Compliance
- Reviewing the SPMP
- Planning Beyond the SPMP
- Other Planning Questions to Ask
- Recommendations for Implementation
- Organizing
- Organizing Activities
- Identifying and Grouping Project Functions, Activities and Tasks
- Things That Impact Project Organization
- Describing Organizational Relationships and Interfaces
- Two Views of Project Team Structure
- Selecting a Project Structure
- Conventional Structure - Line Organization
- Functional Project Organization
- Project Organization
- Matrix Project Organization
- Creating Position Descriptions
- Defining Responsibilities and Authority
- Establishing Position Qualifications
- Project Staffing
- Project Staffing Activities
- Filling Project Positions
- Assimilating New Personnel
- Training Personnel
- General Staff Development
- Evaluating Project Performance
- Terminating Project Assignments
- Project Leadership
- What is Project Leadership?
- Components of Leadership
- Project Leadership Activities
- Controlling
- Questions the PM Should Ask
- Requirements for Controlling
- Control Activities
- Developing Performance Standards
- Establishing Monitoring and Reporting Systems
- Measuring and Analyzing Results
- Taking Corrective Actions
- Application to IEEE 12207 (Annex B)
- Points of Correlation
- Summary
Module STDH - Summary of Applying IEEE Standard 1058 for Software Project Management
- SW Engineering Project Management Functions and Objectives
- Project Tradeoffs
- Top Ten Points
- Why Projects Fail
- Questions for Reflection
- Summary
Module STDI - Applying IEEE Standard 1540 for Software Risk Management
- What is Risk?
- Components of Risk
- Risk Characteristics
- Risk Exposure
- What is Risk Management?
- Objectives of Risk Management
- Effective Risk Management
- Elements of Risk Management
- Project Risks
- Determining Root Causes and Risks
- Issue that Impact Risk Management
- Risk Management and Project Management
- IEEE Standard 1540 for Software Risk Management
- Purpose of the Standard
- Major Structure of the Standard
- Limitations of the Standard
- Prerequisites
- A Risk Management Process
- Risk Identification
- Direct vs. Inverse Risk Identification
- The Team Approach to Risk Identification
- Sources of Risk Information
- Identifying Schedule Risks
- Identifying Cost Risks
- Factors that Influence Cost and Schedule Risks
- Identifying Requirement Risks
- Methods for Identifying Requirement Risks
- Computer Software and System Risks
- Methods to Identify Quality Risks
- Logistical and Operational Risks
- Identifying Logistical and Operational Risks
- Risk Analysis
- The Risk Watch List
- Assessment of Impact
- Treatment of Risk
- Risk Avoidance
- Risk Acceptance
- Risk Control
- Contingency Planning
- Risk Transfer
- Increasing Understanding
- Estimating Risk Impacts and Avoidance Costs
- Monitoring and Controlling Risks
- Planning a Risk Management Program
- The Risk Management Program Plan
- Risk Management Plan Outline
- The Risk Action Request
- The Risk Action Request - Considerations
- Risk Action Request Outline
-
The Risk Treatment Plan
-
The Risk Treatment Plan Outline
-
-
Applying the Risk Management Process to IEEE12207
-
Related Resources
-
Summary: Objectives of Risk Management
Module STDJ - Risk Analysis Techniques
- Risk Analysis in IEEE 1540-2001
- What is Risk?
- The Nature of Risk
- Three Views of Risk
- The Elements of Risk
- Risk Assessment
- Why is Risk Assessment Important?
- SEI Risk Taxonomy
- Performing a Project Risk Assessment
- Step 1 - Assemble Participants
- Step 2 - Present Tutorial, if Needed
- Step 3 - Answer Questionnaires
- Step 4 - Tabulate Scores
- Step 5 - Plot Scores on a Kiviat Chart
- Step 6 - Summarize Risk Findings
- Step 7 - Present Risk Assessment Findings
- Assessing Technical Risks
-
- Likelihood of Failure
- Impact of Failure
- Ways to Apply the Results
-
- Assessing Mission Risk
- Root Cause Analysis Using Fishbone Diagrams
- How Can This Information Be Used?
- When is Risk Assessment Performed?
- Who Performs Risk Assessment?
- Who Owns Risk Assessment?
Module STDK - Risk Summary
- Top Ten Points
- Questions for Reflection
Resources
- Glossary
- Course notebook with slides, worksheets, checklists, complete examples and supporting text
- You will have the basic information needed to plan projects based on risk.