Measured by other areas of engineering, software development is still a rather young discipline, subjected to continuous change and innovation.
Subsequently, it is not unusual for all project stakeholders, customers and development companies alike, to share a lack of basic experience. They also share an absence of established and standardized methods that have been proven successful across a number of different projects.
Disappointments, unplanned delays or high follow-up costs are just a few of the undesirable but often inevitable consequences.
At the same time, there are two undeniable truths: People make mistakes, and requirements change.
Countering this and reducing the risks requires a systematic approach that helps to discover potential errors early. This minimizes the effects on the user and to allow the careful and controlled integration of changes to the application as well as to the process.
To us, this also means integrating our customers into the development process wherever possible. You only want to pay for what you need; we want to find the solution that is optimal for you. We offer a broad variety of communication channels that enable reaching this goal.
The Kreios team relies on agile methods, particularly on a pragmatic but well-balanced combination of SCRUM and traditional system analysis.
Find the methods centered on these principles listed below.
- Individuals and interactions over processes and tools. Although well-defined development processes and high-end developer tools are important, the qualification of the contributors to a project and the efficient communication with each other are significantly more important.
- Working software over comprehensive documentation. Well-written documentation can be helpful and is essential for most projects, but it is always the finished product that represents the actual goal of the development process.
- Customer collaboration over contract negotiation. A contract determines the fundamentals of a cooperation and thereby defines the basic parameters – but not necessarily the specifics – of future developments.
- Responding to change over following a plan. In the course of a development project, many requirements and surrounding conditions change, just like the understanding of the problem. The team needs to be able to react rapidly on such changes without risking a loss of structure, control or traceability.
"Individuals and interactions over processes and tools". To us, this also means preferring flexible solutions such as Confluence over static documents.
Instead of devoting energy to tools and version control, we want to focus on content. While providing just such a lightweight framework, our wiki serves as a communication platform that facilitates collaboration not only within the team, but also with you, our customer. This way, meeting notes, requirement documents and all other project information are never more than a login away.
Internally, we use project management tools like JIRA to track and organize our tasks. These do not only provide project management support, but also facilitate communication within the team.
Among other things, you can, as our customer, use them to report bugs, initiate change requests and collaborate with us in organizing our backlog. By granting you access to some of our project management tools, we enable you to impact the development priorities and help steer the project into the right direction. If not, you can just sit back, relax and watch it happen.