Job Specifications
NOTE: NATO requires a NON-DISCLOSURE UNDERTAKING for this position. The NDU template is available upon request.
Deadline Date: Thursday 24 April 2025
Requirement: Cloud Service Broker (CSB) Technical Writer Services
Location: Brussels, BE
Full Time On-Site: Yes
Time On-Site: 100%
Period of Performance: 2025 BASE: As soon as possible but not later than 2 JUN 2025 until 31 DEC 2025 with the possibility to exercise following options:
2026 option: from 01 JAN 2026 to 31 DEC 26
2027 option: from 01 JAN 2027 to 31 DEC 27
2028 option: from 01 JAN 2028 to 31 DEC 28
Required Security Clearance: NATO Secret - but exceptionally work can start while clearance is in progress
1 INTRODUCTION
To address the complex nature of cloud transformation, the NATO Enterprise Cloud Operating Model (NECOM) has been designed to facilitate and harmonize a common approach towards leveraging cloud services across the NATO Enterprise, ensuring the effectiveness, security, compliance, and interoperability of all its different cloud environments while maintaining coherence and synchronization with extant capability planning processes. Key elements of NECOM include the Cloud Strategy Group (CSG) and the Cloud Service Broker (CSB) functions.
The CSB function is composed of a multi-disciplinary team with expertise extending across the domains necessary to efficiently build and operate cloud services, such as technology, project management, financial management, acquisition and legal. NCIA is responsible for implementing the CSB.
To support a the successful implementation of the Cloud Service Broker (CSB), the NCIA Chief Technology Office - Cloud Centre of Excellence (CTO-CCoE) seeks support provided by a skilled technical writer to manage and produce the key documentation and governance artefacts necessary for CSB implementation. This includes collaboration with strategic leads to ensure accuracy, consistency, and alignment of documentation with NATO objectives.
2 OBJECTIVES
Provide consultancy services for creating and maintaining the CSB governance framework, ensuring clarity, traceability, and effective stakeholder communication. This role focuses on capturing requirements, developing deliverables, and ensuring clarity and consistency in documentation.
3 SCOPE OF WORK
Under the direction / guidance of the NCIA Point of Contact or delegated staff, the contractor shall provide services as per below:
Support the creation of Request for Proposals (RFPs) to engage industry in cloud implementation
Collaborate with subject matter experts (SMEs), project managers, and business development teams to gather relevant technical and business information
Create the CSB operating model, including all required documentation such as Terms of Reference (ToR), RACI matrix, Standing Agenda, and other governance artefacts
Capture and document requirements from key strategic stakeholders to develop accurate and comprehensive deliverables
Support the resolution of challenges related to ToR and RACI alignment by providing clear and actionable documentation
Collaborate with the CSB Strategy and Alignment Lead to ensure artefacts align with the overarching strategy
Assist in the development of strategy outputs and long-term planning documents
Support the ramp-up of the Cloud Portfolio (a programmatic organisational element of NCIA) by documenting project resource demands and architectural/design alignment requirements
The contractor will be part of a team and will provide services using an Agile and iterative approach during multiple sprints. Each sprint is planned for a duration of 1 week. The content and scope of each sprint will be agreed during the sprint-planning meeting, in writing, based on the activities mentioned above.
Due to the AGILE approach of this project, there is a need to define a set of specific arrangements between the NCI Agency and the contractor that specifically defines the deliverables to be provided for each sprint as well as their associated acceptance criteria. This includes sprint planning, execution and review processes, which are detailed below:
3.1. Sprint Planning:
Objective: Plan the objectives for the upcoming sprint
Kick-off meeting: Conduct a monthly meeting with the contractor to plan the objectives of upcoming sprints and review contractor`s manpower to meet the agreed deliverables.
Set sprint goals: Define clear, achievable goals for the sprint and associated acceptance criteria, including specific delivery targets, Quality standards as well as Key Performance Indicators (KPIs) for each task to be recorded in the sprint meeting minutes.
Agree on the required level of effort for the various sprint tasks.
Backlog Review: Review and prioritise the backlog of tasks, issues, and improvements from previous sprints.
Assess each payment milestone cycle duration of one calendar month. State of completion and validation of each sprint status and sign off sprints to be submitted for payment as covered in Section 4.
3.2. Sprint Execution
Objective: Contractor to execute the agreed "sprint plans" with continuous monitoring and adjustments.
Regular meetings between NCIA and the contractor to review sprint progress, address issues, and make necessary adjustments to the processes or production methodology. The Meetings will be physically in the office, or in person via electronic means using Conference Call capabilities, according to the NCI Agency staff instructions.
Continuous improvement: Contractor to establish a continuous feedback loop to gather input from all stakeholders for ongoing improvements and their subsequent implementation depending on NCIA approval.
Progress Tracking: Contractor to use a shared dashboard or tool to track the status of the sprint deliveries and any issues.
Quality Assurance/Quality Check: Contractor shall ensure that the quality standards agreed for the sprint deliverables are maintained throughout the sprint.
Quality Control: NCIA to perform the Final Quality Control of the agreed deliverables and provide feedback on any issues.
3.3. Sprint Review
Objective: Review the sprint performance and identify areas for improvement.
At the end of each sprint, there will be a meeting between the NCI Agency and the Contractor to review the outcomes against the acceptance criteria comprising sprint goals, agreed quality criteria and Key Performance Indicators (KPIs).
Define specific actions to address issues and enhance the next sprint.
3.4. Sprint Payment
For each sprint to be considered as complete and payable, the contractor must report the outcome of their work during the sprint, first verbally during the retrospective sprint review meeting and then in writing within three days after the sprint's end date. A report must be sent by email to the NCI Agency manager, highlighting all work performed against the agreed tasking list set for the sprint.
The contractor's payment for each sprint will be depending upon the achievement of agreed Ac...
About the Company
EMW was founded in 1995 by engineers and managers who formerly held senior positions in well known telecommunications and information technology companies to pursue their vision for this new company.
Our core business is providing information and communication technology services in the areas of planning, engineering and implementation; project and program management; systems integration; operations and maintenance; and training. Our competencies range over all aspects of inside and outside plant; feeder, access and inter-o...
Know more