Identify project requirements and objectives
How identify project requirements and objectives are reshaped as AGI capability advances.
The bottom line
Roughly 85% of the work in Identify project requirements and objectives is information-shaped — already within reach of AI delivery. The question here is not whether it shifts, but which tasks go first and who staffs the residual.
Why: With no child occupations seeded, this scalar is derived from the PCF category prior 'Manage portfolio, program, and project' and the process description. Defining project objectives, specifying capabilities, and producing formal documentation are pure knowledge-work and information-transformation tasks, placing this firmly in the digital band.
grounded in the economy graph · digital scalar 0.85 · digital
Related articles
No articles yet for this entity.
Recent capability events
No capability events for this entity yet.
How the work flows
Trigger: A project charter or initial mandate is approved and handed over for detailed planning.
- Gather expectations from key stakeholders
- Define project objectives and success criteria
- Elicit functional and non-functional requirements
- Analyze and prioritize the identified requirements
- Draft formal requirements documentation
- Validate requirements with stakeholders
- Obtain formal sign-off on the requirements baseline
Outcome: A formal requirements document detailing the project's objectives, capabilities, and features is approved by stakeholders.