agile methods

Flexible methods

Definition

(see Digital Transformation Paper 2020–2025 pp. 56-58)

The rapid evolution of the potential of information and communication technologies and the complexity of the issues to be solved, which arise during the development of digital public services, do not allow the analysis, understanding and evaluation of the potentially available solutions from the outset. This makes it difficult, or in some cases impossible, to identify clearly in advance the requirements for the implementation of digital services. Also, the adoption of models of sequential implementation of the phases of a project, such as initialization, design, implementation, evaluation and control does not encourage direct communication and effective cooperation of the parties involved.

For all the above, where possible, it is proposed to adopt a flexible approach to project implementation. Implementation takes place in iterative cycles, where each of them aims to cover the most important outstanding requirements, in a specific timeline (e.g. some weeks). Also, in each cycle there is a check and feedback on the results from the involved groups. The process of intermediate checks in each cycle ensures the timely identification of any problems, the planning of corrective actions, the reprioritisation of requirements based on the evolution of implementation and the identification of residual requirements, thus affecting the initial planning and planning of project implementation. At the beginning of each cycle the involved groups agree on the scope to be implemented in the next cycle until after repetitions, all important requirements are adequately met. This process facilitates the integration of modifications due to the changing external environment, a better understanding and analysis of the issue to be resolved and systematic cooperation between stakeholders. Based on this approach, the final solution is composed of individual distinct functional parts, each covering a subset of operational requirements.

Benefits of using

(see mosaico)

It overcomes disadvantages related to traditional project management methodologies, such as the waterfall methodology.
It reduces the complexity of the project by dividing it into incremental iterations with well-defined deliverables, allowing the team to receive targeted feedback on each change and integrate it into future plans.
It allows clear priorities to be set in the short and medium term.
It promotes the adaptation and continuous improvement of procedures and working methods.
It sets short periods for each delivery, promoting timely and continuous delivery of software that can be evaluated by stakeholders.
It ensures the early detection of failures in the development process and their rapid resolution at less risk and cost.
It improves communication and maximizes cooperation between all stakeholders.

Institutional framework

–

Good practices

It will be taken from the Mosaic.

Tools