No Fear of Complexity

The Accurate Assessment of Our Capabilities

We are a small company and must realistically evaluate our possibilities – our capacities, the technologies used, and the necessary expertise.

Already during the inquiry and initial discussion, we analyze whether a project is a good fit for us. Does it have the right size? How complex are the requirements? Which technologies do we need to implement it? Our estimates have always been correct so far, as there has not been a project where we "fell flat".

How complex a project is can only be properly assessed with foresight and the necessary expertise. Doing this in advance is important!

Delivering functional, usable software on time, with which the customer is satisfied, is not guaranteed (though one might think so). According to a study on software quality published on Wikipedia, in Germany during the period 2002-2004, only about 30% of all developed software was delivered on time and functional. 18% of all projects failed completely, 56% exceeded costs, and 84% missed the deadline. We have also worked with clients who came to us with failed or aborted projects that the programmer could not complete. A frustrating experience for the client and certainly also for the developer, who apparently misjudged his skills and capabilities!

Questions we ask ourselves to accurately assess our capacities:

• How many projects can we handle simultaneously with the necessary care?
• Can we meet the desired schedules?
• How complex is the project, and how much new learning is required?
• How many technologies can we use at the same time, have the necessary expertise available, and refresh it whenever necessary?

Questions we ask to accurately assess the client's capacities:

Our clients are small and medium-sized businesses, whose budgets are often limited. Therefore, we first check the framework set by the budget regarding requirements and the target goal.

• Can we take on the project within this budget and meet the requirements?
• Are the personnel capacities available on the client's side?
• Is there a point of contact for our project who is available at all times and can make or influence decisions? Someone who constantly informs themselves about the progress and participates, e.g., through testing?

Requirements for software or a website over many years of operation:

1. Functionality
   The software does what it is supposed to do. Technical updates are necessary and are implemented from time to time.
2. User guidance and usability:
   The user understands the workflows and can operate them. Modernizations are occasionally necessary and are implemented.
3. Comprehensibility and depth of understanding:
   Both the client and we as developers can still understand after years what we have solved and why. We keep the project lean and understandable. Features that have become unnecessary over time are removed.

What we do to control complexity:

• Processes and checklists
• Documentation and wiki
• Version control system
• Ticket system and task management
• Test environment as a development environment
• Active and responsible project and customer communication
• Defining milestones and conducting interim reviews