Development Standards Process¶
Software development Standards and principles are being developed by a task force composed of DHI experts and specialists in the relevant area.
When development standards and principles are being developed, they follow a process to ensure that the standards will:
- be developed by key experts in DHI on the subject.
- contain the required scope and content.
- be reviewed by stakeholders.
- be rolled-out to the right audience.
The process outlined below must be followed during the development of standards.
flowchart LR
%% Overall layout is left-to-right
Col1 --> Col2
Col2 --> Col3
Col3 --> End([Implementation support,<br/>Reviews and Audits])
%% Standards setup
subgraph Col1[<b>Standards Setup & Scope</b>]
direction TB
B[Define standard owner<br/>and task force];
B --> C{Architecture Board approves<br/>the task force?};
C --> |No| B;
C --> |Yes| D[Define scope];
D --> E{Scope approval};
E --> |No| D;
end
%% Write standards
subgraph Col2[<b>Write Standards & Review</b>]
direction TB
F[Initial Draft] --> G[Task force review<br/>and updates];
G --> H{Task force approval?};
H --> |No| G;
H --> |Yes| I[Stakeholder review<br/>and updates];
I --> J{Stakeholder approval?};
J --> |No| I;
end
%% Standards review
subgraph Col3[<b>Approval & Roll-out</b>]
direction TB
K{CTO/AB approves standards?};
K --> |Yes| L[Make Roll-out Plan];
L --> M{Architecture Board approves<br/>the roll-out plan?}
M --> |Yes| N[Roll-out];
end
style C fill:#c2f0c2,stroke:#2d8a2d,color:#000
style K fill:#c2f0c2,stroke:#2d8a2d,color:#000
style M fill:#c2f0c2,stroke:#2d8a2d,color:#000
style E fill:#f0e68c,stroke:#B58B00,color:#000
style H fill:#f0e68c,stroke:#B58B00,color:#000
style J fill:#f0e68c,stroke:#B58B00,color:#000-
Define development standard owner and task force
Assign a standard owner (driver) and set the task force, find stakeholders, and define the audience.
The work done by the owner and task force related to writing the standards can be registered on the Architecture Board project.
Defining the task force also means initiating the standards document specifying the task force, stakeholders, and audience on the DHI Developers.
The composition of the task force must be approved by the Architecture Board.- Standard owner/driver
The standard owner is responsible for setting up meetings and making sure that the standards are written and reviewed by the task force.
Standards work must be organized creating a feature in the Architecture Board project in the epic of the category and user stories for tracking the progress of the standards. - Task force
The task force is a group of experts who write the standards and approve them before the standards goes into stakeholder review.
The task force must be formed so that they have skills and the ability to define the scope.
The task force members must cover affected teams, projects and products within the scope. - Stakeholders
Stakeholders are key people within the area and the region that are supposed to use and apply to standards. The stakeholder group will assist in review and roll-out of the standards.
The stakeholder group must cover most T&I offices to ensure a smooth roll-out.
Consider staff in T&I: CZ, PL, US/CAN, DE, DK Projects, DK Products, Data Model Integration and Earth Observation Centre (if not already represented in the task force)
Stakeholders within GBUs should be considered on a case-by-case basis. If stakeholders are required, reach out to the GBU OpEx Directors to identify suitable candidates.
- Standard owner/driver
-
Task force Approval
Gate: The Architecture Board must approve the task force and stakeholders to ensure that specialists able to assist in defining scope and writing the standards are available. - Define scope
The standard owner makes sure that a suggested scope/ToC including a short description for each section, to make it clear what the standards scope is.
While reviewing the scope, the standards could be split into multiple standards and tasks.
The scope must also identify dependencies on other standards. - Scope approval
The task force reviews and approves the suggested scope. - Initial Draft (standard owner)
The initial draft must be created and written based on the standards template as markdown (template in section below) created on DHI Developers.
Do not add the markdown(s) to the 'mkdocs.yml' page until they are published.
The draft document is written by the standard's owner. Draft documents and/or documents in progress will be shared with the task force and the stakeholders identified.
The standard owner must organize work on standards creating a feature in the Architecture Board project in the epic of the category (Package) and user stories for tracking the progress of the standards. - Task force review and updates
The task force reviews, updates and approves the standards. This is done in the markdown file created on DHI Developers.
It is important that all task force members provide their input.
In case the standard owner or task force members does not have time for providing input for a specific deadline, contact a member of the Architecture Board to agree on next steps. -
Stakeholder review
Stakeholders get the standards document for review once approved by the task force. Once feedback from stakeholders has been considered, the standards are ready to be published.
Stakeholder review is done sharing standards previews on DHI Developers with the stakeholders.- The standard owner sets up an introduction meeting with all stakeholders explaining the objective and how to provide their feedback.
- Stakeholders should be given a one-week window to provide their feedback.
The task force must agree on changes suggested by stakeholders before updating the standards.
- The standard owner sets up an introduction meeting with all stakeholders explaining the objective and how to provide their feedback.
-
Development Standards Approval
Gate: The CTO and/or the Architecture Board must approve the reviewed standards before a standard roll-out can start.
The CTO should, as a rule of thumb, approve mandatory standards, AI related standards and Cloud/Azure related standards. - Make Roll-out plan and roll-out
The Architecture Board is responsible for roll-out and must approve the plan for rolling-out the standards.
The standards must be published on DHI Developers and Viva Engage (e.g. section Developers).
Standards must during roll-out be implemented in the DHI Playbook (contact jabh). It is important that the audience of standards gets notified about the new standards.
An important part of roll-out is to make sure that people know about the standards. This means that just publishing standards must be accompanied by alignment with key stakeholders.
A suggested roll-out template can be found in the Roll-out Plan Template section below.
Gate: The Architecture Board must approve the roll-out plan. - Implementation support, Reviews and Audits
Once development standards have been published, individual appliance and review plans, AI skills, and supporting documents will be made.
E.g. templates (Visual Studio etc.), step-by-step guides, standard updates and a review and audit process.
Development Standards Template¶
Every set of standards must contain a mandatory set of sections.
# [Title]
## Version History
|Version|Date|Description/Updates|
|---|---|---|
|1.0|[Date]|[Description]|
## Introduction
Short introduction to the standards as a very short summary.
## Contacts
Section listing who are working on the giuidelines. The list must be approved by the Architecture Board.
|Standard Owner|[nn](mailto:nn@dhigroup.com "No name")|
|Task force|[nn](mailto:nn@dhigroup.com "No name"); [nna](mailto:nna@dhigroup.com "No Name A")|
|Stakeholders||
|Approver(s)|Architecture Board|
## Roles to Apply
List of development roles that must know about the content of the standards.
Development roles:
- Architects
- Backend developers
- Frontend developers
- Infrastructure/DevOps Engineers
- Product Manager/Product Owners
- Testers
## Enforcement Levels
Section providing an overview of the sections of the standards, specifying the enforcement levels as well as what kind of projects/products the enforcement level applies to.
|Section|Enforcement Level|Comment|
|---|---|---|
|Section 1|Important|Specifying ownership of the individual task is important.|
## References
Section containing references to other standards.
These references must also be found in the one or more sections of the standards.
Roll-out Plan Template¶
The roll-out plan can be started once the standards have been approved by either the Architecture Board or the CTO.
Use this template as a base for the roll-out plan.
For every set of standards¶
- Publish on DHI Developers
The standard owner publishes standards on the DHI Internal Developer site containing the standards. - Viva Engage (DHI Daily Digest)
The Architecture Board makes a post on Viva Engage in the Technology and Innovation Community so that T&I Staff gets a DHI Daily Digest mail.
The standard owner should make a draft of the post.
If the standards are relevant to all DHI staff, post the standards in the All Company Community. - Roll-out on PO Community Meeting(s)
A brief introduction for product owners on the weekly T&I PO Community meeting being held on Wednesdays at 10-11 CET.
The meeting should be a short introduction to the development standards and what to being published outlining the content. Highlight the affected development roles to the product owner.
No recording will be made. - Make development staff on-boarding video
Make a 10-15 minute on-boarding video for development staff affected (e.g. as a meeting with no attendees).
The video should provide a short introduction for the development standards, what the standards contain and where to find them. - Store roll-out meeting recording(s)
Store employee roll-out meeting recordings/videos on the DHI Training Portal.
Make sure that everybody has access to the recording and add a link to the recording in the standards on DHI Developers.
Contact Lars Hoffmann to get recorded videos published on the DHI Training Portal. - Contact PO's and GBU stakeholders
Contact T&I product owners and GBU project managers to make sure that they know about standards. Have a dialog on what standards they can, should or must apply to.
Review and audit process should be ready and suggested to the PO's. - Skill development
Making skills for AI agents that can assist in code base checking, state reporting and code fixing of product and project code bases to help teams applying to development standards.
Regular meetings and updates¶
-
Development Manager Updates
Development managers should have regular updates on standards released and what teams and products should apply to what standards (as agreed with PO's), so that managers have a change to follow up with development staff. -
Viva Engage
Use Viva Engage regularly to highlight standard updates and/or summaries.
Review and Audits¶
A robust software development review and audit process ensures:
- Quality and security are built into delivery
- Compliance and governance are enforced systematically
- Risks are identified early (technical, legal, operational)
- Consistency across teams and geographies
The review and audit process is agreed and planned with product owners depending on the maintenance tier agreed with the individual product owner.
Standard Tiers¶
Standard tiers define the standards governance effort based on product criticality, budget and risk.
Each tier determines:
- Review depth & frequency
- Required automation & audit controls
| Standards Tier | Description | Review Frequency |
|---|---|---|
| High | Strategic investments, proactive maintenance, high investment budget, standards appliance plan required. | Quarterly |
| Dedicated | Business critical systems, regular maintenance, dedicated maintenance budget, partial standards appliance plan | Every 6 months / per release |
| Reactive | Reactive maintenance, limited enhancements, limited maintenance budget, selected standards appliance plan | Yearly |
| Minimal | Legacy systems, minimal maintenance, risk acceptance, no or limited budget, no standards appliance plan | N/A |
Standard Tier Alignment and Appliance¶
The plan for aligning standard tiers and planning the efforts for each product or project is in progress and is expected to be completed in August 2026.
- Product owners suggest standard tiers (Done)
- âś…Product development standards tiers (for 2026 and 2027) to be aligned with business owners (July)
- Development standards are being finalized and AI skill development completed(June, July and August)
-
🔄Individual development standards appliance plan to be made with each PO (August and September)
The Architecture Board and standard owners will reach out to PO’s- Access to repos granted
The repositories to scan are identified and read access to the repositories are granted to FRT and KTH. - Appliance Reports
Appliance reports gets generated based on all or selected development standards. - đź“‹Report review and plan tasks/actions
The Architecture Board sets up a meeting with relevant stakeholders including the product owner to discuss plan and tasks for the individual product.
- Access to repos granted
Products and Standard Tiers¶
The list of assets/products and the product owners are listed below with standard tiers.
Please find the Digital Assets by PO and BO on SharePoint, managed by Martin Lythe Ciborowski
Standard tiers of individual products will be evaluated every year.
Note
Suggested product standard tiers are provided by product owners and are in an alignment process with business owners and management.
âś… - Development standard tiers have been aligned with Business Owners.
🔄 - Development standards appliance plan in progress
đź“‹ - Development standards appliance plan ready
đźš« - Development standards appliance plan on hold or does not apply.
| Product | Product Owner | Business Owner | Standards Tier (2026) | Standards Tier (2027) |
|---|---|---|---|---|
| Azure Market and SaaS | Karthik Balachandran (KBAL) | Karthik Balachandran (KBAL) | âś…Reactive | âś…Reactive |
| Bathymetry Portal | Marie Lund Larsen (MLLA) | Lars Boye Hansen (LBH) | âś…Reactive | âś…Reactive |
| Data Link | Niels Riegels (NDR) | Patrick Dich Grode (PDG) | âś…Reactive | âś…Reactive |
| DC.Live | Nita Renanta (NIRE) | Henrik Refstrup Soerensen (HRS) | High | High |
| DHI BlueCast | Babino Gupta (BAGU) | Reza Kazeroni (MKFA) | Reactive | Reactive |
| DHI CityFlow Live | Johannes Winberg (JOWI) | Lars-Goeran Gustafsson (LGG) | âś…Dedicated | âś…Dedicated |
| DHI CityFlow Live Receiving water | Johannes Winberg (JOWI) | Kalyan Chakravarthy (CMKA) | âś…Dedicated | âś…Dedicated |
| DHI CityFlow Live Stormwater | Johannes Winberg (JOWI) | Lars-Goeran Gustafsson (LGG) | âś…Dedicated | âś…Dedicated |
| DHI CityFlow Live Treatment Plant | Johannes Winberg (JOWI) | Henrik Refstrup Soerensen (HRS) | âś…Dedicated | âś…Dedicated |
| DHI CityFlow Live Wastewater Network | Johannes Winberg (JOWI) | Lars-Goeran Gustafsson (LGG) | âś…Dedicated | âś…Dedicated |
| DHI CityFlow Live Water Distribution | Johannes Winberg (JOWI) | Jonas Kirstein (JOKI) | âś…Dedicated | âś…Dedicated |
| DHI PlumeCast | Babino Gupta (BAGU) | Reza Kazeroni (MKFA) | Reactive | Reactive |
| DIMS.CORE | Nita Renanta (NIRE) | Henrik Refstrup Soerensen (HRS) | âś…Minimal | âś…Minimal |
| Domain Services | Hizrian Muhammad Faris (FARI) | Hizrian Muhammad Faris (FARI) | âś…Reactive | âś…Reactive |
| Entitlement System (Revenera) | Jiri Kirkos (JIKI) | Douglas N. Graham (DNG) | âś…Reactive | Dedicated |
| 🔄FEFLOW | Volker Clausnitzer (VCL) | Dr. Carlos Andres (CVI) | ✅Dedicated | ✅High |
| Leakage Monitor | Jiri Kirkos (JIKI) | Zdenek Svitak (ZS) | âś…Dedicated | Dedicated |
| License System (Old) | Lasse Kelman Christensen (LAC) | Lasse Kelman Christensen (LAC) | âś…Minimal | âś…Minimal |
| Litpack | Elena Stuart (ELST) | Stephen J Flood (SJF) | âś…Reactive | âś…Dedicated |
| Mesh Builder | Niels Riegels (NDR) | Niels Riegels (NDR) | âś…Reactive | âś…Reactive |
| MIKE 21 Mooring Analysis | Elena Stuart (ELST) | Stephen J Flood (SJF) | âś…Dedicated | âś…Dedicated |
| MIKE 21/3 | Elena Stuart (ELST) | Stephen J Flood (SJF) | âś…Dedicated | âś…Dedicated |
| MIKE 21C | Aurelien Gasc (AUG) | Mark Britton (MFB) | âś…Minimal | âś…Minimal |
| MIKE C-Map | Elena Stuart (ELST) | Stephen J Flood (SJF) | âś…Minimal | âś…Minimal |
| MIKE Cloud Platform | Leona Tejklova (LETE) | Ilias Pliotas (ILIP) | âś…Dedicated | âś…Dedicated |
| MIKE ECO Lab / ABM Lab | Elena Stuart (ELST) | Stephen J Flood (SJF) | âś…Dedicated | âś…Dedicated |
| MIKE HYDRO Basin | Niels Riegels (NDR) | Bertrand Richaud (BER) | âś…Reactive | âś…Reactive |
| MIKE Metocean Simulator | Niels Riegels (NDR) | Patrick Dich Grode (PDG) | âś…Reactive | âś…Reactive |
| MIKE Mine | Nita Renanta (NIRE) | Ferdinand Flechtner (FEFL) | âś…Dedicated | âś…Dedicated |
| MIKE OPERATIONS | Aurelien Gasc (AUG) | Elbys Jose Meneses (EJME) | âś…Dedicated | âś…Dedicated |
| MIKE OPERATIONS SW Enabler | Aurelien Gasc (AUG) | Aurelien Gasc (AUG) | âś…Dedicated | âś…Dedicated |
| 🔄MIKE SHE | Aurelien Gasc (AUG) | Philipp Huttner (PHHU) | ✅Dedicated | ✅Dedicated |
| MIKE View | Niels Riegels (NDR) | Niels Riegels (NDR) | âś…Minimal | âś…Minimal |
| MIKE WaterNet Advisor | Jiri Kirkos (JIKI) | Petr Ingeduld (PI) | âś…Dedicated | âś…Dedicated |
| 🔄MIKE+ | Mathieu Hellegouarch(MJH), Niels Riegels (NDR) | Morten Just Kjoelby (MJK), Philipp Huttner (PHHU) | ✅Dedicated | ✅Dedicated |
| MOOD | Kai Claussen (KCL) | Patrick Dich Grode (PDG) | âś…Reactive | âś…Dedicated |
| Python Libraries | Henrik Andersson (JAN) | Jesper Sandvig Mariegaard (JEM) | Dedicated | Dedicated |
| Shared MIKE Components | Lasse Kelman Christensen (LAC) | Lasse Kelman Christensen (LAC) | âś…Dedicated | âś…Dedicated |
| Water Tools Portal (WTP) | Nita Renanta (NIRE) | Elbys Jose Meneses (EJME) | âś…Reactive | âś…Reactive |
| WEST | Christopher Eugen Gaszynski (CHGA) | Henrik Refstrup Soerensen (HRS) | âś…Reactive | âś…Dedicated |
Other T&I Products or Teams¶
Products with no an official product owner, product owners that are not part of the Product Owner Community or supporting teams without direct product ownership.
| Product or Team | Product Owner/Manager | Standards Tier (2026) | Standards Tier (2027) |
|---|---|---|---|
| Build Automation & QA Team | Karthik Balachandran (KBAL) | âś…Dedicated | âś…Dedicated |
| 🔄Core & Common | Jesper Grooss (JGR), Troels Haar Hemmingsen (TRHE) | ✅High | ✅High |
| Earth Observation Centre of Excellence Portals - et4fao.dhigroup.com - frame.dhigroup.com - eo.dhigroup.com - marine-vegetation.satlas.dk - esa-sen4et.org - bathymetry.satlas.dk - nanok.xyz - satlas.dk - urban.satlas.dk - eo-labs.dhigroup.com - eo4wi.earth |
Marie Lund Larsen (MLLA) | âś…Minimal | âś…Minimal |
| Earth Observation Centre of Excellence Portals - coastalprofiler.dhigroup.com - coastalmapper.dhigroup.com - mcsav.dhigroup.com - sav-sweden-v2.dhigroup.com - sav-denmark.dhigroup.com - marineobserver.dhigroup.com - soilmoisture.io - map.communityactionforfreshwater.org - communityactionforfreshwater.org - excavation.z16.web.core.windows.net - vistatrees.dhigroup.com - sdg632hub.org - sdg661.app - map.globalwetlandwatch.org - datacube.dhigroup.com - regioner.dhigroup.com - worldforestdata.dhigroup.com |
Marie Lund Larsen (MLLA) | âś…Reactive | âś…Reactive |
| Earth Observation Centre of Excellence Portals - ramona.earth |
Marie Lund Larsen (MLLA) | âś…Reactive | âś…Minimal |
| Earth Observation Centre of Excellence Portals - LBST |
Lotte Nyborg (LN) | âś…Dedicated | âś…Reactive |
| đźš«MUSE | Babino Gupta (BAGU) | N/A | N/A |
| UX Design | Anna Katrine Hoegh Andersen (AKHA) | High | High |
| WBalMo | Dr. Tobias Pilz (TOPI) | âś…Minimal | âś…Dedicated |
GBU Development¶
GBU's or DHI Companies in some cases developed and maintain products independent of T&I.
| Product | Company/Office | Contact/Manager | Business Owner | Area | Standards Tier (2026) | Standards Tier (2027) | Comment |
|---|---|---|---|---|---|---|---|
| đźš«Data Farm | Christian Fischer Holm (CFH) | Marine & Coastal | N/A | N/A | Currently no synergies. Singapore (EMMP), Ballastvand, M&C Nordics Contact:NGR |
||
| MIKE+ CN | DHI China | Jiyan Meng (MJY) | Water in Cities | Reactive | Dedicated | ||
| MIKE Marine CN | DHI China | Jiyan Meng (MJY) | Marine & Coastal | N/A | Reactive | ||
| NCOS Online | DHI Seaport Pty Ltd, Australia | Oliver Brass (OLBR) | Simon Brandi Mortensen (SBM) | Marine & Coastal | Reactive | Reactive | Focus on Security and Infrastructure standards. |
| SKYNET | DHI S.r.l. a socio unico, Italy | Mirko Flauto (MIFL) | Andrea Crosta (ACR) | Marine & Coastal, Water in Cities, Inland | Standard tier will be defined once skill reports are available. | ||
| Water Tools Portal (WTP) | Int. Development Digital Services | Elbys Jose Meneses (EJME) | Bespoke frontend web development for individual projects by EJME |
GBU Development Contacts¶
This section lists development staff setting in GBU's to be included in communities and development standards alignment.
| Developer | Office | Projects |
|---|---|---|
| Hema Kumar (HAPP) | NZ | MEDUSA, CREST, SAFESWIM |
Projects¶
Active GBU projects and strategic investments where T&I are involved.
| Project | GBU Contact | T&I Manager | T&I dev. staff | Comment |
|---|---|---|---|---|
| Badevandsudsigten | Mai-Britt Kronborg (MBK) | Louise Rosenberg Maersk (LORM) | BAGU; MATF; PAUZ | |
| CIAM | N/A | Kristian Thage (KTH) | DDRA; FRT; LETE; FTOL | New DHI authentication and authorization |
| Gandalf | Jan Novak (JANO) | Louise Rosenberg Maersk (LORM) | SV; FIK | |
| MUDP | Lise Lyck (LLY) | Louise Rosenberg Maersk (LORM) | JAUH | |
| North Sea Portal | Jesper Dannisøe (JDA) | Louise Rosenberg Maersk (LORM) | BOGD | |
| SeaMe/RWE | Jesper Dannisøe (JDA) | Louise Rosenberg Maersk (LORM) | FTOL; RASA |
OpEx Directors¶
- Marine & Coastal: Jacob H Jensen (JHJ)
- Water in Cities + Water Resources: Mikkel Moeller Christensen (MMCH)