The document outlines elements of a development plan and quality assurance plan for a software project. The development plan covers deliverables, interfaces, methodology, standards, milestones, organization, facilities, risks, and costs. The quality assurance plan defines quality goals, review activities, tests, and configuration management. It also discusses classes of development risks like scheduling and requirements, and provides examples of top risks. Finally, it describes a risk management process and potential actions to prevent and resolve risks through prevention, identification, and resolution. The overall objectives are to plan adequately for successful and timely project completion through scheduling, resource allocation, risk resolution, quality activities, and management control.

1. Development and Quality Plan

2. Development Plan: Elements
1. Project products, specifying “deliverables”
2. Project interfaces
3. Project’s methodology and development tools
4. Software development standards and procedures
5. Map of the development process

3. Development Plan: Elements
6. Project milestones
7. Project staff organization and coordination with
external participants
8. Required development facilities
9. Development risks and risk management actions
10. Control methods
11. Project cost estimates

4. Quality Assurance Plan: Elements
• A quality assurance plan sets out the desired product
qualities and how these are assessed and defines the most
significant quality attributes.
• The quality assurance plan should define the quality
assessment process.
• It should set out which organizational standards should be
applied and, where necessary, define new standards to be
used.

5. Quality Assurance Plan: Elements
Elements:
1. List of quality goals
2. Review activities
3. Software tests
4. Acceptance tests for software externally developed
5. Configuration management plans: tools, procedures, and
dates for version release

6. Classes of Software Development Risks
1. Scheduling and timing risks
2. System functionality risks
3. Subcontracting risks
4. Requirement management risks
5. Resource usage and performance risks
6. Personnel management risks

7. Top 10 Software Risk Items (SRI)
1. Developing wrong software functions
2. Unrealistic schedules and budgets
3. Developing wrong user interface
4. Gold plating
5. Continuing stream of requirement
changes

8. Top 10 Software Risk Items (SRI)
6. Shortfalls in externally furnished
components
7. Shortfalls in externally performed tasks
8. Personnel shortfalls
9. Real-time performance shortfalls
10. Straining computer science capabilities

9. Risk Management Process
Activities are triggered due to:
• New projects
• Changes or additions to ongoing projects
• Feedback form monitoring the projects

10. Risk Management Process

11. Risk Management Actions [Galin2004]
No. Risk management actions (RMA)
Internal risk management
Prevention Identify Risks
early on
resolution
1 Detailed analysis of the requirements and
estimated schedules and costs
X
2 Efficient project organization, adequate staff
and team size
X
3 Personal Training X
4 Arranging for take over in case of turnover
and unanticipated workloads
X
5 User participation in the development
process
X
6 User participation in the development
process
X
7 Intensive SQA measures such as inspections,
X design reviews, and benchmarking
X

12. Risk Management Actions [Galin2004]
No. Risk management actions (RMA)
Internal risk management
Prevention Identify Risks
early on
resolution
8 Periodic checking for timely availability of firm
professionals currently occupied with other
projects
X
9 Arranging for participation of professional staff
members with experience with SRIs
X
10 Scheduling SRI-related activities as early as
possible
X
11 Prototyping SRI related modules or
applications
X
12 Preparing scenarios for complicated SRI-
related modules or applications
X
13 Simulating related modules or applications X

13. No. Risk management actions (RMA)
Subcontracting
Prevention Identify Risks
early on
resolution
1 Preparing comprehensive and through
contracts with subcontractors and suppliers,
including contract reviews
X
2 Participating in internal progress control and
SQA activities of subcontractors (incorporated
in the contract)
X
3 Arranging for “loans” of professionals with
specialized knowledge and experience if the
need arises
X
4 Hiring consultants to support the team in the
absence of sufficient know-how and
experience
X

14. No. Risk management actions (RMA)
Customer
Prevention Identify Risks
early on
resolution
1 Formulating comprehensible and thorough
contracts with customers, including contract
reviews
X
2 Negotiate with the customer to change
requirements with high risk
X
3 Negotiate with the customer to change
schedule elements with high risk
X

15. Objectives (Quality + Process)
• Planning is meant to prepare adequate foundations for successful
and timely completion of the project.
• The planning process includes:
1. Scheduling development activities and estimating the
required manpower resources and budget
2. Recruiting team members and allocating development
resources
3. Resolving development risks
4. Implementing required SQA activities
5. Providing management with data needed for project
control