Project Management and the Project Context
What makes a project a project
A project is a temporary endeavour, undertaken to deliver one or more defined outputs in line with an agreed business case, within a finite timeframe and with finite resources. Three tests distinguish it from business as usual: it is temporary (it ends, and the team disbands), unique (no two are identical), and business-case driven (it exists to deliver defined benefits). Project management is the application of methods, tools and competence to deliver those objectives.
Keep three terms apart, because questions trade on the confusion. Outputs are what the project produces (a system, a building). Outcomes are the resulting change in the organisation (staff now process claims digitally). Benefits are the measurable value realised from that change (cost per claim down 30%), and they usually accrue after the project closes.
Context and environment
Analyse context both internally (structure, culture, maturity, governance, resource availability) and externally using PESTLE: Political, Economic, Social, Technological, Legal, Environmental. Understand the hierarchy: a portfolio is the whole prioritised collection of projects and programmes; a programme is a group of related projects managed together to deliver outcomes and benefits that could not be achieved individually.
Traps
Confusing programme with portfolio; describing benefits as outputs; assuming benefits are realised during the project; treating the business case as a one-off document rather than one reviewed at every gate.
Rule of thumb
If the work cannot be described as temporary, unique and business-case driven, it is business as usual - and should be moved out of project scope.