π Lecture 33 β ISO/IEC 12207:2008
π Overview: This lecture introduces ISO/IEC 12207:2008, the first international standard to provide a comprehensive set of life cycle processes for software. It establishes a common language and structure for all stakeholders involved in software development, based on principles of modularity and responsibility. The lecture details the three main process groupsβSystem Context Processes, Software Specific Processes, and Agreement Processesβand explains their sub-processes.
ποΈ Topics Covered
The lecture covers the definition and purpose of ISO/IEC 12207, its principles of modularity and responsibility, the classification of processes into three types (basic, support, organizational), the various modes of using the standard, the detailed breakdown of life cycle process groups (Agreement, Organizational Project-Enabling, Project, Technical, Software-Specific) including their sub-processes, the concept of tailoring, and the conditions for conformance.
π Lecture Summary
ISO/IEC 12207:2008
ISO/IEC 12207 is an ISO standard for software lifecycle processes. It is the first International Standard to provide a comprehensive set of life cycle processes, activities, and tasks for software that is part of a larger system, and for standalone software products and services. It was first introduced on August 1, 1995. The ISO 12207 standard establishes a process of lifecycle for software, including processes and activities applied during the acquisition and configuration of the services of the system. Each Process has a set of outcomes associated with it. The standard has the main objective of supplying a common structure so that the buyers, suppliers, developers, maintainers, operators, managers and technicians involved with the software development use a common language. This common language is established in the form of well-defined processes. ISO/IEC 12207 also provides a process that can be employed for defining, controlling, and improving software life cycle processes. The structure of the standard was intended to be conceived in a flexible, modular way so as to be adaptable to the necessities of whoever uses it.
π Definition β ISO/IEC 12207: An international standard that provides a comprehensive set of life cycle processes, activities, and tasks for software.
Modularity
Modularity means processes with minimum coupling and maximum cohesion.
π Definition β Modularity: A principle where processes are designed with minimum coupling (low interdependence) and maximum cohesion (high internal focus).
Responsibility
Responsibility means to establish a responsibility for each process, facilitating the application of the standard in projects where many people can be legally involved. The set of processes, activities and tasks can be adapted according to the software project. These processes are classified in three types: basic, for support and organizational. The support and organizational processes must exist independently of the organization and the project being executed. The basic processes are instantiated according to the situation.
π Definition β Responsibility: A principle that establishes clear ownership for each process, facilitating legal and operational clarity in projects.
Modes of Use
This International Standard can be used in one or more of the following modes:
- By an organization: To help establish an environment of desired processes. These processes are to be supported by an infrastructure of methods, procedures, techniques, tools and trained personnel. The organization may then employ this environment to perform and manage its projects and progresses systems through their life cycle stages. In this mode this International Standard is used to assess conformance of a declared, established set of life cycle processes to its provisions.
- By a project: To help select, structure and employ the elements of an established set of life cycle processes to provide products and services. In this mode this International Standard is used in the assessment of conformance of the project to the declared and established environment.
- By an acquirer and a supplier: To help develop an agreement concerning processes and activities. Via the agreement, the processes and activities in this International Standard are selected, negotiated, agreed to and performed. In this mode this International Standard is used for guidance in developing the agreement.
- By organizations and assessors: To perform assessments that may be used to support organizational process improvement.
Life Cycle Process Groups
The processes are organized into two major groups:
- System Context Processes
- Software Specific Processes
Each process of this standard is described in terms of the following attributes:
- The title conveys the scope of the process as a whole
- The purpose describes the goals of performing the process
- The outcomes express the observable results expected from the successful performance of the process
- The activities are a list of actions that are used to achieve the outcomes
- The tasks are requirements, recommendations, or permissible actions intended to support the achievement of the outcomes
Agreement Processes
These processes define the activities necessary to establish an agreement between two organizations. There are two agreement processes:
- Acquisition Process: If the Acquisition Process is invoked, it provides the means for conducting business with a supplier of products that are supplied for use as an operational system, of services in support of an operational system, or of elements of a system being developed by a project.
- Supply Process: If the Supply Process is invoked, it provides the means for conducting a project in which the result is a product or service that is delivered to the acquirer.
Organizational Project-Enabling Processes
There are five organizational project-enabling processes:
- Life Cycle Model Management Process
- Infrastructure Management Process
- Project Portfolio Management Process
- Human Resource Management Process
- Quality Management Process
The Organizational Project-Enabling Processes manage the organization's capability to acquire and supply products or services through the initiation, support and control of projects. They provide resources and infrastructure necessary to support projects and ensure the satisfaction of organizational objectives and established agreements. They are not intended to be a comprehensive set of business processes that enable management of the organization's business.
Project Processes
In this International Standard, the project has been chosen as the context for describing processes concerned with planning, assessment and control. The principles related to these processes can be applied in any area of an organization's management. There are two categories of Project Processes:
-
Project Management Processes: Used to establish and evolve project plans, to assess actual achievement and progress against the plans and to control execution of the project through to fulfillment. Individual Project Management Processes may be invoked at any time in the life cycle and at any level in a hierarchy of projects, as required by project plans or unforeseen events. Simply put, the Project Management Processes are used to plan, execute, assess and control the progress of a project. There are two:
- Project Planning Process
- Project Assessment and Control Process
-
Project Support Processes: Provide a specific focused set of tasks for performing a specialized management objective. They are all evident in the management of any undertaking, ranging from a complete organization down to a single life cycle process and its tasks. There are five:
- Decision Management Process
- Risk Management Process
- Configuration Management Process
- Information Management Process
- Measurement Process
Technical Processes
There are ten technical processes:
- Stakeholder Requirements Definition Process
- System Requirements Analysis Process
- System Architectural Design Process
- Implementation Process
- System Integration Process
- System Qualification Testing Process
- Software Installation Process
- Software Acceptance Support Process
- Software Operation Process
- Software Maintenance Process
- Software Disposal Process
The Technical Processes are used to define the requirements for a system, to transform the requirements into an effective product, to permit consistent reproduction of the product where necessary, to use the product, to provide the required services, to sustain the provision of those services and to dispose of the product when it is retired from service. The Technical Processes define the activities that enable organizational and project functions to optimize the benefits and reduce the risks that arise from technical decisions and actions. These activities enable products and services to possess the timeliness and availability, the cost effectiveness, and the functionality, reliability, maintainability, usability and other qualities required by acquiring and supplying organizations. They also enable products and services to conform to the expectations or legislated requirements of society, including health, safety, security and environmental factors.
Software-Specific Processes
The Software-Specific Processes are:
- Software Implementation Processes
- Software Support Processes
- Software Reuse Processes
Software Implementation Processes
The Software Implementation Processes are used to produce a specified system element (software item) implemented in software. This process transforms specified behavior, interfaces and implementation constraints into actions that create a system element implemented as a software product or service, otherwise known as a software item. This process results in a software item that satisfies architectural design requirements through verification and stakeholder requirements through validation. For the purpose of clear description, processes are sometimes decomposed into smaller pieces. Some processes are decomposed into activities and/or lower-level processes. A lower-level process is described when the decomposed portion of the process itself satisfies the criteria to be a process.
π Definition β Software Item: A system element implemented as a software product or service.
The sub-processes of the Software Implementation Process are:
- Software Requirements Analysis Process: A lower-level process of the Software Implementation Process. The purpose is to establish the requirements of the software elements of the system.
- Software Architectural Design Process: A lower-level process of the Software Implementation Process. The purpose is to provide a design for the software that implements and can be verified against the requirements.
- Software Detailed Design Process: A lower-level process of the Software Implementation Process. The purpose is to provide a design for the software that implements and can be verified against the requirements and the software architecture and is sufficiently detailed to permit coding and testing.
- Software Construction Process: A lower-level process of the Software Implementation Process. The purpose is to produce executable software units that properly reflect the software design.
- Software Integration Process: A lower-level process of the Software Implementation Process. The purpose is to combine the software units and software components, producing integrated software items, consistent with the software design, that demonstrate that the functional and non-functional software requirements are satisfied on an equivalent or complete operational platform.
- Software Qualification Testing Process: A lower-level process of the Software Implementation Process. The purpose is to confirm that the integrated software product meets its defined requirements.
Software Support Processes
The Software Support Processes provide a specific focused set of activities for performing a specialized software process. A supporting process assists the Software Implementation Process as an integral part with a distinct purpose, contributing to the success and quality of the software project. There are eight of these processes:
- Software Documentation Management Process
- Software Configuration Management Process
- Software Quality Assurance Process
- Software Verification Process
- Software Validation Process
- Software Review Process
- Software Audit Process
- Software Problem Resolution Process
Software Reuse Processes
The Software Reuse Process Group consists of three processes that support an organization's ability to reuse software items across project boundaries. These processes are unique because, by their nature, they operate outside the bounds of any particular project:
- Domain Engineering Process
- Reuse Asset Management Process
- Reuse Program Management Process
Tailoring Process
Tailoring is not a requirement for conformance to the standard. In fact, tailoring is not permitted if a claim of "full conformance" is to be made. If a claim of "tailored conformance" is made then tailoring is to be performed as required by this process. The purpose of the Tailoring Process is to adapt the processes of this International Standard to satisfy particular circumstances or factors that:
- Surround an organization that is employing this International Standard in an agreement
- Influence a project that is required to meet an agreement in which this International Standard is referenced
- Reflect the needs of an organization in order to supply products or services
It should be noted that tailoring may diminish the perceived value of a claim of conformance to this standard. This is because it is difficult for other organizations to understand the extent to which tailoring may have deleted desirable provisions. An organization asserting a single-party claim of conformance to this standard may find it advantageous to claim absolute conformance to a smaller list of processes rather than tailored conformance to a larger list of processes.
π Definition β Tailoring: The process of adapting the standard's processes to satisfy particular circumstances or factors; it is not permitted for "full conformance" but is required for "tailored conformance."
π‘ Why this matters: Tailoring is a critical concept because it introduces a trade-off between flexibility and the perceived value of conformance. Students must understand that while tailoring allows adaptation, it can weaken the credibility of a conformance claim, making it often better to claim full conformance to a smaller, well-defined set of processes.
β Key Takeaways
The most critical takeaway from this lecture is understanding ISO/IEC 12207 as the foundational international standard for defining software life cycle processes, built on the principles of modularity (minimum coupling, maximum cohesion) and responsibility. You must be able to distinguish between the three main process types (Agreement, Organizational, and Project/Technical processes) and their specific sub-processes, especially the key groups like Agreement (Acquisition & Supply), Project Management (Planning & Assessment), and Software Implementation (Requirements, Design, Construction, Integration, Testing). A critical distinction to remember is the difference between "full conformance" and "tailored conformance" in the Tailoring Process, understanding that tailoring is not permitted for full conformance and can diminish the standard's perceived value. Finally, recognize the standard's flexible, modular nature allowing it to be used by organizations, projects, acquirers/suppliers, and assessors for different purposes, including process improvement and conformance assessment.
π§ Quick Revision Questions
- What are the two basic principles on which the ISO 12207 standard is based?
- List the two Agreement Processes defined in ISO 12207 and explain the primary goal of each.
- What is the difference between "full conformance" and "tailored conformance" to the standard?
- Name the three main groups of Software-Specific Processes and explain the unique characteristic of the Software Reuse Processes.
- What are the six sub-processes of the Software Implementation Process, and what is the final purpose of the Software Qualification Testing Process?
π Lecture 34 β SPICE β ISO/IEC 15504
π Overview: This lecture introduces SPICE (Software Process Improvement and Capability dEtermination), also known as ISO/IEC TR Standard 15504. It is a major international initiative for software process assessment, providing a reference model with both process and capability dimensions. The lecture covers the structure of processes, capability levels, process attributes, the assessment process, and how SPICE is used for process improvement and capability determination.
ποΈ Topics Covered
The lecture covers the original goals of the SPICE project, the ISO/IEC 15504 reference model including its process dimension (five process categories) and capability dimension (six levels from Incomplete to Optimizing), the nine process attributes, the four-point rating scale for assessment, steps in the assessment process, the assessment model and tools, assessor qualifications, the two main uses of SPICE (process improvement and capability determination), and the acceptance and limitations of ISO/IEC 15504 compared to CMM/CMMI.
π Lecture Summary
SPICE β ISO/IEC 15504
SPICE is a major international initiative to support the development of an International Standard for Software Process Assessment. It is also known as ISO/IEC TR Standard 15504. SPICE is an acronym for Software Process Improvement and Capability dEtermination.
π Definition β SPICE: A major international initiative to develop an International Standard for software process assessment, also known as ISO/IEC TR 15504.
Principal/Original Goals of SPICE Project
The primary goals were to develop a working draft for a standard for software process assessment, to conduct industry trials of the emerging standard, and to promote the technology transfer of software process assessment into the software industry world-wide. The first goal was achieved in June 1995 with the release of Version 1 of a draft standard. The SPICE documents were published as ISO/IEC TR 15504 - Software Process Assessment. The primary impetus for assessment use came from acquirers of large, critical software-intensive systems, notably in defense and telecommunications. The increasing number of assessment approaches and their use in commercially-sensitive areas motivated the development of this International Standard. All industries now depend on software for competitive advantage, and growth requires meeting international standards and world's best practices.
ISO/IEC 15504
ISO/IEC 15504 is the reference model for maturity models, consisting of capability levels which consist of process attributes and further consist of generic practices. Assessors use this model to place the evidence they collect during assessment so they can give an overall determination of the organization's capabilities for delivering products (software, systems, and IT services). The reference model defines a process dimension and a capability dimension.
π Definition β Process Dimension: Shows processes divided into five process categories.
π Definition β Capability Dimension: Defines capability levels measured using process attributes.
Processes
The process dimension shows processes divided into five process categories:
- Customer-supplier
- Engineering
- Supporting
- Management
- Organization
It is expected that the process categories will expand, particularly for IT service and enterprise process categories.
Capability Levels and Process Attributes
For each process, ISO/IEC 15504 defines a capability level on the following scale:
| Level | Name |
|---|---|
| 5 | Optimizing Process |
| 4 | Predictable Process |
| 3 | Established Process |
| 2 | Managed Process |
| 1 | Performed Process |
| 0 | Incomplete Process |
The capability of processes is measured using process attributes. The international standard defines nine process attributes:
π Definition β Process Attributes: Nine attributes used to measure the capability of processes.
- 1.1 Process Performance
- 2.1 Performance Management
- 2.2 Work Product Management
- 3.1 Process Definition
- 3.2 Process Deployment
- 4.1 Process Measurement
- 4.2 Process Control
- 5.1 Process Innovation
- 5.2 Process Optimization
Each process attribute consists of one or more generic practices, which are further elaborated into practice indicators to aid assessment performance.
Assessment of Process Attributes
Each process attribute is assessed on a four-point (N-P-L-F) rating scale:
- Not achieved (0 - 15%)
- Partially achieved (>15% - 50%)
- Largely achieved (>50% - 85%)
- Fully achieved (>85% - 100%)
The rating is based upon evidence collected against the practice indicators, which demonstrate fulfillment of the process attribute.
Assessments
ISO/IEC 15504 provides a guide for performing an assessment. This includes:
- The assessment process
- The model for assessment
- Any tools used in the assessment
Assessment Process
A conformant assessment method must be used. The actual method is not specified in the standard. The standard places requirements on qualification and competence of assessors and provides general guidance, which must be supplemented by formal training and detailed guidance during initial assessments.
Steps in Assessments:
- Initiate an assessment (assessment sponsor)
- Select assessor and assessment team
- Plan the assessment, including processes and organizational unit to be assessed (lead assessor and assessment team)
- Pre-assessment briefing
- Data collection
- Data validation
- Process rating
- Reporting the assessment result
An assessor can collect data by various means including interviews, documents and quality records, and statistical process data. The assessor validates this data to ensure it is accurate and completely covers the assessment scope. The assessor assesses this data using their expert judgment against a process's base practices and the capability dimension's generic practices in the process rating step. Process rating requires exercising expert judgment, which is why there are requirements on assessor qualifications and competency. The process rating is presented as a preliminary finding to the sponsor to ensure agreement that the assessment is accurate.
Assessment Model
The process assessment model (PAM) is the detailed model used for an actual assessment. It is an elaboration of the process reference model (PRM) provided by the process lifecycle standards. The PAM is based on the process reference model for systems: ISO/IEC 15288. The standard allows other models to be used if they meet ISO/IEC 15504's criteria, including a defined community of interest and meeting requirements for content (process purpose, process outcomes, and assessment indicators).
π Definition β Process Assessment Model (PAM): The detailed model used for an actual assessment, elaborated from the Process Reference Model (PRM).
Tools Used in the Assessment
There exist several assessment tools. The simplest comprise paper-based tools that incorporate the assessment model indicators, including base practice indicators and generic practice indicators. Assessors write down assessment results and notes. There are also computer-based tools that present indicators and allow users to enter assessment judgment and notes in formatted screens, as well as automate collated assessment results (process attribute ratings) and create reports.
Assessor Qualification and Competency
For a successful assessment, the assessor must have a suitable level of relevant skills and experience. These include:
- Personal qualities such as communication skills
- Relevant education, training and experience
- Specific skills for particular categories, e.g., management skills for the management category
- ISO/IEC 15504 related training and experience in process capability assessments
Uses of SPICE
ISO/IEC 15504 can be used in two contexts:
- Process improvement
- Capability determination (= evaluation of supplier's process capability)
Process Improvement
ISO/IEC 15504 can be used to perform process improvement within a technology organization. Process improvement is always difficult, and initiatives often fail, so it is important to understand the initial baseline level (process capability level) and assess the situation after an improvement project. ISO 15504 provides a standard for assessing the organization's capacity to deliver at each stage. The reference framework provides a structure for defining objectives, which facilitates specific programs to achieve these objectives. It specifies requirements for improvement programs and provides guidance on planning and executing improvements.
π Definition β Process Capability Level: The initial baseline level of an organization's process capability, used to understand the starting point for process improvement.
Capability Determination
An organization considering outsourcing software development needs to have a good understanding of the capability of potential suppliers to deliver. ISO/IEC 15504 can be used to inform supplier selection decisions. It provides a framework for assessing proposed suppliers, as assessed either by the organization itself or by an independent assessor. ISO/IEC 15504 specifies the high level requirements for covering target process profiles. Target process profiles are particularly important in contexts where the organization (e.g., a government department) is required to accept the cheapest qualifying vendor. This also enables suppliers to identify gaps between their current capability and the level required by a potential customer, and to undertake improvement to achieve contract requirements (i.e., become qualified).
π Definition β Target Process Profiles: Profiles specifying the required capability level for processes, important for contexts like government procurement where the cheapest qualifying vendor must be accepted.
Acceptance of ISO/IEC TR 15504
ISO/IEC 15504 is publicly available through National Standards Bodies and has the support of the international community. Thousands of assessments have been performed to date. Major sectors like automotive, space, and medical systems lead the pace with industry relevant variants. Domain-specific models like Automotive SPICE and SPICE 4 SPACE can be derived from it. There have been many international initiatives to support take-up such as SPICE for small companies.
On the other hand, ISO/IEC 15504 has not yet been as successful as the models developed by the Software Engineering Institute. Reasons include:
- ISO/IEC 15504 is not available as free download but must be purchased from ISO; CMM and CMMI are free downloads from the SEI website
- The CMMI is actively sponsored by the US Department of Defense
- The CMM was created first and reached critical market share before ISO 15504 became available
- The CMMI has subsequently replaced the CMM and incorporates many ideas of ISO/IEC 15504 but retains benefits of the CMM
- ISO/IEC 15504 was created in a development context, making it difficult to apply in a service management context; work has started to develop an ITIL-based process reference model
You can join the SPICE users' group at www.spiceusergroup.org. Every year an international conference is held on SPICE, named the SPICE Conference.
π‘ Why this matters: Understanding the differences in adoption and acceptance between SPICE/ISO 15504 and CMM/CMMI helps professionals choose the right assessment framework and recognize the competitive advantages each model offers.
β Key Takeaways
SPICE (ISO/IEC 15504) is an international standard for software process assessment that defines a two-dimensional reference model with five process categories and six capability levels (0 to 5). The nine process attributes, each with generic practices, are assessed on a four-point N-P-L-F rating scale to determine capability. The assessment process involves eight steps from initiation to reporting, requiring qualified assessors with specific skills and training. SPICE is used for both process improvement (to establish baselines and track progress) and capability determination (to evaluate and select suppliers). Despite its international support and domain-specific variants like Automotive SPICE, ISO/IEC 15504 has not achieved the same adoption as CMM/CMMI due to factors including cost, sponsorship, and timing.
π§ Quick Revision Questions
- What are the five process categories in the ISO/IEC 15504 process dimension?
- List the six capability levels from lowest to highest as defined in ISO/IEC 15504.
- What are the nine process attributes used to measure process capability?
- Describe the four-point rating scale (N-P-L-F) used for assessing process attributes, including the percentage ranges.
- What are the two main contexts in which ISO/IEC 15504 can be used, and briefly explain each.
π Lecture 35 β Process Assurance
π Overview: This lecture defines process assurance as the collective activities carried out during product development to ensure methods and techniques are integrated, consistent, and correctly applied. It details the critical components of planning and organization necessary for successful process assurance, including project teams, standards, scheduling, and communication. The lecture concludes with an examination of the primary causes of failure in process assurance efforts, emphasizing management failures over technical ones.
ποΈ Topics Covered
The lecture begins by defining process assurance and its emphasis on cost, time, technical requirements, testing measurements, and prototyping. It then details ten key components of planning and organization for process assurance: project team, project standards, schedule monitoring, project tracking, estimation, effective communication, steering committee, project risks, measurement, and integrated technology. The lecture concludes by analyzing four major causes of failure in process assurance: lack of management support, lack of user involvement, lack of project leadership, and lack of measures of success.
π Lecture Summary
Process Assurance
Process assurance consists of the collective activities carried out while developing a product to ensure that the methods and techniques used are integrated, consistent, and correctly applied. Emphasis is given to cost, time, technical requirements, testing measurements, and prototyping. Process assurance involves the interrelationships of several different components, and depending on how these are managed, they can have a major positive impact on the products. Once an effective process assurance program is put in place and shown to be beneficial, then emphasis can be placed in making verification and validation strategies effective and in improving the quality of the products. Successful process assurance is based on planning and organization, which have several important components.
Components of Planning and Organization
1. Project Team
The project team is the project managerβs only means of reaching the project goals. Selection of team members is a vital step to the success of the project. The size of the team depends on the size and complexity of the project. It is important to identify the blend of the technical knowledge and the experience required for the successful completion of the project. Special attention should be paid to creating team composition that fosters mutual respect among team members and maintains good team morale.
2. Project Standards
Before the project is started, the team should establish standards for activities such as requirements gathering, developing design, and conducting unit tests. Standards or guidelines should also be established for quality control activities such as walk-throughs, reviews, and inspections. Many companies follow IEEE Software Engineering standards or have their own internally developed standards. The standards should be flexible enough to be applied to large or small projects. Any deviations from the standards should be approved by the project team, and the reason for such deviation should be noted in the minutes of the project meetings.
3. Schedule Monitoring
Stringent deadlines for the project are frequently established by management, end users, a project sponsor, or a client with no regard to the reality of achievement. For this reason, the project start date, milestones, and completion date should be negotiated upfront. If the unrealistic date is accepted and the project activities are then made to fit within this time frame, the quality of the project certainly will suffer. The key to an βon-timeβ completion of project lies in the ability to identify the critical path before starting the project. The critical path of a project is where problems that may affect the overall schedule are faced. To define the critical path, you should develop systematic work breakdown structures which identify task groupings, task sequences, and entrance/exit criteria for each task. They assist in selecting the correct skilled resources and ensure no activity is forgotten. Once you have defined a critical path, review the tasks and schedule with the project team members and other significantly impacted individuals, who are the stakeholders. Avoid the most common mistake of adding another resource to shorten or meet the schedule, as this usually increases overhead and reduces efficiency. Overtime can be effective for a short period, but longer periods can exhaust the team. It is possible to minimize risk by managing your resources, especially never putting your best programmers on the critical path.
π Definition β Critical Path: The sequence of project activities where problems that may affect the overall schedule are faced.
4. Project Tracking
There are several project-tracking tools available on the market which give project progress information and provide a view of the total project schedule at a glance. Some of these tools have features to do task dependencies and estimations. These features allow the project manager to evaluate the impact of a delay in the completion of any individual activity within the project. Such tools are excellent vehicles in giving early warnings for project delays so there are no surprises at the end.
5. Estimation
The project manager must be capable of understanding any assumptions in the project, what is possible, and what is financially desirable. This will result in a fine-tuning of schedule estimates, thus creating more realistic estimates. Time estimates are not foolproof, as activities are many times not clearly understood or defined. Allow time for resource management and unforeseen events like illness of a team member; such contingencies should be viewed as reserved time. Revise estimates at the end of each major phase and if there are any changes in scope, cost, or schedules encountered, notify management and obtain appropriate approvals.
6. Effective Communication
Two-way communication between management and the project team is a critical interpersonal skill. An effective project manager must have the skills to listen, observe, and give guidance to the team. During a time constraint situation, the project manager should be able to delegate responsibilities but also give guidance to control stress levels. The success of team harmony and good rapport depends on the project manager's ability to encourage open communication frequently and resolve any conflict through informal negotiation.
7. Steering Committee
A steering committee is responsible for defining project policy, reviewing project milestones, and evaluating risk factors. Members should represent all impacted areas of the business and should be knowledgeable enough to make informed technological decisions. If project features are changed or new features are added, the steering committee is responsible for evaluating the impact and authorizing, rejecting, or deferring the changes. The steering committee should be in charge of system management tasks such as estimating maintenance time, deciding on support from operations, managing data, and forming a Configuration Control Board (CCB) that manages the impact of changes.
8. Project Risks
Systems projects are risky if project expectations are not controlled or if the outcome was ill-defined. While risk cannot be eliminated, many companies identify and address risk factors upfront. Project risks can be assessed in three categories: business risk, technology risk, and project size risk. Risks can be minimized by implementing controls from initiation, ensuring preestablished development standards are followed, providing project management training, and reducing scope through incremental or phased development. Technical risk is encountered when using new technology for the first time and can be controlled by appointing a qualified technical project leader, implementing a strong quality control group, and getting additional expertise from outside consultants.
π Definition β Technical Risk: A project risk encountered when the project team utilizes a new technology like new hardware or a new development methodology for the first time.
9. Measurement
Establishing measurement criteria against which each phase of the project will be evaluated is vital. When the exit criteria are well-defined, it is sufficient to evaluate the outcome of each phase. If the outcome does not meet the performance criteria, the project manager should control the project by evaluating problems and implementing new processes. Preestablished quality goals can serve as measurement criteria. It is important to know that certain elements cannot be controlled by project management, such as selection of the wrong technology, proceeding without understanding business needs, underestimation of the learning curve, and a lack of strategic plans.
10. Integrated Technology
A strategy for Integrated Technology (IT) should be considered by management in relation to other business needs. This empowers management to react to operational needs and take inventory of current systems and technical staff quality. When planning a project, the system architecture with its data groups, structures, processes, and dependencies must be considered. Parts of the new system that will interface with existing systems should be identified. If the technology is new and not well understood, allowances to incorporate experiments should be made in the overall project plan and schedule.
Causes of Failure in Process Assurance
There are many reasons why process assurance efforts fail, most of which are related to management failures rather than technical failures:
- Lack of Management Support
- Lack of User Involvement
- Lack of Project Leadership
- Lack of Measures of Success
1. Lack of Management Support
Management very often assigns a project and then forgets about it or fails to allocate adequate resources. This lack of project sponsorship leads to serious morale problems and lost resources. The project sponsor is usually a member of senior management responsible for researching regulatory issues, obtaining project funding, and managing business implications. Since the sponsor acts as the main advocate, lack of support from this individual is extremely serious.
2. Lack of User Involvement
When end users are not involved in the design and development phases, many assumptions are made regarding the requirements, especially when requirements are ambiguous. This situation can be corrected by assigning a user liaison responsible for getting support, providing detailed user requirements, providing feedback, managing user expectations, and identifying user acceptance criteria.
3. Lack of Project Leadership
The single most important cause of failure is due to lack of project leadership. Consequences include IT staff not understanding business needs, project scope and goals not being defined, performance not being controlled, and improper selection of team members. Ensuring the project is in the hands of a good project manager is vital. An effective project manager must have responsibility, authority equal to responsibility, and access to necessary resources. The project manager should be flexible, responsive, effective in coordinating activities, credible, and respected by team members.
π‘ Why this matters: The balance of responsibility, authority, and access to resources is a critical success factor for any project manager.
4. Lack of Measures of Success
Failure also occurs when project success is based only on development efficiency measures (e.g., on time and within budget) while effectiveness measures (e.g., technical performance and quality) are ignored. To evaluate project success, objective measurements should be developed, such as completing the project on time, within budget, and with all required features. Each element of the success criteria must be defined and agreed upon prior to starting the project.
β Key Takeaways
Process assurance ensures that development methods and techniques are integrated, consistent, and correctly applied, with emphasis on cost, time, technical requirements, testing, and prototyping. Ten core components of planning and organization are essential: project team selection, project standards, schedule monitoring using critical path and work breakdown structures, project tracking tools, realistic estimation with contingencies, effective two-way communication, a steering committee, risk assessment and minimization, measurement against exit criteria, and integrated technology planning. The four major causes of process assurance failure are all management-related: lack of management support, lack of user involvement, lack of project leadership, and lack of measures of success. A project manager must have balanced responsibility, authority, and access to resources, while success must be measured by both efficiency (on time, within budget) and effectiveness (technical performance, quality) criteria.
π§ Quick Revision Questions
- What are the five areas of emphasis in process assurance?
- What is the critical path and why is it important for schedule monitoring?
- What three categories can project risks be assessed into?
- What are the four primary causes of failure in process assurance?
- What three attributes must be treated equally for a project manager to be effective?