‘Agile’ has become an indispensable term in the world of software development. Although Scrum is likely to be the most heard-of method, Triggre has chosen to work with Kanban instead, as the latter adopts a more technical approach which allows us to serve our non-technical users better. A paradox? Not so much. Allow us to explain.
Building applications with Triggre is like picking a new car
Do you remember when you built your last car? Most likely, you never did. Instead, you simply went to the dealer, picked a model, decided whether you wanted the 3-door or the 5-door version, picked a color and perhaps added a sunroof or air conditioning. This is in no way a technical process; you do not have to think about how the crankshaft connects to the pistons or at which rate the spark plugs need to fire.
Similarly, the process of creating software with Triggre is creative rather than technical. For users, it is simple and fun. In the background, however, our development team ensures that everything has been organized smoothly in terms of technology. In other words: we need a highly technical behind-the-scenes approach to avoid bothering our users with complex programming language and specifics.
Kanban: the sky is the limit
As Scrum requires the team to express all new features in user stories, it is not suitable for Triggre’s goals. After all, we aim to support virtually all user stories, including the ones that our (new) customers will come up with tomorrow. Kanban is the right approach to achieve this, and it also allows us to perform tasks that cannot be captured in Scrum’s traditional user stories – for example, making major technical improvements.
More freedom, customization, and responsibility
Like Scrum, Kanban provides a long list of tasks, or a backlog of features that need to be developed. However, while Scrum divides these in set intervals, Kanban allows developers much more freedom: they can take on a task whenever they are ready to do so.
Consequently, the workflow is more constant, smooth, and customized. Of course, this development method requires highly responsible developers with great communication skills who do not need to hold formal meetings in rigidly fixed intervals, as is common with Scrum. Luckily, that is not a problem for Triggre’s experienced, enthusiastic developers!
Author: Antoine Talen