Structured requirements elicitation and traceability (aligned with SOP 6.09):

• Define and maintain structured and updated requirements documentation through the Programme of Work (PoW);
• Establish bidirectional traceability chains from project-level requirements up to capability and enterprise requirements;
• Identify, elicit, and catalogue formal requirements (CRs, MMRs, IERs) aligned to capability planning;
• Document stakeholder needs using structured templates and validation sessions;
• Maintain a traceability matrix linking CRs, MMRs, IERs, CONOPS, and CPP objectives to strategic outcomes;
• Aim to increase overall quality of the requirements artefacts across levels of detail and abstraction;
• Support requirements change control in accordance with PoW governance.

Support CONOPS, CONUSE, CONEMPS, and IERs documentation:

• Conduct interviews and workshops to define operational contexts and usage scenarios;
• Draft high-level artefacts (CONOPS, CONUSE, CONEMPS) aligned to programme intent;
• Capture operational, system specific, and technical IERs from stakeholders and technical leads;
• Develop portfolio standardized diagrams, workflows, and usage models to complement documentation.

Workshop facilitation and support to work package leads:

• Collaborate with WP leads to plan, run, capture, and follow up on workshops;
• Help structure the collection of requirements by theme, dependency and priority;
• Convert workshop outputs into structured requirements and work products.

Requirements packaging for transition to delivery:

• Consolidate validated requirements and concept artefacts into agency accepted formats (e.g. DOORS, SOP 6.09) ready for transition to projects;
• Ensure supporting documentation, diagrams, use cases, and assumptions are captured;
• Assist WP leads in developing documentation required for project initiation;
• Package solution information so it is clear, concise, and consumable for decision;
• Makers and delivery teams. Impact analysis, dependencies and readiness support;
• Support the assessment of feasibility, dependencies, and organizational readiness for proposed requirements;
• Document internal and external dependencies as part of traceability and roadmap planning;
• Support the identification of areas requiring new project formation or prioritization within the PoW;
• Record and trace key dependencies and impacts in the requirements and traceability set.

Project proposal development support under the PoW:

• Collaborate with stakeholders to identify and shape candidate project proposals;
• Draft and deliver project proposal documentation packages including requirements extracts, traceability, dependencies, and readiness assessments;
• Support proposal review cycles, capture lessons learned, and recommend improvements to future project proposal processes.

CPP development support:

• Consolidate requirements and traceability matrices into CPP input products;
• Produce requirement alignment tables, dependency views, and prioritization options for submission to the Capability Programme Plan cycle;
• Facilitate workshops and reviews to validate CPP deliverables with stakeholders.

Reporting and coordination support:

• Provide regular updates and progress reports to the NC3 Portfolio and Programme Leads;
• Maintain a single source of truth for requirements, and documentation via NCIA platforms;
• Participate in weekly, monthly, and checkpoint meetings to ensure alignment with portfolio governance.