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
APM PFQ 7 S2
Glossary for APM Project Fundamentals Qualification
| Term | Definition |
|---|---|
| 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 systematic and organised way to undertake project-based work and can be viewed as 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 |
| 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 |
| Extended life cycle | An extended life cycle adds an adoption phase to a linear or iterative life cycle with the purpose of ensuring the accountability and governance of the investment stays with the change teams until change is fully embedded. It provides the missing connection to benefits realisation in a linear life cycle and facilitates cooperation and knowledge sharing between change and business-as-usual teams |
| 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 |
| 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 |
| Story point | A method of estimating the completion / forecasting work yet to complete on a user story when using an iterative life cycle |
| 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 |
| Minimum viable product | A product with just enough features to satisfy early users, and to provide feedback for future product development |
| 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. |
| Deployment | Implementation of plans and verification of performance through testing and assurance to realise intended outputs, outcomes and benefits |
| Transition | Handover, commissioning and acceptance of outputs to the sponsor and wider users, culminating in formal closure. |
| 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 |
| 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 |
| Deployment | 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 |
Created by:
Sarah Ironmonger
Popular Management sets