Glossary
Know What You Say, Say What You Mean
Understanding the language of IT projects can be challenging, with specialised terms and jargon frequently used in project delivery. This section provides concise definitions to align project teams and stakeholders.
Knowledge Area | Term | Acronym | Definition | Category |
---|---|---|---|---|
Process Analysis | 5 Whys | A problem-solving technique used to identify the root cause of an issue by asking 'Why?' five times in succession. | Techniques | |
Process Analysis | 5S | 5S | A Lean methodology creates an organised, clean, and efficient workplace through five steps: Sort, Set in order, Shine, Standardise, and Sustain. | Methodologies, Frameworks, and Approaches |
Testing | A/B Testing | A controlled experiment compares two product versions (version A vs. version B) to determine which performs better based on a specific metric. | Techniques | |
Process Analysis | A3 Problem Solving | A3 | A structured problem-solving methodology used in Lean and Six Sigma involves documenting the problem, analysis, and solution on a single A3-sized page. | Techniques |
Testing | Acceptance Criteria | The conditions that a software product must satisfy to be accepted by the user or customer define the success or failure of a test. | Techniques | |
Design | Accessibility | The design of products, devices, services, or environments for people with disabilities ensures that all users can access and benefit from the product. | Techniques | |
Project Management | Action Item | A task or item must be completed, usually from a meeting or project discussion. It is assigned to a specific person or team for completion. | Outputs | |
Project Management | Actual Cost | AC | The actual costs incurred for work performed on the project during a specific period. | Techniques |
Design | Adaptive Design | A design methodology that adjusts the layout and content of a website or app based on the specific characteristics of the device or screen it is being viewed on. | Techniques | |
Reporting | Ad-Hoc Report | A report is generated on demand, typically for a specific business need, rather than on a regular schedule. | Outputs | |
Organisational Change | ADKAR Model | A change management model focusing on five stages of individual change: Awareness, Desire, Knowledge, Ability, and Reinforcement. | Tools | |
Project Management | Administrative Closure | The finalisation of all administrative tasks, such as archiving project documentation, updating records, and ensuring the project is officially closed in all systems. | Processes | |
Design | Affinity Diagram | A visual tool used in design thinking and brainstorming that organises ideas, concepts, or user feedback into related groups for better understanding and synthesis. | Techniques | |
Design | Affordance | A design principle refers to an object's perceived and actual properties that determine how it can be used, helping users understand its function. | Techniques | |
Project Delivery | Agile | An iterative approach to project management and software development that emphasises flexibility, collaboration, and customer satisfaction. | Methodologies, Frameworks, and Approaches | |
Business Architecture | Agile Business Architecture | A business architecture approach incorporating agile principles and practices allows for flexible and iterative development of business capabilities and processes. | Methodologies, Frameworks, and Approaches | |
Project Delivery | Agile Manifesto | A statement of core values and principles that guide the Agile methodology for software development and project management. | Methodologies, Frameworks, and Approaches | |
Design | Alignment | The process of arranging elements on a page or screen to line up in a clear, organised way helps create a clean and visually pleasing layout. | Processes | |
Testing | Alpha Testing | Internal developers or testers typically conduct the initial testing phase before releasing the product to a limited number of users. | Techniques | |
Data Analysis | Alteryx | A data analytics platform used to clean, prepare, and analyse data and to automate complex workflows. | Tools | |
Development | Angular | A TypeScript-based open-source framework for building web applications, known for its two-way data binding and robust tooling. | Methodologies, Frameworks, and Approaches | |
Reporting | Annual Report | A comprehensive report summarises an organisation's financial performance, strategic initiatives, and overall progress over a year. | Outputs | |
IT Architecture | API Gateway Architecture | A server or middleware that acts as a single entry point for managing and routing requests to multiple APIs, often used in microservice architectures. | Architecture | |
Testing | Appium | A mobile automation testing tool that allows functional testing on iOS and Android applications using a single API. | Tools | |
IT Architecture | Application Architecture | The process of designing software applications with a focus on their structure, components, and integration with other applications or systems. | Architecture | |
IT Architecture | Application Programming Interface | API | A set of protocols, tools, and definitions that allow different software applications to communicate and interact with each other. | Tools |
Document Management | Approval | The formal process of validating and accepting a document, deliverable, or project output as meeting the specified criteria and ready for the next phase or release. | Processes | |
Project Management | Approval Gate | A decision point during project initiation or execution where key stakeholders review progress or proposals before giving the green light to proceed. | Techniques | |
Document Management | Approval Matrix | A chart or document that defines the roles and responsibilities of individuals or groups involved in approving different types of documents or deliverables within a project. | Techniques | |
Document Management | Approval Process | The formal steps and procedures through which documents or deliverables are reviewed, modified, and approved by the designated stakeholders. | Processes | |
Document Management | Approval Workflow | The sequence of steps includes the individuals or groups responsible for approving documents, deliverables, or project outputs before moving forward. | Techniques | |
Business Architecture | Archi | A modelling tool for Enterprise Architecture that supports the ArchiMate modelling language for visualising enterprise processes, applications, and technology. | Tools | |
Release and Deployment | Artifact | A by-product of the software development process, typically a compiled code file (e.g., .jar, .war, .exe) deployed to environments during release. | Outputs | |
Data Analysis | Artificial Intelligence | AI | The simulation of human intelligence in machines programmed to think and learn from data enables them to perform tasks typically requiring human cognition. | Techniques |
System Analysis | As-is Model | As-is | A model or diagram that represents the current state of a system or process before any changes or improvements are made. | Outputs |
Project Management | Asana | Asana | A project management tool used to track tasks, manage workflows, and improve team collaboration. | Tools |
Process Analysis | As-Is Process | As-Is | A term describes the current state of a process or system before any improvements or changes are made. | Techniques |
Business Analysis | Assumption | A condition or circumstance accepted as true for the purpose of planning and requirements gathering may not be validated. | Techniques | |
Project Management | Assumptions Log | A document that captures all assumptions made during the project initiation, such as availability of resources or favourable market conditions, and monitors them throughout the project. | Outputs | |
Risk Management | Audit Committee | A group of board members is responsible for overseeing an organisation's financial reporting process, audit procedures, and compliance activities. | Stakeholders | |
Reporting | Audit Report | A formal document produced by an auditor after reviewing and evaluating an organisation's financial or operational activities for accuracy and compliance. | Outputs | |
Risk Management | Audit Trail | A chronological record of events or transactions that provides evidence of an organisation's adherence to policies, regulations, and controls. | Outputs | |
Document Management | Audit Trail | A record of all actions taken on a document or deliverable, typically tracked in a version control system or document management system, to ensure accountability and traceability. | Outputs | |
IT Architecture | Automation Architecture | The design of systems and tools used to automate IT tasks, including deployment, monitoring, testing, and configuration management. | Architecture | |
Testing | Automation Testing | Using automated tools and scripts to perform testing tasks helps reduce manual effort and speed up the testing process. | Techniques | |
Service Management | Availability | The ability of a service or system to be operational and accessible when needed is measured as a percentage of uptime. | Techniques | |
Service Management | Availability Management | The process of ensuring that IT services and infrastructure are available to meet agreed-upon service levels and minimise downtime. | Processes | |
Development | Babel | A JavaScript compiler that allows developers to use the latest ECMAScript features by transpiling code to backwards-compatible versions. | Tools | |
Implementation | Backward Compatibility | The ability of a system or software to continue functioning with older versions of hardware, software, or data. | Techniques | |
Project Management | Baseline | The project plan's approved version includes scope, schedule, and costs. It serves as a reference point for measuring and monitoring project performance. | Techniques | |
System Analysis | Behavioural Modelling | The process of representing the dynamic aspects of a system, such as user interactions, process flows, and state changes, often using state diagrams or sequence diagrams. | Outputs | |
Organisational Change | Change Management Maturity Model | A framework used to assess the maturity of an organisation's change management practices, helping to identify areas for improvement and growth in managing change. | Methodologies, Frameworks, and Approaches | |
Organisational Change | Change Management Plan | A comprehensive document outlines how an organisation will implement and manage a change initiative, including communication, training, and resistance management strategies. | Outputs | |
Organisational Change | Change Metrics | Quantitative and qualitative measurements are used to assess the effectiveness of the change process, including employee adoption rates, system performance, and business outcomes. | Techniques | |
Organisational Change | Change Network | A group of individuals across the organisation who support and advocate for the change initiative. | Stakeholders | |
Organisational Change | Change Ownership | The degree to which individuals or groups within the organisation take responsibility for driving and supporting change. | Techniques | |
Organisational Change | Change Plan Template | A predefined template documents the change management strategy, including the steps, timeline, resources, and responsibilities involved in managing the change. | Outputs | |
Organisational Change | Change Readiness | The degree to which an organisation, its processes, and employees are prepared to embrace and implement change. | Techniques | |
Organisational Change | Change Reinforcement | The process of embedding new behaviours, practices, or technologies into the organisation to ensure they are sustained over time. | Processes | |
System Analysis | Change Request | CR | A formal proposal to alter any part of the system design or functionality during the system analysis and development phases. | Outputs |
Project Management | Change Request | CR | A formal proposal to modify the project plan's scope, schedule, cost, or other elements. | Techniques |
Organisational Change | Change Sustainability | The ability of an organisation to sustain the changes over time, ensuring that new behaviours, practices, and systems are maintained long after the change has been implemented. | Processes | |
Organisational Change | Change Vision | A clear and compelling description of the future state the organisation will reach after the change is complete is used to inspire and motivate employees. | Techniques | |
Document Management | Check-in/Check-out | A process where team members 'check out' a document to make changes and then 'check it in' once changes are complete, ensuring proper version control and preventing conflicts. | Techniques | |
Development | CI/CD | Continuous Integration/Continuous Delivery | A set of practices and tools that enable automated testing, integration, and code delivery, promoting faster and more reliable software development cycles. | Practices |
Development | CI/CD Pipeline | An automated workflow that facilitates continuous integration and delivery of code involves stages such as build, test, and deployment. | Processes | |
Data Analysis | Classification | A type of supervised machine learning that aims to predict the categorical label of new data based on historically labelled data. | Techniques | |
Implementation | Client Onboarding | The process of integrating a new client into a product or service system, ensuring that all initial setup, configurations, and training are completed. | Processes | |
Project Management | Closeout Report | A formal document is prepared at the end of the project to summarise the outcomes, including a review of scope, deliverables, cost, schedule, and lessons learned. | Outputs | |
IT Architecture | Cloud Architecture | The design of applications and systems hosted on cloud computing platforms involves scalability, security, and resource management considerations. | Architecture | |
Development | Cloud Computing | The delivery of computing services, such as servers, storage, databases, networking, software, and analytics, over the Internet is often used with scalable and flexible infrastructure. | Tools | |
IT Architecture | Cloud-Native Architecture | Cloud-Native | An approach to designing, building, and running applications fully leveraging cloud computing benefits, including scalability, flexibility, and resilience. | Architecture |
IT Architecture | Cloud-Native Development | The practice of designing, developing, and deploying applications specifically to run in cloud environments, often using microservices and containers. | Processes | |
Data Analysis | Clustering | A machine learning technique that groups similar data points into clusters based on similarity is often used in data mining and pattern recognition. | Techniques | |
Design | Cognitive Load | The total amount of mental effort a user uses to process information while interacting with a system. The goal is to design interfaces that minimise cognitive load. | Techniques | |
Document Management | Collaborative Editing | A process where multiple individuals can simultaneously make changes or add comments to a document, often facilitated by cloud-based document management tools. | Techniques | |
Design | Colour Theory | The study of how colours interact with each other, the psychological effects of colours, and how they can be used effectively in design. | Techniques | |
Risk Management | Committee of Sponsoring Organisations of the Treadway Commission | COSO | A private sector initiative that provides a framework for organisations to assess and improve their internal control systems. | Methodologies, Frameworks, and Approaches |
Organisational Change | Communication Plan | A plan that outlines how information about the change will be communicated to stakeholders, ensuring clear, consistent, and timely messaging. | Outputs | |
Project Management | Communication Plan | A strategy for communicating project progress, updates, and issues with stakeholders, ensuring transparency and timely information sharing. | Outputs | |
Organisational Change | Communication Strategy | A plan for communicating the change initiative's goals, reasons, and progress to different stakeholders in the organisation. | Outputs | |
Risk Management | Compliance | The act of adhering to laws, regulations, guidelines, and standards that govern an organisation's operations. | Processes | |
Risk Management | Compliance Audit | A systematic review or examination of an organisation's adherence to regulatory requirements and internal policies. | Outputs | |
Vendor and Supplier Management | Compliance Audits | A process of reviewing vendor and supplier practices to ensure adherence to contractual terms, legal regulations, and organisational policies. | Processes | |
Risk Management | Compliance Monitoring | The ongoing process of tracking and assessing an organisation's compliance with relevant regulations, policies, and standards. | Processes | |
Risk Management | Compliance Officer | A designated individual overseeing compliance within an organisation, ensuring adherence to laws, regulations, and internal policies. | Stakeholders | |
Risk Management | Compliance Program | A set of organised activities within an organisation to ensure adherence to legal, regulatory, and ethical standards and to mitigate risks. | Processes | |
Reporting | Compliance Report | A report demonstrating an organisation's adherence to regulatory, legal, or internal standards is often used for audits or assessments. | Outputs | |
Risk Management | Compliance Risk | The risk is that an organisation will fail to comply with relevant laws, regulations, or internal policies, potentially resulting in penalties or reputational damage. | Processes | |
Risk Management | Compliance Risk Management | The process of identifying, assessing, and managing compliance-related risks to ensure that the organisation adheres to all relevant laws, regulations, and standards. | Processes | |
Project Management | Compliance Verification | Ensuring that the project meets all relevant legal, regulatory, and organisational compliance requirements before it is closed. | Processes | |
System Analysis | Conceptual Design | The high-level architecture and fundamental design concepts are established in the early design phase. | Techniques | |
Service Management | Configuration Item | CI | Any component, such as hardware, software, or network components, must be managed to deliver an IT service. | Techniques |
Release and Deployment | Configuration Management | The discipline of managing and maintaining the configuration of software systems, including deployment environments, to ensure consistency and integrity across systems. | Processes | |
Service Management | Configuration Management Database | CMDB | A database containing information about configuration items (CIs) and their relationships is used to support service management processes. | Tools |
Reporting | Consolidated Report | A report that aggregates data from multiple sources or departments into one comprehensive document, often used for high-level summaries. | Outputs | |
Project Management | Constraints | Any limitations or restrictions, such as time, budget, resources, or regulatory requirements, could impact the project. | Techniques | |
Project Management | Constraints Log | A document tracks constraints that may affect the project, such as time, budget, or resource limitations. | Outputs | |
Project Management | Constructive Cost Model | COCOMO | A model is used to estimate a software project's cost, effort, and schedule based on its size and complexity. | Techniques |
IT Architecture | Containerisation Architecture | Containerisation | Using containers to package and deploy applications and their dependencies provides consistency across different environments and scalability. | Architecture |
Document Management | Content Review | A review process focused on evaluating the content of a document to ensure accuracy, relevance, and alignment with business or project requirements. | Techniques | |
Business Analysis | Context Diagram | A high-level diagram that provides an overview of a system and its interactions with external entities. | Outputs | |
Project Management | Contingency Plan | A plan is developed to address unforeseen risks or changes, ensuring that the project can continue smoothly despite unexpected events. | Outputs | |
Service Management | Continual Improvement Model | A model focusing on ongoing efforts to improve services, processes, and outcomes based on feedback, analysis, and iterative enhancements. | Methodologies, Frameworks, and Approaches | |
Project Management | Project Closeout | Closeout | In the final phase of a project, all project activities are completed, deliverables are handed over to the client or stakeholder, and lessons learned are documented. | Outputs |
Project Management | Project Closure | The process of formally completing and closing a project, including finalising deliverables, documentation, and evaluations. | Processes | |
Project Management | Project Closure Checklist | A list of tasks and activities to be completed during the project closure phase, ensuring all aspects of the project are finalised. | Outputs | |
Project Management | Project Closure Meeting | Closure Meeting | A formal meeting is held at the end of the project to review the completion of deliverables, discuss any outstanding issues, and finalise project closure. | Processes |
Project Management | Project Closure Notification | A formal notification was sent to all relevant stakeholders, informing them of the project's completion and closure. | Outputs | |
Project Management | Project Closure Report | A summary report outlining the completed activities, lessons learned, financial outcomes, and other critical data needed for final project closure. | Outputs | |
Project Management | Project Documentation Archive | The process of storing and organising all project documents and records for future access, typically in a centralised repository or document management system. | Processes | |
Project Management | Project Execution | The phase of the project lifecycle where project plans are put into action, and the work is carried out. | Methodologies, Frameworks, and Approaches | |
Project Management | Project Governance | Governance | A framework of processes, roles, responsibilities, and authority to guide the successful management and delivery of the project. | Processes |
Project Management | Project Handover | Transferring the project deliverables and responsibilities to the client or operational team. | Processes | |
Project Management | Project Initiation Document | PID | A formal document that outlines the purpose, objectives, scope, stakeholders, and overall structure of the project, marking the official start of the project. | Outputs |
Project Management | Project Kickoff | The initial meeting or event at the beginning of a project is to introduce the project team, align stakeholders, and review the project's goals and plan. | Practices | |
Project Management | Project Lifecycle | The series of phases a project goes through from initiation, planning, execution, monitoring and control to closure. | Processes | |
Project Management | Project Management Body of Knowledge | PMBOK | A set of standard guidelines and best practices for project management is recognised globally as a framework for managing projects. | Methodologies, Frameworks, and Approaches |
Project Management | Project Management Information System | PMIS | A system used for organising, tracking, and managing project data and information, such as schedules and costs. | Tools |
Project Management | Project Management Office | PMO | A department or group within an organisation is responsible for overseeing project management, ensuring consistent project governance, and aligning projects with organisational goals. | Stakeholders |
Project Management | Project Milestone | A significant event or decision point in a project that marks a key achievement or completion of a phase. | Techniques | |
Project Management | Project Objectives | Clear, measurable goals that the project aims to achieve are typically aligned with the business or organisational strategy. | Outputs | |
Project Management | Project Plan | A detailed document describing the project's objectives, scope, schedule, cost, and quality requirements is created once the project is formally initiated. | Outputs | |
Vendor and Supplier Management | Project Procurement | The process of acquiring goods, services, or contracts necessary for project execution. | Processes | |
Project Management | Project Risk | Any uncertain event or condition that, if it occurs, may have a positive or negative effect on the project's objectives. | Processes | |
Project Management | Project Schedule | A detailed timeline that outlines project activities, their durations, and the sequence of tasks to be completed. | Techniques | |
Project Management | Project Scope | A project's overall boundaries and deliverables outline what will be included and excluded. | Outputs | |
Project Management | Project Sponsor | The person or group who provides the financial resources, support, and authority for the project and ensures that the project aligns with business objectives. | Stakeholders | |
Project Management | Project Team | Team | A group of individuals with defined roles and responsibilities responsible for executing the project tasks and achieving project objectives. | Stakeholders |
Project Management | Project Timeline | A visual representation or chart that outlines the project's key milestones, deadlines, and task durations, often presented in a Gantt chart format. | Techniques | |
Project Delivery | Projects IN Controlled Environments | PRINCE2 | A process-based methodology for effective project management that focuses on organisation and control throughout the project lifecycle. | Methodologies, Frameworks, and Approaches |
Design | Prototype | An early working model of a product or system used to test and validate design concepts and user interactions before full development. | Outputs | |
Design | Prototype Testing | Testing a prototype (early design model) to evaluate usability and functionality and gather feedback for improvement. | Techniques | |
System Analysis | Prototyping | The process of creating an early, simplified version of a system to validate design ideas, gather user feedback, and refine requirements. | Processes | |
Design | Proximity | A design principle states that related items should be grouped to improve readability and organisation. | Techniques | |
Vendor and Supplier Management | Purchase Agreement | A legally binding contract between a buyer and supplier specifying the terms and conditions for the sale and delivery of goods or services. | Outputs | |
Vendor and Supplier Management | Purchase Order | PO | A formal document issued by a buyer to a vendor or supplier that outlines the details of the products or services being ordered, including prices, quantities, and delivery terms. | Outputs |
Data Analysis | Python | A programming language widely used for data analysis, statistical modelling, automation, and machine learning. | Languages | |
Data Analysis | QlikView | A business intelligence tool that provides data analysis, reporting, and visualisation features to enable decision-making and data-driven insights. | Tools | |
Project Management | Quality Assurance | QA | The proactive process of defining and ensuring quality standards and procedures are met throughout the project. | Processes |
Implementation | Quality Assurance | Ensuring that the products and processes meet certain quality standards, often through structured testing during the implementation phase. | Processes | |
Testing | Quality Control | QC | The process of inspecting and testing the actual product or service to identify defects, often after it has been developed. It focuses on verifying the correctness of the product. | Processes |
Project Management | Quality Management | Ensuring the project's outputs meet the required standards and specifications by planning, monitoring, and controlling quality. | Processes | |
Document Management | Quality Review | A review process focused on ensuring that the product or document meets the required quality standards before approval or release. | Techniques | |
Reporting | Quarterly Report | A report that summarises activities and financials over a quarter (3 months) to assess business performance and progress. | Outputs | |
Data Analysis | R Programming | R | A programming language and environment for statistical computing and data analysis, widely used for complex analytics, modelling, and visualisation. | Tools |
Project Delivery | Rapid Application Development | RAD | A software development methodology that emphasises quick prototyping and iterative development to deliver products faster. | Methodologies, Frameworks, and Approaches |
Project Delivery | Rational Unified Process | RUP | An iterative software development methodology focused on defining software requirements early and improving the quality of the product over time. | Methodologies, Frameworks, and Approaches |
Development | React | A JavaScript library for building user interfaces, particularly for creating dynamic single-page applications with reusable components. | Methodologies, Frameworks, and Approaches | |
Reporting | Real-Time Reporting | A reporting that provides instant updates, ensuring that decision-makers have the most current information available. | Outputs | |
Development | Redis | An open-source, in-memory data structure store used as a database, cache, and message broker, often employed for fast data retrieval. | Tools | |
Document Management | Redlining | The process of marking changes, edits, or revisions on a document, typically using a specific format or markup to highlight changes from previous versions. | Processes | |
Testing | Regressed Test | A test that was previously executed and passed is now re-executed to confirm that changes or new updates have not introduced new defects. | Techniques | |
Data Analysis | Regression | A statistical method used to model the relationship between a dependent variable and one or more independent variables is often used for prediction. | Techniques | |
Testing | Regression Testing | The process of testing changes or updates to software to ensure that previously working functionalities have not been negatively affected. | Processes | |
Release and Deployment | Release Candidate | A version of a software product that is potentially ready for production release, having passed internal testing, and is ready for final validation. | Outputs | |
Implementation | Release Management | Planning, designing, and deploying new or changed IT services and components into production environments. | Processes | |
Release and Deployment | Release Management | The process of planning, scheduling, and controlling the movement of releases to test and live environments, ensuring they are delivered efficiently and securely. | Processes | |
Release and Deployment | Release Train | A scheduled, repeatable approach to releasing software where features and updates are planned and delivered in time-boxed iterations. | Techniques | |
Reporting | Report Automation | Using software or tools to generate and distribute reports automatically saves time and reduces human error. | Processes | |
Reporting | Report Generation | Create reports by gathering data from various sources and presenting them in a structured, organised format. | Processes | |
Reporting | Report Template | A pre-defined format or structure for reports that can be filled in with relevant data. | Outputs | |
Vendor and Supplier Management | Request for Information | RFI | A document used to gather preliminary information from potential suppliers or vendors about their capabilities, products, or services. | Outputs |
Vendor and Supplier Management | Request for Proposal | RFP | A document issued by an organisation to solicit bids from potential vendors or suppliers for goods or services required. | Outputs |
Vendor and Supplier Management | Request for Quotation | RFQ | A process where an organisation invites suppliers to provide price quotes for specific products or services. | Outputs |
Service Management | Request Fulfillment | The process of handling user service requests typically involves access to standard services such as password resets or hardware requests. | Processes | |
Business Analysis | Requirement Change Control | The process of managing changes to requirements, ensuring that changes are evaluated, documented, and implemented systematically. | Processes | |
Business Analysis | Requirement Dependency | The relationship between two or more requirements where one requirement cannot be fulfilled until another is completed or validated. | Techniques | |
System Analysis | Requirement Elicitation | Gathering requirements from stakeholders through interviews, surveys, observations, and workshops. | Processes | |
Business Analysis | Requirement Engineering | A discipline within systems engineering that focuses on gathering, documenting, and managing requirements for a product or system. | Methodologies, Frameworks, and Approaches | |
Business Analysis | Requirement Gap | A discrepancy or missing requirement must be addressed to meet the full business need or system functionality. | Techniques | |
Business Analysis | Requirement Gathering | Identifying and documenting the requirements for a system or project, typically through interviews, surveys, workshops, or observation. | Processes | |
Business Analysis | Requirement Review | A process where relevant stakeholders review requirements documents to ensure they are clear, complete, and valid. | Techniques | |
Business Analysis | Requirement Traceability Matrix | RTM | A document that ensures that each requirement is linked to its corresponding design, development, and testing activities, ensuring no requirements are missed. | Outputs |
Business Analysis | Requirement Validation | Ensuring that requirements are correct, complete, feasible, and aligned with stakeholder needs and project goals. | Processes | |
Business Analysis | Requirement Verification | The process of ensuring that the final deliverables meet the stated requirements through testing and reviews. | Processes | |
Business Analysis | Requirements Analysis | The process of evaluating and breaking down gathered requirements to ensure they are clear, feasible, and aligned with business objectives. | Processes | |
Business Analysis | Requirements Elicitation | Elicitation | Gathering stakeholder requirements using various techniques like interviews, surveys, and workshops. | Processes |
Business Analysis | Requirements Management | The process of documenting, analysing, tracing, prioritising, and agreeing on requirements, controlling changes and communicating to relevant stakeholders. | Processes | |
Business Analysis | Requirements Specification | A formal document that outlines all the specific details, including both functional and non-functional aspects, that a product must fulfil. | Outputs | |
Business Analysis | Requirements Traceability | The process of ensuring the final solution meets all requirements and can be traced through design, implementation, and testing. | Processes | |
Business Analysis | Requirements Traceability Matrix | RTM | A tool used to ensure that requirements are met throughout the project lifecycle by linking them to project deliverables. | Outputs |
Organisational Change | Resistance Management | Identifying, addressing, and reducing resistance to change from employees or stakeholders during an organisational change initiative. | Processes | |
Organisational Change | Resistance Mapping | Identifying individuals or groups within an organisation who are likely to resist change and understanding the reasons for resistance. | Processes | |
Organisational Change | Resistance to Change | The pushback or reluctance that employees or other stakeholders show when faced with organisational changes. Resistance may come from fear, uncertainty, or lack of understanding of the change. | Processes | |
Project Management | Resource Allocation | Assigning available resources (time, personnel, budget) to project tasks based on priority, workload, and availability. | Processes | |
Project Management | Resource Levelling | A technique used in project scheduling that adjusts tasks' start and finish dates to ensure that resource usage is balanced across the project. | Techniques | |
Project Management | Resource Management | The process of planning, allocating, and managing resources (people, equipment, money) throughout the project lifecycle to ensure optimal use. | Processes | |
Project Management | Resource Plan | A document outlines the resources (human, financial, physical, or technological) needed for the project, including their availability and allocation. | Outputs | |
Project Management | Resource Release | The formal process of releasing resources, such as personnel, equipment, or materials, that were assigned to the project but are no longer needed. | Processes | |
Project Management | Resource Smoothing | A technique used to adjust the project schedule to ensure resources are allocated efficiently without extending the overall project timeline. | Techniques | |
Project Management | Resourcing | The process of allocating and scheduling human resources, equipment, and materials for project tasks. | Processes | |
Project Management | Responsible, Accountable, Consulted, Informed | RACI | A matrix is used to clarify roles and responsibilities in a project, indicating who is responsible, accountable, consulted, and informed for each task or deliverable. | Techniques |
Design | Responsive Design | A design approach that ensures an application or website automatically adjusts to fit various screen sizes and devices, such as mobile phones, tablets, and desktops. | Techniques | |
Development | RESTful API | An architectural style for designing networked applications where resources are defined and accessed via stateless operations. | Methodologies, Frameworks, and Approaches | |
Reporting | Return on Investment | ROI | A measure used to evaluate the efficiency or profitability of an investment, calculated by dividing the gain from the investment by its cost. | Techniques |
Document Management | Review | Examining a document, deliverable, or project output to ensure it meets the specified requirements and quality standards. | Processes | |
Document Management | Revision | A change or update to a document or deliverable is typically recorded and tracked through a version control system. | Techniques | |
Risk Management | Risk | An uncertain event or condition that, if it occurs, has a positive or negative effect on project objectives. | Techniques | |
Risk Management | Risk Assessment | The process of evaluating the potential risks that could affect a project or organisation, considering their likelihood and impact. | Processes | |
Project Management | Risk Closure | Reviewing, mitigating, and closing any outstanding risks or issues identified during the project, ensuring they are resolved or transferred to other departments. | Processes | |
Risk Management | Risk Control | The actions taken to manage, reduce, or eliminate identified risks in an organisation or project. | Processes | |
Risk Management | Risk Governance | The framework and processes used by an organisation to manage and oversee its risk management activities, ensuring that they align with business objectives and regulatory requirements. | Methodologies, Frameworks, and Approaches | |
Implementation | Risk Management | The process of identifying, assessing, and mitigating potential risks during the implementation of a project or system to ensure successful delivery. | Processes | |
Risk Management | Risk Management | The process of identifying, assessing, and mitigating risks that could impact an organisation's ability to achieve its objectives. | Processes | |
Risk Management | Risk Mitigation | Mitigation | Developing strategies and actions to reduce the impact or probability of identified project risks. | Processes |
Risk Management | Risk Owner | The individual or group responsible for managing a specific risk, ensuring it is monitored and mitigated as necessary. | Stakeholders | |
Project Management | Risk Register | A document used to identify, assess, and manage risks throughout the project lifecycle, tracking the status and response actions. | Outputs | |
Reporting | Risk Report | A report that assesses and outlines the risks to an organisation, project, or business, including their potential impact and mitigation strategies. | Outputs | |
Risk Management | Risk Tolerance | The level of risk an organisation is willing to accept to pursue its objectives, balancing risk against potential reward. | Processes | |
Testing | Risk-Based Testing | A testing approach where test cases are prioritised based on the risk or potential impact of failure, ensuring high-priority areas are thoroughly tested. | Techniques | |
Project Management | Risks, Assumptions, Issues, and Dependencies | RAID | A management tool for identifying and tracking key project elements: risks, assumptions, issues, and dependencies critical to project success. | Techniques |
Release and Deployment | Rollback | The process of reverting a system or application to a previous version or state, typically after a failed deployment or issue in the new version. | Processes | |
Implementation | Rollback Plan | A contingency plan specifies how to revert a system or application to its previous state in case of an unsuccessful implementation or deployment. | Outputs | |
Release and Deployment | Rollout | The process of releasing a software update or feature to end users, typically in stages, to minimise risks associated with new releases. | Processes | |
Implementation | Rollout | Deploying a new system or product to users in stages ensures the implementation process is controlled and tested before full-scale deployment. | Techniques | |
Release and Deployment | Rollout Plan | A strategic plan detailing how a software release will be introduced to users, including timing, communication, and support. | Outputs | |
Process Analysis | Root Cause | The primary, underlying factor is responsible for a particular problem or issue in a process. | Techniques | |
Service Management | Root Cause | The primary factor or issue that causes an incident or problem is often uncovered through troubleshooting and analysis. | Techniques | |
Process Analysis | Root Cause Analysis | RCA | A problem-solving technique is used to identify the underlying causes of problems or defects, often using tools like the '5 Whys' or Fishbone diagram. | Techniques |
Service Management | Root Cause Analysis | Investigating and identifying the primary cause of recurring incidents or problems to prevent future occurrences. | Processes | |
System Analysis | Root Cause Analysis | The process of identifying the underlying causes of problems or issues within a system to ensure proper resolution and prevent recurrence. | Processes | |
Development | Ruby | A dynamic, object-oriented programming language known for its simplicity and ease of use, particularly popular in web development with the Ruby on Rails framework. | Languages | |
Development | Ruby on Rails | A server-side web application framework written in Ruby, following the Model-View-Controller (MVC) architectural pattern. | Methodologies, Frameworks, and Approaches | |
Development | RubyGems | A package manager for the Ruby programming language that provides a central repository for managing libraries and tools. | Tools | |
Reporting | Sales Report | A report that tracks sales activities, figures, and performance against sales targets or forecasts. | Outputs | |
Data Analysis | Sampling | Selecting a subset (sample) of data from a larger population to conclude the whole dataset. | Processes | |
Release and Deployment | Sandbox | A testing environment that isolates code or software changes from the live production environment, allowing for experimentation and testing without affecting live systems. | Tools | |
Testing | Sanity Testing | A subset of regression testing is conducted to determine if a particular function or bug fix works correctly before proceeding with further testing. | Techniques | |
Data Analysis | SAS | A software suite for advanced analytics, business intelligence, data management, and predictive analytics. | Tools | |
Project Delivery | Scaled Agile Framework | SAFe | A framework that applies Agile principles at scale for larger enterprises, aligning team, program, and portfolio work. | Methodologies, Frameworks, and Approaches |
Project Management | Schedule Compression | Reducing the overall project duration through techniques such as fast-tracking or crashing. | Processes | |
Project Management | Schedule Control | Monitoring and controlling project timelines ensures the project stays on track and is completed on time. | Processes | |
Project Management | Schedule Performance Index | SPI | Schedule efficiency is calculated by dividing earned value by planned value. | Techniques |
Project Management | Schedule Variance | SV | The difference between earned and planned value shows whether the project is ahead or behind schedule. | Techniques |
Project Management | Scope | The sum of all deliverables and objectives to be achieved during a project, including boundaries and exclusions. | Techniques | |
Project Management | Scope Creep | The uncontrolled or unapproved expansion of a project's scope often leads to delays, cost overruns, and project failure. | Processes | |
Business Analysis | Scope Definition | The process of defining and documenting the boundaries of a project, specifying what is included and excluded in terms of deliverables, tasks, and activities. | Processes | |
Project Management | Scope Statement | A document that clearly defines the scope of the project, including deliverables, boundaries, and constraints, setting expectations for what will and will not be included. | Outputs | |
Project Delivery | Scrum | An Agile framework is used for managing and completing complex projects by breaking them into small, manageable sprint tasks. | Methodologies, Frameworks, and Approaches | |
Project Delivery | Scrumban | A hybrid project management methodology that combines elements of Scrum and Kanban to provide flexibility and efficiency in project delivery. | Methodologies, Frameworks, and Approaches | |
IT Architecture | Security Architecture | The process of designing secure systems and networks, including identifying security risks, controls, and compliance requirements for an organisation's IT environment. | Architecture | |
Testing | Selenium | A testing tool for automating web browsers, used for functional testing, regression testing, and automating web application testing. | Tools | |
Service Management | Self-Service Portal | A web-based interface that allows users to request services, report incidents, or access knowledge articles without direct interaction with the service desk staff. | Tools | |
Development | Serverless | A cloud-computing model where cloud providers manage server infrastructure, allowing developers to focus on building and deploying code without managing the underlying hardware. | Tools | |
IT Architecture | Serverless Computing Architecture | Serverless Computing | A cloud computing model where the cloud provider automatically manages the infrastructure, allowing developers to focus on writing code rather than managing servers. | Architecture |
Business Architecture | Service Blueprint | A visual representation of the service delivery process, showing the customer journey, employee actions, and underlying support systems. | Outputs | |
Service Management | Service Catalogue | A detailed list of IT services a service provider offers, including descriptions, pricing, and availability information. | Outputs | |
Service Management | Service Delivery | The execution of services by a vendor or supplier as defined in the contract or SLA, focusing on ensuring quality, timeliness, and customer satisfaction. | Methodologies, Frameworks, and Approaches | |
Business Architecture | Service Delivery Model | A framework for how services are provided to customers, including the processes, people, and technology involved. | Methodologies, Frameworks, and Approaches | |
Service Management | Service Desk | A single point of contact between users and IT support teams is designed to manage incidents and service requests and provide support. | Stakeholders | |
Service Management | Service Level Agreement | SLA | A contract or agreement that defines the level of service expected from a service provider, detailing response times, uptime, and support levels after implementation. | Outputs |
Service Management | Service Level Agreement Monitoring | SLA Monitoring | Tracking and measuring the vendor's performance against the terms outlined in the Service Level Agreement. | Processes |
Service Management | Service Level Management | SLM | Defining, managing, and monitoring the quality of IT services to meet business needs and agreed-upon service levels. | Processes |
Service Management | Service Level Objective | SLO | A specific, measurable target within an SLA that outlines the level of service performance expected for a particular service. | Techniques |
Service Management | Service Management | The overall process of planning, delivering, managing, and improving how IT services are used within an organisation. | Processes | |
Service Management | Service Operation | The phase in the service lifecycle focused on delivering services efficiently and effectively to meet customer needs daily. | Processes | |
Service Management | Service Owner | An individual is responsible for a particular IT service's overall quality and management, ensuring it meets business requirements. | Stakeholders | |
Service Management | Service Provider | An organisation or third-party entity that provides and manages IT services for an enterprise or customer. | Stakeholders | |
Service Management | Service Reporting | The process of capturing, analysing, and presenting data related to the performance of IT services, often through dashboards or reports. | Processes | |
Service Management | Service Transition | The phase in the service lifecycle is responsible for managing the transition of a new or changed service into the live environment. | Processes | |
IT Architecture | Service-Oriented Architecture | SOA | An architectural pattern that structures IT systems into loosely coupled services that can be reused and combined to meet business requirements. | Architecture |
Document Management | Sign-off | Formal, final approval of a document or deliverable, indicating it meets requirements and can be closed or moved to the next phase. | Techniques | |
Process Analysis | Simulation | A technique used to model and analyse the behaviour of a system or process under different conditions using computer models. | Techniques | |
Process Analysis | SIPOC Diagram | SIPOC | A high-level process mapping tool is used to visualise Suppliers, Inputs, Processes, Outputs, and Customers in a process. | Techniques |
Project Delivery | Six Sigma | A data-driven methodology focused on eliminating defects and improving processes by identifying and removing the causes of variation. | Methodologies, Frameworks, and Approaches | |
Design | Sketching | The process of quickly drawing design ideas and concepts to explore possibilities and communicate early-stage design concepts. | Processes | |
Service Management | SLA Monitoring | Monitoring the performance and quality of IT services to ensure that agreed-upon SLAs are met. | Processes | |
Testing | Smoke Testing | A preliminary level of testing is performed to check if the basic functionalities of an application work as expected before more extensive testing is carried out. | Techniques | |
Development | SOAP | Simple Object Access Protocol | A protocol for exchanging structured information in the implementation of web services, typically using XML for message formatting. | Methodologies, Frameworks, and Approaches |
IT Architecture | Software as a Service | SaaS | A cloud-based software delivery model where applications are hosted by a third-party provider and accessed over the internet on a subscription basis. | Technologies |
Business Analysis | Software Requirements Specification | SRS | A detailed description of the software's functionality, including functional and non-functional requirements. | Outputs |
Testing | Software Testing Life Cycle | STLC | A series of steps followed during the software testing process to ensure the software's quality. This includes planning, design, execution, and closure of testing activities. | Processes |
IT Architecture | Software-Defined Networking | An IT architecture that separates network control from physical hardware, allowing network administrators to manage traffic and resources through software-based controllers. | Architecture | |
Development | SonarQube | A tool used for static code analysis, measuring code quality, and detecting bugs, vulnerabilities, and code smells. | Tools | |
Vendor and Supplier Management | Sourcing | Identifying and selecting suppliers or vendors for required goods or services is often part of a procurement strategy. | Processes | |
Process Analysis | Spaghetti Diagram | A process mapping tool that visually represents the flow of materials or information through a system, often revealing inefficiencies and waste. | Techniques | |
Organisational Change | Sponsorship | The active support and endorsement from senior leaders or managers for a change initiative provide authority and resources for successful implementation. | Techniques | |
Development | Spring Framework | A comprehensive programming and configuration model for Java-based enterprise applications, offering support for dependency injection, aspect-oriented programming, and more. | Methodologies, Frameworks, and Approaches | |
Project Delivery | Sprint | A short, time-boxed iteration in Agile methodologies, especially Scrum, where a specific set of deliverables is completed. | Techniques | |
Project Management | Sprint Backlog | A list of tasks or user stories that the Scrum team aims to complete in a particular sprint derived from the product backlog. | Outputs | |
Project Management | Sprint Review | A meeting is held at the end of each sprint in agile projects where the team demonstrates the work completed during the sprint and gathers feedback. | Techniques | |
Data Analysis | SPSS | A statistical software package used for data analysis, statistical modelling, and hypothesis testing. | Tools | |
Development | SQL | Structured Query Language | A standard language used for querying and managing relational databases, supporting data definition, manipulation, and control. | Tools |
Release and Deployment | Staging Deployment | Deploying software in an environment that closely mirrors production is used for final testing and quality assurance before a live release. | Processes | |
Release and Deployment | Staging Environment | An environment that mimics the production environment is used to test the final version of the software before it is deployed to production. | Tools | |
Project Management | Stakeholder | Any individual, group, or organisation that can affect or perceive themselves to be affected by a project or initiative. | Stakeholders | |
Organisational Change | Stakeholder Analysis | The process of identifying, analysing, and understanding the interests and influences of key stakeholders within the organisation. | Processes | |
System Analysis | Stakeholder Analysis | Identifying, analysing, and prioritising individuals, groups, or organisations affected by or are interested in the system or project. | Processes | |
Organisational Change | Stakeholder Analysis | Identifying and evaluating stakeholders' interests, influence, and needs to ensure their involvement and commitment during a change process. | Processes | |
Project Management | Stakeholder Analysis | Identifying, assessing, and managing stakeholders' expectations, needs, and influence throughout the project lifecycle. | Processes | |
Business Analysis | Stakeholder Analysis | The process of identifying the key stakeholders in a project, understanding their needs and expectations, and ensuring their requirements are captured. | Processes | |
Project Management | Stakeholder Communication | The process of informing stakeholders about the project's closure, including the final status, lessons learned, and any remaining actions. | Processes | |
Organisational Change | Stakeholder Engagement | The process of involving and gaining support from all relevant stakeholders to ensure the success of a change initiative. | Techniques | |
Project Management | Stakeholder Management | The process of identifying, analysing, and engaging stakeholders to ensure their needs and expectations are met. | Processes | |
Organisational Change | Stakeholder Mapping | The process of categorising stakeholders based on their influence, interest, and impact on the project or initiative. | Processes | |
Organisational Change | Stakeholder Register | A document that identifies all the stakeholders involved in the project, detailing their interests, impact, and level of influence on the project. | Outputs | |
Project Management | Stakeholder Report | A communication tool used to inform stakeholders about the project's progress, challenges, and upcoming milestones. | Outputs | |
Business Analysis | Stakeholder Requirements | Requirements that come from the stakeholders or end-users of the system, outlining their needs, desires, and expectations for the product. | Outputs | |
Document Management | Stakeholder Review | A review process in which key stakeholders or subject matter experts provide feedback on documents or deliverables to ensure they meet expectations. | Techniques | |
Reporting | Standard Report | A regularly scheduled report that follows a predetermined format, often based on key metrics and KPIs. | Outputs | |
Project Management | Statement of Work | SOW | A formal document that defines the scope, objectives, deliverables, and timeline for a project or contract. | Outputs |
Testing | Static Testing | A type of testing that involves examining the software's code, documentation, and other artifacts without executing the program, often performed through code reviews or inspections. | Techniques | |
Project Management | Status Meeting | A recurring meeting where the project manager and team discuss the project's current status, issues, risks, and progress. | Processes | |
Project Management | Status Report | A report that updates the project's progress, including key performance indicators, risks, issues, and actions taken. | Outputs | |
Design | Storyboard | A visual representation of how a user will interact with a system is often used to map out the flow of a process or a series of events in a product. | Techniques | |
Business Architecture | Strategic Alignment | Ensuring that business capabilities, operations, and projects are aligned with the strategic goals and vision of the organisation. | Processes | |
Testing | Stress Testing | A type of testing that evaluates how a system behaves under extreme conditions or high loads to determine its breaking point. | Techniques | |
Data Analysis | Structured Query Language | SQL | A standardised programming language used to manage and manipulate relational databases, enabling users to query, update, and manage data. | Languages |
Project Management | Success Criteria | The specific criteria or conditions will determine whether the project has met its objectives and is successful. | Techniques | |
Project Management | Success Criteria Validation | Confirming that the project has met the agreed-upon success criteria, typically through a formal review or assessment at closure. | Processes | |
Reporting | Summary Report | A concise report that summarises key findings, results, or insights from a more detailed or lengthy document. | Outputs | |
Vendor and Supplier Management | Supplier Collaboration | Working closely with suppliers to improve mutual processes, share information, and enhance the overall supply chain performance. | Techniques | |
Vendor and Supplier Management | Supplier Diversity | The practice of sourcing from diverse suppliers, particularly those owned by minorities, women, veterans, or other underrepresented groups. | Techniques | |
Vendor and Supplier Management | Supplier Evaluation | The process of assessing and reviewing potential suppliers or existing vendors to determine their ability to meet the organisation's quality, performance, and cost requirements. | Processes | |
Vendor and Supplier Management | Supplier Relationship Management | SRM | A strategic approach to managing interactions with key suppliers to maximise the value of those relationships, ensuring long-term success and mutually beneficial outcomes. | Methodologies, Frameworks, and Approaches |
Vendor and Supplier Management | Supplier Risk Management | Identifying, assessing, and mitigating risks related to the performance and reliability of suppliers and vendors. | Processes | |
Process Analysis | Supplier, Input, Process, Output, Customer | SIPOC | A high-level process mapping tool is used to identify key elements of a process, including suppliers, inputs, outputs, and customers. | Techniques |
Vendor and Supplier Management | Supply Chain Management | Managing the flow of goods and services, from raw materials to the final product delivered to the customer, includes vendor and supplier relationships. | Processes | |
Implementation | Support Model | The framework or system for providing ongoing support to end-users after implementation, including helpdesk services, troubleshooting, and maintenance. | Methodologies, Frameworks, and Approaches | |
Development | Swift | A powerful and intuitive programming language for iOS, macOS, watchOS, and tvOS app development, developed by Apple. | Languages | |
Project Management | SWOT Analysis | SWOT | A strategic planning tool is used to identify strengths, weaknesses, opportunities, and threats related to a business or project. | Techniques |
System Analysis | System Architecture | The high-level structure of a system, describing its components, their relationships, and the technologies used. | Architecture | |
Implementation | System Configuration | Adjusting system settings, parameters, and options ensures that a software application or hardware system is set up according to requirements. | Processes | |
System Analysis | System Decomposition | The process of breaking down a complex system into smaller, manageable components or subsystems for analysis and design. | Processes | |
Implementation | System Deployment | Installing, configuring, and enabling a system to go live and become functional for end users. | Processes | |
Design | User Journey | A map or flowchart depicts a user's interactions and experiences when engaging with a product or service. | Techniques | |
Design | User Persona | Based on data and research, a semi-fictional representation of the target user is used to guide design decisions. | Techniques | |
Business Analysis | User Story | A brief, informal description of one or more features or functionalities that a user needs from the system, often used in Agile methodologies. | Techniques | |
Business Architecture | Value Proposition | A statement or description of a business's unique value to its customers, addressing their needs and pain points. | Outputs | |
Process Analysis | Value Stream | An organisation performs a series of steps or activities to deliver a product or service to customers, focusing on maximising value and minimising waste. | Techniques | |
Process Analysis | Value Stream Mapping | VSM | A lean-management tool used to analyse and design the flow of materials and information required to bring a product or service to a customer. | Techniques |
Process Analysis | Value Stream Mapping | A method for analysing and visualising the flow of information and materials needed to bring a product or service to a customer, often used in implementing process improvements. | Techniques | |
Data Analysis | Variable | An attribute, feature, or characteristic of a dataset that can be measured and varied is often used as an independent or dependent variable in statistical models. | Techniques | |
Project Management | Variance Analysis | The process of comparing actual project performance against the planned performance, identifying discrepancies, and taking corrective actions. | Processes | |
Project Management | Variance at Completion | VAC | The difference between the original budget (BAC) and the estimated cost at completion (EAC) indicates whether the project is expected to be under or over budget. | Techniques |
Reporting | Variance Report | A report used to compare actual performance against budgeted or expected performance, highlighting differences or variances. | Outputs | |
Service Management | Vendor Audit | A detailed review of a supplier's or vendor's financial records, processes, and practices to ensure they comply with agreed-upon terms and industry standards. | Processes | |
Service Management | Vendor Compliance | Ensuring that vendors meet all regulatory, legal, and contractual obligations, including ethical standards and environmental requirements. | Processes | |
Service Management | Vendor Consolidation | The practice of reducing the number of suppliers or vendors to streamline operations, reduce complexity, and negotiate better terms. | Techniques | |
Service Management | Vendor Management | Selecting, managing, and maintaining relationships with third-party vendors and suppliers to ensure they meet business needs and performance expectations. | Processes | |
Service Management | Vendor Negotiation | Discussing and agreeing on terms and conditions with a supplier or vendor, often to secure favourable pricing, terms, and delivery schedules. | Processes | |
Service Management | Vendor Onboarding | The process of integrating a new vendor or supplier into the organisation's supply chain, ensuring compliance with company standards and policies. | Processes | |
Service Management | Vendor Performance Management | The process of monitoring and evaluating the performance of vendors and suppliers based on agreed-upon metrics such as quality, timeliness, and service levels. | Processes | |
Risk Management | Vendor Risk | The potential risks arise from third-party vendors, including non-compliance, financial instability, or failure to meet contractual obligations. | Processes | |
Vendor and Supplier Management | Vendor Tiering | The practice of categorising vendors into different levels or tiers based on their importance, volume of business, and strategic value. | Techniques | |
Business Analysis | Verification Matrix | A matrix tracks how each requirement is validated during testing, verifying all requirements against the final product. | Outputs | |
Release and Deployment | Version Control | A system that records changes to a file or set of files over time allows multiple software versions to be managed and tracked. | Techniques | |
Document Management | Version Control System | VCS | A tool used to track changes to documents or code, enabling teams to manage revisions and keep a history of document versions. | Techniques |
Document Management | Version History | A record of all versions of a document, including changes made and who made them, is used to track the document's evolution over time. | Techniques | |
Document Management | Versioning | The practice of assigning unique version identifiers to different iterations of a document or deliverable, typically to manage updates and track progress over time. | Techniques | |
IT Architecture | Virtualisation Architecture | Virtualisation | The design and use of virtual resources (e.g., virtual machines, virtual networks, virtual storage) to maximise efficiency, scalability, and cost savings in IT environments. | Architecture |
Design | Visual Design | The process of designing the aesthetics of the user interface, including layout, colour schemes, typography, and imagery, to create an appealing and functional UI. | Processes | |
Design | Visual Hierarchy | The arrangement of elements in a design indicates their importance, guiding the viewer's eye to focus on key information first. | Techniques | |
Testing | V-Model | A software development methodology that emphasises validation and verification in a V-shaped process, where each phase corresponds to a testing phase. | Methodologies, Frameworks, and Approaches | |
Development | Vue.js | A progressive JavaScript framework used for building user interfaces and single-page applications, focusing on simplicity and flexibility. | Methodologies, Frameworks, and Approaches | |
Document Management | Walkthrough | A detailed step-by-step review of a document, design, or deliverable, where team members discuss each aspect to identify errors or gaps. | Techniques | |
Project Management | Warranty Period | A defined period after project completion during which the contractor or service provider is responsible for fixing any defects or issues with the deliverables. | Processes | |
Project Delivery | Waterfall | A traditional project management methodology where each project phase (requirements, design, implementation) flows sequentially. | Methodologies, Frameworks, and Approaches | |
Development | Webpack | A static module bundler for JavaScript applications, enabling bundling of assets, optimisation, and management of dependencies. | Tools | |
Testing | White Box Testing | A testing technique involves testing a software application's internal workings, such as code structure, algorithms, and data flow. | Techniques | |
Design | Wireframe | A basic, low-fidelity visual representation of a webpage or application layout is often used to plan and structure the user interface (UI) design. | Outputs | |
Project Management | Work Breakdown Structure | WBS | A hierarchical decomposition of a project into smaller, manageable tasks or components to facilitate project management. | Techniques |
Project Management | Work In Progress | WIP | The total work or tasks currently being worked on in a given project or system. | Techniques |
Project Management | Work Package | A group of related tasks or activities that are managed together to form a deliverable or component of a project. | Outputs | |
Development | XML | Extensible Markup Language | A markup language is used to store and transport data in a machine-readable format, focusing on simplicity and extensibility. | Data Formats |
Development | YAML | YAML Ain't Markup Language | A human-readable data serialisation format is used to configure files and exchange between languages with different data structures. | Languages |
IT Architecture | Zachman Framework | A schema for organising and classifying the different aspects of an enterprise architecture, including its people, processes, data, and technology. | Methodologies, Frameworks, and Approaches | |
Testing | Zephyr | A test management tool for planning, tracking, and managing tests across different testing teams. | Tools | |
Release and Deployment | Zero-Downtime Deployment | A deployment strategy that ensures updates or changes are applied to production without causing any downtime or service interruption for end users. | Techniques |
Page ${currentPage} of ${totalPages}