Digital programme (DUO)

DUO aims to ensure that digital development is efficient, well enough planned and transparent.

DUO - Steering digital transformation

Since autumn 2018, the development of digital services at the Ä¢¹½Ö±²¥ has been driven forward according to the DUO (Digitaalisen uudistamisen ohjaus) steering model, following the , but customized for our own purposes. 

The aim is to increase transparency about digital development across the university and to bring more structure to the process, thus increasing efficiency.

DUO development is guided and prioritised by the Digital Programme steering groups.

Agile development accelerates and drives action

The SAFe framework bases its philosophy on two major development models: and .

Lean seeks to minimise waste and queue things up, not in parallel.

Agile development values communication with the customer and a functional outcome above all else.

How can I participate in DUO?

For more information, please contact Merja Laamanen, Head of Digital Transformation Office merja.h.laamanen@jyu.fi.

Transparency at the heart of DUO

One of DUO's key principles is to make development more transparent, in terms of plans, progress and implementation. All development is linked to the priorities of the university's strategy, and each individual development contributes to a specific area.

The MS Teams platform, the University website and the Jira project management tool (for stakeholders and developers) are also used to make activities transparent. Transparency increases trust between the contractor and the client and improves communication.

Development increments in 3-month cycles

In the SAFe framework, the planning and development of an organisation is broken down into 3-month cycles, called development increments. The cycle goes roughly like this:

  • September-November
  • Christmas-February
  • March-May
  • June-August

An essential part of the three-month cycle is synchronisation with the rest of the organisation. Being able to agree in advance on this rhythm makes it easier to plan and prioritise what needs to be done. Another important thing is to make dependencies visible. At the end of each development increment, the last two weeks are reserved for planning and innovating for the next increment.

See also