2025-0273 Technical Software Tester Services NIRIS Testing (NS) - MON 15 Sep at EMW, Inc.. Deadline Date:. Monday 15 September 2025 . Requirement:. Provision of Technical Software Tester Services Support the NIRIS Testing. Location:. Off-Site. Note: . Please refer to your Subcontract Agreement, article 6.4.1.a, which states “Off-Site Discount: 5% (this discount is applicable to all requirements, and applies when the assigned personnel are permitted to work Off-Site, such as at- home)". Please be sure to price this discount in your overall price proposal when submitting bids against off-site RFQs. Period of Performance:. 2025 BASE: starting date 13th of October 2025 – 31st December 2025 with possibility to exercise the following options:. 2026 Option: 1st January 2026 until 31st December 2026. 2027 Option: 1st January 2027 until 31st December 2027. 2028 Option: 1st January 2028 until 31st December 2028. Required Security Clearance:. NATO SECRET. . 1 INTRODUCTION. The NATO Communications and Information Agency (NCI Agency) located in The Hague, The Netherlands, is currently involved in the development of new capabilities for NATO as well as in the support of existing capabilities. In the light of these activities, the C2 Service Centre is looking for ONE technical software tester.. More specifically, the work will support the full software development cycle of the Networked Interoperable Real-Time Information Services (NIRIS) software. NIRIS has been developed to meet the Minimum Military Requirement (MMR) for receiving, disseminating and providing situational awareness information for Command and Control (C2) and is currently the most widely used system for providing such information in NATO.. 2 OBJECTIVES. The main objectives of this statement of work can be summarized as follows:. - Test, update and maintain NIRIS software modules.. 3 SCOPE OF WORK. Under the direction / guidance of the Solution Architect, Service Delivery Manager, Test Manager and Project Manager, the services to be provided are related with executing and maintaining the NIRIS test cases. This includes the following activities:. • Write, execute and maintain the NIRIS test cases both manually and automatic.. • Work closely with the developers/subject matter experts to understand the product use cases and features.. • Attend to team meetings to provide progress updates, and impediments to the colleagues and delegated staff.. • Share the knowledge inside the team, organize trainings or demos and document the information knowledge database.. • Work independently, self-organized with focus on outcome that match the teams’ target.. • Create setups that include Virtual Machines and standard servers (DNS, HTTP, Active Directory, and Monitoring) on Linux based operation systems.. It is envisioned that these services are provided by ONE CONTRACTOR experienced software tester.. 4 ROLES AND RESPONSIBILITIES. The development and testing services will be carried out on an Agency-provided laptop while using remotely the engineering and test facilities in the NATO Software Factory hosted in Microsoft Azure. These facilities consists of all necessary development and test services (such as Gitlab, Jira, Zephyr, Nexus…). The contractor shall update the status of the NIRIS development tasks in Jira, commit code in Gitla b, and maintain test procedures and test results in Zephyr. Some of the work could also be requested to be conducted locally in NCI Agency in The Hague, The Netherlands.. The contractor will be part of a team (Service Delivery Manager, Project Manager, Solution Architect, Technical Lead, Software Developers, Testers, etc.) geographically distributed and working using an Agile and iterative approach using multiple sprints. Each sprint is planned for a duration of one (1) week.. 5 DELIVERABLES AND PAYMENT MILESTONES. Detailed resource assessments will be agreed during each sprint meeting as set out in Section 6.. Payments shall be dependent upon the successful acceptance of each sprint and the validation as set out under Section 6. All Invoices shall be accompanied with a Certificate of Acceptance (COA, Annex B) signed by the Contractor and project authority.. Each sprint has a duration of one week. The content, scope and acceptance criteria of each sprint will be agreed during the sprint‐planning meetings as covered in Section 6, in writing. Each payment milestone cycle is planned for a duration of one calendar month. Upon completion and validation of each sprint and at the end of the monthly milestone, all completed sprints can be submitted for payment.. The NCIA team reserves the possibility to exercise a number of sprints later, based on the same sprint deliverable timeframe and cost, depending on project priorities and requirements.. In 2025, the following deliverables are expected from the service as set in this statement of work.. Deliverable: Up to 12 sprints for NIRIS software testing (Number of sprints is estimated and will be adjusted based on actual starting date.). Payment Milestones: Payment Milestones will be end of the month for all the Sprints completed and accepted within the respective month. 2026 Option: 01 January to 31 December 2026. Deliverable: Up to 41 sprints . Cost Ceiling: Price will be determined by applying the price adjustment formula as outlined in CO‐115786‐ AAS+ Special Provisions article 6.5.. Payment Milestones: Payment Milestones will be end of the month for all the Sprints completed and accepted within the respective month. 2027 Option: 01 January to 31 December 2027. Deliverable: Up to 41 sprints . Cost Ceiling: Price will be determined by applying the price adjustment formula as outlined in CO‐115786‐ AAS+ Special Provisions article 6.5.. Payment Milestones: Payment Milestones will be end of the month for all the Sprints completed and accepted within the respective month. 2028 Option: 01 January to 31 December 2028. Deliverable: Up to 41 sprints . Cost Ceiling: Price will be determined by applying the price adjustment formula as outlined in CO‐115786‐ AAS+ Special Provisions article 6.5.. Payment Milestones: Payment Milestones will be end of the month for all the Sprints completed and accepted within the respective month. 6 COORDINATION AND REPORTING. 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 resource 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:. 6.1. Sprint Planning:. Objective: Plan the objectives for the upcoming sprint.. Kick-off meeting: Conduct an initial meeting with the contractor to plan the objectives of upcoming sprints.. Set sprint goals: Define clear, achievable goals for the sprint.. Backlog Review: Review and prioritize the backlog of tasks, issues, and improvements from previous sprints.. 6.2. Sprint Execution. Objective: The resource to execute the “sprint plans” with continuous monitoring and adjustments.. Regular meetings (including daily stand-up) between NCI Agency 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 project manager’s instructions.. Continuous improvement: The resource 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: The resource to use a shared dashboard or tool to track the status of the sprint deliveries and any issues.. 6.3. Sprint Review. Objective: Review the sprint performance and identify areas for improvement.. At the end of each sprint, there may be a meeting between the NCI Agency and the team to review the outcomes.. Define specific actions to address issues and enhance the next sprint.. 6.4. Sprint Payment. For each sprint to be considered as complete and payable, the resource must report the outcome of their work during the sprint within three days after the sprint’s end date. A report must be sent by email to the NCI Agency project manager, listing all the work achieved against the agreed tasking list set for the sprint.. The payment shall be dependent upon successful acceptance as set in the above planning/review meetings. This will follow the payment milestones that shall include a completed Certificate of Acceptance (COA) – See Annex B.. Invoices shall be accompanied with a Certificate of Acceptance sheet (COA) – (Annex B) signed by the Contractor and project authority.. 7 SCHEDULE. This task order will be active immediately after signing of the contract by both parties.. It is expected that the initial services start being provided in October 2025 (13th October 2025 – tentative start date) and ending not later than December 2025.. If the sprints of the annual options are exercised, the period of performance is within 01 January to 31st December of the relevant year.. 8 SECURITY. Performance of the services described in this SOW require a valid NATO SECRET security clearance provided by the national security organization and valid at the time of submission of the bid covering the period of the requirement.. 9 CONSTRAINTS. All the documentation provided under this statement of work will be based on NCI Agency templates or agreed with project point of contact.. All scripts, documentation and required code will be stored under configuration management and/or in the provided NCI Agency tools.. 10 PRACTICAL ARRANGEMENTS. The contractor is expected to work off site. Work on-site can also be arranged with the Project Manager.. It may be required to travel to NCI Agency The Hague and other sites within NATO for completing these tasks.. Travel costs are out of scope and will be borne by the NCI Agency separately in accordance to the provisions of the AAS+ Framework Contract.. This work must be accomplished by ONE resource. In the event the contractor leaves during the contract period, he or she shall be replaced by a new contractor who has the required qualifications and is acceptable. AAS Framework contract Terms and Conditions apply.. 11 QUALIFICATIONS. [See Requirements]. 8 SECURITY. Performance of the services described in this SOW require a valid NATO SECRET security clearance provided by the national security organization and valid at the time of submission of the bid covering the period of the requirement.. 11 QUALIFICATIONS. The consultancy support for this work requires a software tester with the following qualifications:. . Candidate is able to work independently and has can-do spirit and is focused on deliverables. . The candidate has relevant and recent experience in software testing for WebGUI, RestAPI, and CLI interfaces for networking-products. . The candidate is able to troubleshoot and debug the problems on Windows Servers and Linux OS (IP Addressing, routing, DNS, HTTP, Active Directory, Certificate Management). . The candidate has basic knowledge in programming and scripting languages (preferably in Java, Linux bash, ansible). . The candidate has basic experience in using development tools (e.g. Jira, Zephyr, GitLab) and the Scrum methodology.. . The candidate is able to plan, write and execute manual test cases for networking- products features. . The candidate has experience in testing computer networking software and Tactical Data Link (Link16, Link22, OTH-G) software.. . The candidate has relevant experience in testing interoperability between software systems. . Possession of technical certifications (Microsoft, RedHat, CompTia, CISCO) is a big advantage. . Testing certifications ISTQB/TMAP or similar are nice to have. . Relevant experience in writing end to end automation test cases (e.g. Robot Framework, Gauge, Cucumber) is nice to have. . The candidate is fully professional proficient in English. . The candidate must have the nationality of one of the NATO nations.. . Company Location: Netherlands.
Telegram
Linkedin
Twitter
Instagram
Facebook