Our Kaban visual system

An improved method to work better

We created our method as a way to implement Kanban principles with Scrum and Agile techniques. To help us improve our processes for higher performance and to build effective implementation’s planning.

This lean process allows us to achieve better performance and to plan an efficient development and testing implementation of our software.

This method allows us to visualise the status of each task with the work in progress. The main objective is to prevent potential problems and implement incremental improvements.

Our method allows us to continually improve our workflows, reduce cycle times by supporting the completion of a job in progress before starting a new one, provide our customers with frequent and early feedback, deliver on time with greater predictability and to minimise the cost of delays.

The phases

Current – Analysis – Development – Testing – Deployment – Delivery

The workflows map the implementation process.
Visually, different columns and rows allow teams to categorise their processes to cover the workflow and quality assurance they envisage.
All project participants (team members, clients, project managers) can easily see the status of each tasks and work in progress.

Current phase

The current phase contains all the tasks required to develop an application.
These tasks are divided into different categories like Story tasks, Feature tasks, Bugs and Subtasks.

Analysis phase

The analysis phase is managed by the project manager and the lead developers. This phase enables us to check that there are no gaps or inaccuracies in the specifications of a task.

Development phase

The development phase starts when a task has passed the analysis phase. The most complex tasks are assigned to our lead developers.

The rest of the tasks are handled by our development team according to the requirements (back-end, front-end, design, other) under the supervision of the senior developer and the project manager.

Testing phase

Our testing phase consists of two sub-phases: code review and front-end testing.

Code review
Once a task has been selected for testing, a senior developer reviews its code and gives feedback to the developer(s). 

Front-end testing
When deploying to the test server, the project manager is notified that he can test the functionality of each task.

Deployment phase

This deployment phase is the process of installing, configuring and activating the application that makes the software system available for use.

Delivery phase

This phase is executed by a specific tester who receives a checklist of all the scenarios and tests the interfaces to ensure that each scenario has been implemented according to the requirements. 

As we value our team and individualities, our method emphasises respect for the roles and responsibilities of each team member.