It is surprising that so many websites still incorrectly implement the basic, rudimentary and essential elements of login and password functionality. Implementing a slick, secure and stable process really should be straightforward for any development team. However, judging by how poorly some websites continue to do it, it may not be as simple as first envisaged.

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.

Websites should always be designed and developed to work in the fluid environment of continuously evolving devices and channels, whether "responsively" designed or otherwise. For many years it has been the web designers and web developers that have been breaking the inherently responsive nature of the web by placing their designs within fixed containers.

We often get asked whether Magnolia's Standard Templating Kit is the best way to go when planning out a new Magnolia project. In this article we discuss some of the pros and cons associated with the STK to help you decide whether it fits the requirements of your Magnolia project.

Responsive website design can be simply described as an approach to design by which the intent is to provide the most optimal viewing experience on all devices. Elaborated, this includes ease-of-use whereby there is minimal user involvement, by way of resizing, panning and scrolling, across a wide array of devices (from personal computers to mobile devices).

For the past few months a continuous talking point in the web development arena has been the controversial new EU online privacy legislation affecting use of cookies. Just one day before the new directive was to be enforced, the ICO changed their official advice.

We hear a lot these days about customer engagement, profiling and content targeting, but with very little groundwork being done first to define who and what we mean by a Customer. Without understanding the limitations of the underlying techniques, it's easy to jump to the wrong conclusions.