Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
Life cycles
APM PMQ Competence one terminology
| Term | Definition |
|---|---|
| Business-as-usual | An organisation's normal day-to-day operations. |
| Adoption | The optional additional phase in a linear life cycle that facilitates the use of project outputs to enable the acceptance and use of benefits. |
| Benefit | A positive and measurable impact of change (or) The quantifiable and measurable improvements resulting from the completion of deliverables that are accepted, utilised and perceived as positive by a stakeholder. |
| Benefits realisation | The practice of ensuring that benefits are derived from outputs and outcomes. |
| Business Case | A document providing justification for undertaking a project, programme or portfolio. It evaluates the benefit, cost and risk of alternative options and provides a rationale for the preferred solution. |
| Business-as-usual (BAU) | An organisation's normal day-to-day operations. |
| BAU (Business-as-usual) | An organisation's normal day-to-day operations. |
| Concept | Development of an initial idea through initial studies and high-level requirements management, and assessment of viability including an outline business case. |
| Definition | Development of a detailed definition, plans and statement of requirements that include a full justification for the work. |
| Deploy | The physical act of putting what has been assembled (the release) into operational use. |
| Deployment (iterative life cycle) | Brings a baseline of evolving solution into operational use. This may be the final solution or a subset of the final solution. After last release, the project is formally closed. |
| Deployment (linear life cycle) | Implementation of plans and verification of performance through testing and assurance to realise intended outputs, outcomes and benefits. |
| Evolutionary Development (timeboxed) | An approach that converges, by successive iterations, on an accurate solution that meets business need and technically is built the right way. |
| Extended project life cycle | Adds an adoption phase to a life cycle to ensure the accountability stays with the change teams until change is embedded, providing a connection to benefits realisation and cooperation and knowledge sharing between change and BAU. |
| Feasibility | Establishing whether a proposed project is likely to be feasible, both from a business and technical perspective, and would be cost-effective from a business perspective. |
| Foundations | Development of: agreed realistic Business Case, prioritised requirements list, solution architecture definition, development approach definition, delivery plan, management approach definition and Foundations summary. |
| Hybrid life cycle | A hybrid life cycle is a pragmatic approach to achieving beneficial change that combines a linear life cycle for some phases or activities with an iterative life cycle for others. |
| Iterative life cycle | A life cycle that repeats one or more phases of a project or programme before proceeding to the next one with the objective of managing uncertainty of scope by allowing objectives to evolve as learning and discovery take place. |
| Life cycle | A framework comprising a set of distinct high-level stages required to transform an idea or concept into reality in an orderly and efficient manner. Life cycles offer a way to undertake project-based work and are the structure underpinning deployment. |
| Linear life cycle | A life cycle that aims to complete a project within a single pass through a set of distinct phases that are completed serially and span from the development of the initial concept to the deployment of an ultimate output, outcome or benefits. |
| Post-project | (DSDM) A phase following the final Deployment to assess the realisation of expected business benefits. |
| Pre-project | (DSDM) Activity prior to project execution involved in the identification, selection and set up of projects which have a clearly defined objective. |
| Project | A unique, transient endeavour undertaken to bring about change and to achieve planned objectives. |
| Project context | The environment within which a project is undertaken. Projects do not exist in a vacuum and an appreciation of the context within which the project is being performed will assist those involved in project management to deliver a project. |
| Project management | The application of processes, methods, knowledge, skills and experience to achieve the project objectives. |
| Requirements | The stakeholders’ wants and needs clearly defined with acceptance criteria. |
| Story point | A method of estimating the completion / forecasting work yet to complete on a user story when using an iterative life cycle. |
| Time boxing | The practice of organising development work into fixed periods of time with determined resources, during which scope is completed to quality as efficiently as possible. 'Timeboxes' are also known as 'sprints'. |
| Timebox | A generic term used in iterative life cycle approaches to refer to an iteration with a fixed end date that is not allowed to change, thereby adjusting the scope and quality to deliver on time and to cost. |
| Transition | Handover, commissioning and acceptance of outputs to the sponsor and wider users, culminating in formal closure. |
| User story | An informal, simple language description of one or more features of a system or tool. User stories are often written from the perspective of an end user or user of a system. |
| Review (iterative) | A final review of the solution before it goes into operational use. |
| Gate | A point in the life cycle between phases that is used to review and confirm viability of the work in line with the business case. Also called decision gate or stage gate. |
Created by:
CITI
Popular Management sets