Dashboard of work in progress Dashboard of work in progress

a tool to Kanbanize the release process. Release management process must be adapted when IT organizations scale up to avoid discontinuity at the release flow and to preserve the software quality. This paper reports on means to improve the release process in a large-scale project. It discusses the rationale behind adopting Kanban principles for release management, how to implement these principles within a transitional approach, and what are the benefits. The paper discusses the post-transitional product to assess the status of the outcomes.

The testing activity of the source code within an isolated branch must be followed by the release of that code to the end user. Prior to the release of a software product, release engineers must perform a list of activities: for examples, planning and coordination, source code merging, integration, and build construction. Regardless of the model of the software process adopted, there is often variability in release effectiveness.

Releasing source code for one Application/Team is simpler than releasing code from a large and complex organization. Large organizations have dedicated teams to manage the release cycle. Regardless of the software process model, the releases of software products must be done one at a time to minimize system failure and customer impact.

Release manager is a central role within the organization. As an “Air Traffic Control lead”, the challenge is to know where the check-ins are at any given time and where each they will be landing. New versions need to keep coming in an oiled release flow for feeding the value to the customers.

Observing the anatomic constraint of the mainline code stream, pipeline with one release at time, drives the hypothesis of using Kanban ideas to resolve the release problems. Kanban focuses on visualizing the workflow of releases, limiting the work in progress, and controlling the Lead Time.


Research Area

Process Modeling

How to conceptualize a software process model that fit the size of your organization and its culture? and how to analyze the breakdown list of activities in order to identify potential improvements?
Learn more ...


Software Release Engineering

What kind of activities the Release Engineering is responsible for? and how we can support, with tools and practices, modern organizations to perform effective software releases?
Learn more ...

Empirical Soft. Engineering

We also focus on Software Team Dynamics through Empirical Studies of coordination and congruence between software team' members.
Learn more...