|
|
Process Warehouse Index: (1-25)
The following is a complete alphabetical listing of process topics on QAI's Process WarehouseSM |
|
Baseline for Current Performance
- A 9-step process focused on calculating a quantitative level of performance for any IT activity.
Requirements – Defining Requirements Quickly for Software Maintenance
- 2005 Best-of-the-Best Award Practice – Enabling Business Analysts to generate detailed requirements in a short period of time to facilitate the rapid implementation of a new software version.
Change - Building a Quantitative Dashboard to Drive Change
- A 4-step process for identifying the key indicators that management needs to use to assure a change occurs as desired.
Change – Process for Changing and Deploying a Process
- A 4-step process outlining a people oriented process for changing work processes successfully.
Change - How to Get Buy-In
- A 5-step process based on professional marketing approaches for use in getting those impacted by change to accept the change.
Change - Identifying Risks
- This practice is designed to help change makers identify the risks of both making a change and the risks associated with not making a change.
Change – Managing and Controlling Software Change
- A 4-step process for those responsible for software maintenance to identify, evaluate, approve each change and assure each change meets current IT standards.
Change – Identify and Minimize the Impact of Change
- Making a change can impact project staff, support staff, other applications, budgets and schedules. The impact needs to be identified and controlled to minimize the impact.
Changing Work Environment - Prepare Workers
- A high-level strategic approach designed to orient IT management to support rapid change in an IT environment.
Configuration Items – Identifying
- This 2-step process is designed to identify the configuration items and the identification of those items subject to configuration control.
Configuration Management Board
- A 3-step process designed to determine who should be on a configuration control board and the responsibilities the board members should be assigned.
Configuration Management Plan for In-House Projects
- A 2-step process for creating a standard for software projects’ configuration management plan.
Configuration Management Standard for Contracted Projects
- This 2-step process is designed to establish a standard for building a configuration management plan for software projects contracted to outside organizations.
Configuration Management Policy
- A 2-step process for creating an IT policy establishing the direction for the IT organization’s configuration management program.
Configuration Management – Process for Establishing a CM Program
- This 4-step practice is designed to establish a configuration management program including configuration identification, control, status accounting, and audits.
Contingency Plan – Development
- A 5-step process for building a contingency plan that contains detailed roles, responsibilities, teams, and procedures associated with restoring an IT system following a disruption.
Contingency Plan - Maintaining IT
- A 3-step process designed to assure that the IT contingency plan accurately reflects systems requirements, procedures, organizational structure, and policy.
Contingency Planning for Software Systems
- A high-level, 7-step process covering the development of a contingency planning policy for a system through testing and maintaining that plan.
Contingency Planning – Strategy
- A 3-step process for IT management to identify the stakeholders in contingency planning, determine what plans are needed, and then integrating contingency planning into the software life cycle.
Contingency Planning – Considerations for Common IT Platforms
- This process addresses the technical requirements for platforms including desktop computers, servers, Web sites, local and wide area networks, distributed systems, and mainframe systems.
COTS – Risks Associated with Selecting Specific COTS
- A 3-step process for measuring the magnitude of risks associated with specific COTS software packages based on the selection criteria for acquiring those packages.
Decision Making Process
- A process for making IT decisions based on the facts associated with the decision, the experience of the decision maker, and the IT organization’s prior experience with similar decisions.
Defects - Conducting Formal Inspections
- A 5-step process for inspecting an IT product to identify changes (i.e., defects) between the product specifications and the product produced by an IT process.
Documenting a User Identified Problem
- A 4step process for documenting the problem, determining the magnitude of the problem, identifying the cause of the problem, and then developing a solution to resolve the problem.
Ensuring Quantitative Data is Valid Data
- This process is designed to help decision makers determine whether or not the data on which they intend to make a decision can be relied upon for the decision. |
|
| |
|
|
|
|
