A project at JAM-IT

Do you want JAM-IT to build an application for you? Or are you simply curious how an IT project works? In this article we explain how we approach a project.

A great deal happens between a first conversation and the delivery of an application. From planning and sprints to testing and demos: we are often asked how this process fits together. We think it is important to be transparent, so we will explain everything before we start. But until then (or as a reference), you can read all about our way of working below.

The first conversation

Before we get to work, we first sit down with you. First of all we want to talk about the application itself. What are you looking for? What does the application need to do? And what other requirements do you have? But we go deeper than that. During this conversation we try to build as clear a picture as possible of how your business fits together and which problem the application should solve. With that information we can advise you properly on the right software.

We also explain exactly what we do and how we can best help you. We map out the requirements and link them to functionality. Together, if you like, we create a domain model to record which entities exist within the application and how they relate to each other. We can also advise you on the consequences of certain choices (think of the application's performance, costs, and so on). That produces a first concept of the application.

Proof of concept (POC)

Are you unsure whether a particular piece of functionality is technically possible? Then we carry out a proof of concept: a small, simplified version of the functionality. With it we can demonstrate that it works and fits the requirements, so you know for sure the project will be feasible.

SCRUM: planning and roles

Once the requirements have been mapped out, we draw up a plan together. Starting with the deadline: when do you want to start using the application? All the tasks are then planned into short sprints. These tasks are called stories. We work with the scrum method, which lets us work very flexibly and adapt every project as required.

That also involves various roles that we divide between us. Within our team there is a scrum master who guards the process and the developers who build the application. From your team we need a product owner, who says which stories are picked up when, and a tester, who tests the functionality before it goes live. Incidentally, one person can also fill several roles, so the team does not necessarily have to be large.

Overview of a sprint

A sprint is a set period (one or two weeks, for example) in which we work on a number of the application's stories. Each story goes through various stages: development, review, testing and done. In our project tracking tool, Jira, you can see the status of the stories in the sprint at any moment.

During the first stage we work on developing the functionality. When the developer is finished, it goes to another developer for review. They check whether everything is technically sound before it moves on to the next stage.

The functionality then goes to the test environment. Here you see what the application looks like and how everything works. The tester now decides whether the functionality is approved. If the functionality does not yet work properly, it is put back into the development stage.

Because not all stakeholders are always closely involved in the development process, we give a demonstration regularly. That way everyone can see what has been built and how the application works. We use it to gather feedback and adjust where necessary.

Finally, the product owner decides whether the functionality can be pushed to the production environment. In other words: it goes live!

And then?

Once the application has been delivered exactly as required, we move from the development phase to the maintenance phase. We carry out security updates, keep the application up to date and help you if there are problems with a piece of functionality. Do you have new requirements? Then we get to work for you!