Classes of service divides tasks in different aspects. Every kind of work can be classified.
Some tasks get solved if you code a requirements, others will be solved by migrating data or exporting them into an specific format. Different kinds of work also have different priorities to each other. So, the classes of service span parallel flows over one Kanban board. (more…)
This blogpost describes the Work In Progress (WIP) limits of the Kanban process and forms one of the five key values, which are as follows: (more…)
How I conquered the European Human Resources hot spotLast month I spontaneously visited the HR conference “Zukunft Personal 2016“ in Cologne, which is regarded as one of the most innovative Human Resources conferences in Europe. More than 730 exhibitors and 16.000 visitors in three days – and I was in the thick of things. I visited the conference on its last day. (more…)
The coordination of the prioritisation of the tasks in a project may involve many parties: the development team, which is obvious in our case, but also sales, marketing, finance, external partners and so on. (more…)
Every month there is something new in the JavaScript world, some new fancy technologies, which might be the next great thing. It’s important to get the latest knowledge of the web development.
Otherwise you will be obsolete after some years. (more…)
A continuous delivery rhythm is a very popular and important factor in agile software development projects. Most of the development methods (such as SCRUM) use fixed delivery rhythms (so called “iterations”) of two weeks or so. (more…)
The most obvious practice to coordinate your team is to use the physical Kanban board itself. WIP limits and visual information (service class, due date, …) will help to indicate whether new tasks can be pulled and what tasks to pull. An alternative or addition to the physical board can be an electronic/online tool (e.g. kanbanery.com). An online board can do more things than a physical board, for example creating metrics and reports for the management. (more…)
In this article let me give you some tips on visualizing the value chain of the workflow using Kanban. In order to do so, we have to keep in mind that Kanban does not seek to install a new workflow, neither does it change job titles, roles, responsibilities or specific work practices. (more…)
Kaizen is a Japanese word with the meaning of „continuous improvement“. It contains the two Japanese characters „kai“ which means „change“ and „zen“ which means „good“.
Source: http://www.digite.com/blog/wp-content/uploads/2016/02/Prioritization.png
Let’s take a moment to visualise the success. Hard, isn’t it? In order to do such thing, David J. Anderson gives us a helping hand and writes about the real-life example. The story of Dragos Dumitru will show us how to follow the path of Kanban method and shift from the worst to one of the best teams in the Microsoft group. (more…)