Our software package exists of multiple modules, each with their own functionalities, and we keep working on new modules to be released. New modules are rather big projects (can take more than a year to develop) and are managed by the Product Owner Organisation. This process starts with gathering information from our internal stakeholders, usually cost engineers with a lot of experience in the field.
After capturing the requirements we have to define specifications, set up acceptance criteria and create provisional screens of how the module should look like. Then we go back to the stakeholders to validate the specification and dive even deeper into the details. This iterative process makes sure that we can deliver a product that is of added value to our clients.
When we are fully finished with the specification, it is our job to make sure that the software engineers are able to implement this as efficient as possible. We do this by breaking up the specification into small parts and assign these parts to developers in the sprint planning. After every sprint a new part of the module is finished and we are able to see a demo version of that. By working in sprints we are, again, able to work in an iterative way.
As I said earlier, we also work on specific custom implementations for clients. As each client has different needs, we develop specific solutions to meet those needs. I really like these projects, since there is a lot of direct interaction with the client.
What I really like about my role and about working at Cost Engineering is that I can cooperate with both sides of the company and that I can actually learn by doing! Moreover, I can develop my skills further with the provided trainings, for example a Design Thinking course. I look forward to improve Cleopatra Enterprise even further in the future!
Interested in working at Cost Engineering? See our available jobs!