Chapter 7: SQA Plan and Project Plan

Chapter 7: SQA Plan and Project Plan

7.1 Introduction

  • Key to Success: Planning ahead is crucial for success, specifically for Software Quality Assurance (SQA) and project plans.

  • Focus on Plans: This chapter covers:

    • Preparation processes and contents of SQA plans and project plans.

  • SQA Plan (SQAP):

    • Focuses on tasks required by the SQA function for the upcoming year.

    • Aids in estimating resources needed for SQAP completion.

    • Resource estimates rely on professional knowledge/experience requirements, allowing appropriate staffing for the SQA function.

  • Project Plan:

    • Covers tasks the project team performs throughout the project lifecycle (development and operation stages).

    • Contains critical elements:

    • Activities schedule

    • Resource estimates per activity

    • The two plans are interconnected, necessitating coordination.

    • SQAP activities often coordinate with relevant project plan activities.

  • Updating Plans: Coordination persists during execution by updating plans based on project progress and change requests.

  • Sections Overview:

    • 7.2 & 7.3: Preparing an SQAP and its contents.

    • 7.4 & 7.6: Preparing a project plan.

    • 7.5: Case illustrating the importance of an updated project plan.

    • 7.7: Special cases for small and internal projects.

  • Standards Reference:

    • IEEE Std. 730-2014: Section 6.33 & Annex C on SQA planning.

    • ISO/IEC/IEEE Std. 12207 Section 6.3.1 on project planning.

    • ISO/IEC Std. 90003 Section 5.4.2 on quality management system planning.

7.2 The Process of Preparing an SQA Plan

  • SQAP Overview: A comprehensive document that directs SQA function activities for a year and is subject to updates based on new circumstances.

  • Preparation Activities:

    1. Determine Outline Elements: Identify relevant SQAP outline elements for stakeholders through discussions.

    2. Prepare Standard Document: Construct the SQAP based on required elements and stakeholder needs while focusing on project risks.

    3. Finalize SQAP: Confirm the SQAP with project managers.

    4. Analyze Product Risks: Identify risks related to software products to users and activities to mitigate them, estimating the success of risk management.

    5. Resource Estimation: Estimate resources necessary for the SQAP, encompassing team size, activity schedules, skills, and equipment needs.

    6. Define Metrics: Establish metrics for evaluating software quality and SQA function performance, aligned with organizational objectives.

  • Updating Activities:

    1. Monitor SQA function activities and project progress, revising the SQAP as needed.

    2. Adapt SQAP due to project changes.

    3. Create periodic reports on SQAP progress for management.

7.3 The SQAP Elements

  • Comprehensive Outline: SQAP elements categorized into three groups:

    • SQA process implementation activity elements

    • Product assurance activity elements

    • Process assurance activity elements

7.3.1 SQA Process Implementation Activity Elements
  • Management Deficiencies Correction: Address inadequacies in management quality policies and monitoring processes.

  • Software Product Risks: Evaluate risks associated with software products and mitigate strategies.

  • Development Equipment and Tools: Create lists of necessary tools and training requirements for project staff.

  • Standards and Practices: Review applicable standards and conventions for all software projects and specific ones per project.

  • Resource and Schedule Estimates: Provide quantifiable estimates based on workload projections for each professional group and equipment needed.

7.3.2 Product Assurance Activity Elements
  • Project Plan Conformance: Evaluate project plans against standards and contracts.

  • Product Evaluations: Assess software development products according to requirements and quality standards.

  • Acceptability Evaluations: Determine acceptability criteria for software products, factoring in installation strategies and maintenance.

  • Maintenance Plan Evaluations: Review plans against contract requirements and standards.

  • Measurement Plans: Design measurement plans and data collection strategies relevant to product risks and quality objectives.

7.3.3 Process Assurance Activity Elements
  • Life Cycle Process Conformance: Evaluate life cycle processes for adequate definitions, responsibilities, and improvements.

  • Environment Evaluations: Ensure development and testing environments meet project requirements.

  • Subcontractor Conformance: Assess subcontractor involvement in project implementation.

  • Development Process Measurements: Collect data on development, testing, and operations measurements.

  • Staff Skills Assessment: Evaluate required project staff skills and identify training needs.

7.4 The Process of Preparing a Project Plan

  • Project Plan Overview: A comprehensive document that serves throughout the project lifecycle, including development and operational stages.

  • Objectives of Project Plans: Define essential project goals summarized in Frame 7.2:

    1. Successful and timely project performance adhering to standards and contract requirements.

    2. Maintaining high-quality project products.

    3. Providing management with necessary data for effective control.

  • Phases of Project Plan Preparation:

    • Data collection

    • Compilation of the project plan

    • Review of the project plan

    • Updates due to change requests or methodological updates.

  • Proposal Materials: Recommendations to base project planning on proposal items while recognizing possible invalid data due to elapsed time.

