Agile Waterfall Model
Customized projects thanks to the "Agile Waterfall Model"
We have developed our own customised project methodology for project management. It has convinced our clients for years and is a foundation of our successful cooperation. The BIG.Cube project approach is based on our conviction that premium consultancy should not depend on individuals. Rather, it should be based on standardised procedures and customized projects. All this is reflected in our project approach: Agile Waterfall Model with Scrumban.
For us, it is ultimately crucial that the project is successful and our client is satisfied. With the BIG.Cube project approach, we achieve these goals.
The Best of 3 Worlds
Over the long time that we have been doing projects together with our employees, we have experienced many different project approaches. That’s why we know the best of them and make use of the strengths of the best 3 project management methods in our “Agile Waterfall Model with Scrumban”:
Approach and Important Roles
The Scrum Master
The Feature Officers
In addition, we use a role of the Kanban model: the Feature Officers. They are, as the name suggests, responsible for individual features and have a very detailed view of “their” features. They divide the features into small backlog items for the developer employees and are available to answer questions.
The Business Analysts
A third important role in the BIG.Cube project approach falls to our Business Analysts. In order to be able to give our clients as accurate an impression as possible of the effort and costs of individual features at a very early stage, our team of Business Analysts starts by analysing all known requirements. Their analysis and evaluation is then used by our clients to flexibly change the prioritisation and schedule of individual features.
3 Success Factors
Maximum Budget Protection
The project budget is saved if the right employee always works on the right tasks. If someone is not currently working on a specific feature or backlog item, then there are no costs for the project.
Due to the flexible project approach, it is possible to adapt requirements at any time. This simultaneously increases the quality of the technical specification, as it is constantly being improved.
Stable Test Environment
Our strict requirement that nothing may be changed after a feature has been tested, as well as during a live run, means that a stable test environment prevails at all times.
With Standardisation to Project Success
Due to the standardised and consistent BIG.Cube project approach, our employees only have an extremely short familiarisation period in new projects. This allows our employees to switch quickly and flexibly between different projects. Therefore, you benefit from the Agile Waterfall Model with Scrumban, because the right BIG.Cube employees with the right skills always work on the right task.