2026-0081 JChat Engineering Support (NS) - WED 10 Jun

About the role

Deadline Date: Wednesday 10 June 2026 Requirement: JChat Engineering Support Location: Offsite with remote access to NCIA software factory and collaborating with NCIA team members with occasional travel to locations throughout NATO 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: From contract signature until 31 December 2026 Required Security Clearance: NATO SECRET (or higher) 1. INTRODUCTION The NATO Information and Communication 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. JChat has been developed by the NCI Agency to provide operators with a text-based asynchronous chat capability. Chat communication is used daily by the operators to pass information, coordinate operations, and support collaborative decision-making. JChat is providing one-to-one chat, group (multi-user) chat and multi-user conferencing (moderated chat) and is based on Instant Messaging (IM) technology. In order to support these activities, the C2 Centre is looking for a team of maximum six developers to augment the NCIA team. 2. PURPOSE The purpose of this Statement of Work is to define the scope, deliverables, pricing, and governance for the delivery of new versions of the JChat Client and server software. 3. OBJECTIVES The following objectives have been defined for this statement of work: Support the preparation of a new release of the JChat Java Client. Support the preparation of a new release of the JChat Web Client. Support the preparation of a new release of the JChat Openfire Server. Support the preparation of a new release of the M-Link server for JChat. Represent the JChat team in test events. Maintain the development pipeline. 4. SCOPE OF WORK The scope is defined in terms of business outcomes and capabilities rather than detailed functional specifications. The detailed implementation shall be refined iteratively through the Product Backlog. 4.1 Scope Flexibility The Client may substitute or reprioritize Product Backlog items at any time, provided that: the estimated effort over all work packages remains within a tolerance band of ±10% of the baseline backlog; and no change to the Firm Fixed Price is required. Such flexibility is required as there are dependencies on COTS products (M-Link) and open-source products (Openfire) with their own delivery timelines. Also, the effort on each of the work packages may be changed based on priorities from the operational community. However, it is expected that the overall effort over all work packages will remain the same. The introduction of new work packages or scope increases beyond the tolerance band of +10% shall constitute a Change Request. 5. DELIVERY APPROACH The Supplier shall deliver the Services using Agile principles consistent with Scrum, including iterative development, incremental delivery, and continuous stakeholder feedback. Minimum Agile Practices Required: Scrum approach based on a two-week development activity, including Planning meetings, Retrospective meetings, Closure meetings, Backlog refinement meetings. Continuous integration and testing. 6. WORK PACKAGES Activities under the various work packages, except WP05, will be expressed in deliverables. WP01: Participate in Scrum meetings. Estimated per developer at 2.5 hours of standup per two-week development activity, four hours of refinement per two-week development activity, four hours of review per two-week development activity, a retrospective meeting and planning meeting per two-week development activity. Estimated Work Package weight: implicit (cost considered included in overall SoW). WP02: Support the preparation of a new release of the JChat Java Client. Under this work package the contractors of the supplier will support the development of a new version of the JChat Java client software following the Scrum methodology based on a backlog of tickets maintained in JIRA by the Purchaser. All activities for the preparation of the release, e.g. development, documenting, testing and reviewing, release building will be expressed as tickets with Story Points (SP) under this work package. Estimated Work Package weight: 32%. WP03: Support the preparation of a new release of the JChat Web Client. Under this work package the contractors of the supplier will support the development of a new version of the JChat web client software following the Scrum methodology based on a backlog of tickets maintained in JIRA by the Purchaser. All activities for the preparation of the release, e.g. development, documenting, testing and reviewing, release building will be expresse

Your Match

How well this role fits your profile.

Company Intel

What employees say

Worked at EMW, Inc.? Share your experience