| | Iron triangle in software development: scope, time and cost |
| |
| | Scope: features, functionality |
| |
| | Time: schedule |
| |
| | Cost: resources, budget |
| |
| | Estimates: by team members |
| |
| | Deadline: by the management team |
| |
| | Agile: iterative and incremental development |
| |
| | Iterations and Increments: periodic evaluation of new deliverables |
| |
| | Risk management: the identification, assessment, and prioritization of risks followed by coordinated and economical application of resources to
minimize, monitor, and control the probability and/or impact of unfortunate events or to maximize the realization of opportunities |
| |
| | Risk Management Golden Rules: process, identification, communication, opportunities, ownership, prioritization, analysis, response
preparation, registry, task tracking |
| |
| | Work breakdown structure (WBS): deliverable-oriented decomposition of a project into smaller components |
| |
| | Rolling wave planning: progressive elaboration to add detail to the Work Breakdown Structure (WBS) on an ongoing basis |
| |
| | Burn down chart: graphical representation of work left to do versus time |
| |
| | Dynamic systems development method (DSDM): generic approach to project management and solution delivery |
| |
| | PRojects IN Controlled Environments 2 (PRINCE2): a structured project management method endorsed by the UK government as the project management standard for public projects. |
| |
| | Scrum: an iterative and incremental agile software development method for managing software projects and product or application development |
| |
| | Customer wants too much: show them alternative outcomes and ask for their help with prioritization |
| |