7.5 Jack Thanks His Department Manager – A Mini Case

  • Context: Jack Bora, a project manager, is tasked with managing the Pagoda project after a delayed start.

  • Initial Approach: He relies on pre-prepared proposal materials instead of creating a detailed project plan.

  • Manager's Demand: Ordered to develop fresh project development and quality plans highlighting risks associated with the delay and changes in team availability.

  • Ultimate Analysis: Updating plans revealed resource shortages and necessary timeline adjustments contributing to successful project management.

7.6 The Elements of the Project Plan

  • Standards Reference: Based on ISO/IEC 90003-2014 and ISO/IEC/IEEE Std. 12207-2008.

  • Group Classification:

    • Development Plan Elements

    • Quality Plan Elements

7.6.1 Development Plan Elements
  • Components include:

    • Project Products: Deliverables and mapping of resources.

    • Control Methods: Monitoring practices like progress reports and meetings.

    • Process Mapping: Detailed activity descriptions, logical sequences, and duration estimates.

    • Resource Estimation: Professional resources required and their quantification.

    • Staff Organization: Workforce structure and flexibility considerations.

    • Project Interfaces: Coordination between software packages and teams.

    • Project Risks: Assessing product and development risks within defined classes.

    • Milestones: Important events in the development process, defining products and timing.

    • Cost Estimation: Incorporating internal/external resource costs and budget updates.

    • Methodology and Tools: Determining project methodologies and tools per phase.

    • Standards and Procedures: Identifying applicable standards as per project contracts.

    • Facilities: Hardware and tools needed during the project duration.

    • Documentation Control: Listing and controlling project documents.

    • Security Measures: Document and code security protocols.

7.6.2 Elements of the Quality Plan
  • Elements include:

    • Quality Goals: Define substantive requirements of quality, preferably in quantitative terms.

    • Procedures: Outline quality assurance procedures and work instructions.

    • Project Stage Criteria: Define what constitutes completion at each development stage.

    • Project Lifecycle SQA Activities: Planning and listing SQA activities, including reviews and tests.

    • Configuration Management: Define tools and procedures for version control and release timing.

    • Measurement Activities: Define software quality metrics and responsibilities for monitoring.

    • Approval Responsibility: Designate personnel authorized to approve project outputs.

    • Training Requirements: Identify needed training for team members on new tools.

    • Change Management: Outline procedures for handling changes across project stages.

7.7 Project Plans for Small Projects and Internal Projects

  • Avoiding Bureaucracy: Many project leaders downplay plan preparation for small/internal projects to evade bureaucracy.

  • Recommendations: Small projects may not require full-scale plans based on duration and identified risks.

  • Advantages of Planning:

    • Better understanding of tasks and responsibilities.

    • Enhanced commitments and customer-developer relationships.

    • Improved project control.

7.7.1 Development and Quality Plans for Small Projects
  • Criteria for Planning: Guidelines evolve around project duration, complexity, and signature requirements.

  • Element Recommendations: Suggested elements for development and quality plans include risk listing, deliverables, milestones, and cost estimates.

7.7.2 Development Plans for Internal Projects
  • Common Pitfalls: Internal projects often avoid proper planning leading to detrimental consequences.

  • Case Illustration: Example demonstrating issues from unplanned internal projects, emphasizing the benefits of structured planning.

  • Final Insight: Full-scale plans for internal projects support reputation management, timely project completion, and cost control.

Summary

  1. SQA Process Implementation Elements: Activities focus on correcting deficiencies, managing product risks, tools, and estimating resources.

  2. Product Assurance Elements: Conformance evaluations for plans, products, maintenance, and measurement plans.

  3. Objectives of Project Plans: Foundations for project execution, quality assurance, and managerial oversight.

  4. Development Plan Elements: Essential components ensuring comprehensive coverage of the project lifecycle and resource management.

  5. Quality Plan Elements: Critical quality assurance strategies ensuring project deliverables meet set standards.

  6. Project Risks Classification: Articulating differences between product and development risks.

  7. Software Risk Management Process: Integrates identification, evaluation, planning, implementation, and monitoring.

  8. Benefits of Planning for Small Projects: Strengthened understanding and accountability in project execution.

  9. Advantages for Internal Projects: Risk mitigation, budget management, and reputation assurance resulting from diligent project planning.