Customised IT solutions that creates value
We have extensive experience in the application development, integration and project management of business critical and complex IT systems for a wide range of public institutions as well as some of Denmark’s leading and largest private companies. These are all dependent on:
- High quality
- Data security
Systematic can ensure the right sparring when application developing. We challenge the decisions, undertake continuous reviews and always focus on delivering that which creates the most value and not just what was originally agreed. We co-operate with you, because we want to create succes together with you.
We break projects into smaller parts and make regular deliveries to the customer, which makes it possible to reprioritise and adapt during the process.
Agile Development at a fixed price
How do you combine a fixed price and agile development in IT projects?
As a customer you often need to limit your risks in IT development using fixed price, and you need to be able to develop a solution over time to ensure that it fulfills your needs.
In Systematic, we often look at IT development projects like this; they run from time A to time B. In this project scope we need to monitor the budget and the needs that must be fulfilled. Furthermore, we need to cooperate with third parties during the project period in order to deliver.
On this level of the project we use traditional methodologies like PRINCE2 and PMI to monitor and manage the project.
At the lower level we use agile methodologies like Scrum to coordinate and adjust the project and the solution with the customer as we go along. We also coordinate with the customer on a daily basis in morning meetings.
Hence, we combine traditional project management methods and agile methods in order to ensure that our solution is able to fulfill the customer’s original needs within the boundaries of a fixed budget.
Agile Development at a fixed price
How we combine traditional Project Management with Agile Development
We continually optimise our development process, which means we can guarantee our customers that we will maintain flexibility and the ability to meet our customers’ demands before it is too late.
Staircase - Systematic's software development process
The software development process invented and discovered over the years at Systematic is called Staircase. The purpose of the Staircase-process is to enable us to develop valuable software in a controlled, efficient, repeatable and low-risk way.
Our software development process proceeds in this way; we start by looking at the systems functionality as a big blob. We divide the functionality into smaller bits and each of these bits is called a feature. A feature is a lump of functionality with a name and a meaning, and is something witch a customer is willing to pay for. Each feature usually takes from 100-300 hours of work to implement.
A features lifecycle is like a line. We start from a state called ‘initial’, which is the starting point. Here we got a name for the feature and perhaps some idea of what the requirements are, but probably not much more than that. The keyword is risk reduction.
At the end we are in a state called ‘done’. The feature is fully implemented and integrated into the system and the system the shippable with new functionality on it.
The work proceeds in two phases – the first phase is called the clarification phase. This is where all the stakeholders for the feature discuss and agree on what the feature means, what its risks are, how to implement it, how to test it and how to integrate it into the completed system.
At some point we are ready to start implementing – the second phase is called the implementation phase and this is where we build the feature and create value. This phase is divided into small micro projects, which we call stories. Each story is the responsibility of one or two programmers. They execute the stories by following a check list, which makes sure that they keep test, quality coding etc. in mind. When they execute the check list they execute the story. A story is usually something of the order of 10-40 hours of work.
A story is a closure in the sense that when a story is done, not only have we implemented something new, but we have tested, verified and integrated it. At the lifecycle line a feature is a closure when the feature is done and we have added new value to the system.
The feature decomposition feeds directly into our overall project planning process, while the stories are spring backlog items and feeds directly into scrum – meaning that we can use scrum to drive the implementation phase of features.
The name of our software development process is Staircase. A Staircase is an excellent way of getting safely and efficiently from one floor to another.
Using this method gives a number of advantages – predictability, efficiency, manoeuvrability or agility. It’s all about providing as much value as possible to the customer.
The software development process iused in Systematic is called Staircase. The method gives our customers predictability in the delivery, increased efficiency and an agile partner.
Staircase has contributed to Systematic’s certification at CMMI Level 5, and is one of the reasons we can call ourselves an agile software house. One of the main advantages with Staircase is that it helps us delivery the most valuable solution to our customers.