In Part One of this article, we introduced the idea of using Kanban for software development projects. In this second part, we work through a detailed example of how the Kanban process might be followed by a software development team during a typical week.

There are numerous anecdotes on the Internet parading the disparity between those who work for creative agencies and those who are pure software developers. You’d be hard-pushed to find two more different kinds of people. It may be a marriage of inconvenience, but in this world of ubiquitous web and mobile apps, techies and designers need each other. Developers ignore this at their peril.

Kanban was invented by Taiichi Ohno as a solution for making Toyota’s manufacturing processes more efficient, but can equally be applied to software development projects. In this two part article we explain the concepts behind Kanban and how it works in practice on a typical software or web development project.

At Priocept we believe that a deep understanding of software engineering is critical to the success of any digital product development, e-commerce, content management or mobile project. So in this article, we go back to basics to try to explain; what exactly is software engineering? And we look at why is there so much software development going on in the world that does not apply a proper engineering philosophy.