Technical suitability

Technical sustainability refers to the long-term use of systems and the ability to develop them in line with changing circumstances and requirements. Every project should cover at least the next 5–10 years, as further development is an important part of our customers’ business. Software maintenance becomes much more difficult, and further developments time consuming and costly, if the future is not considered from the very beginning.

Software developers need, therefore, to be able and willing to think about the further development of technologies and architecture in the coming years. These skills usually come with experience, after you have first tried to maintain a poor-quality code by yourself and learnt to leave the code in better shape than it was when you started.

It is also important that customers are encouraged to improve development tools and methods, so that technical debt and poor quality code do not end up in version control and production. Among other things, this includes extensive automated testing of the code, as well as inspections involving the entire team, where the problem areas are genuinely highlighted. These measures can improve quality, reduce regression and speed up production, in other ways ultimately save mental resources, time and money.

Human sustainability refers to the continuous, life-long development and wellbeing of the individual and lays the foundations for four other areas. Satisfied, committed and skilled employees enable the execution of technically sustainable and, therefore, cost-effective solutions in the long term. When individuals are competent and well-trained, they are well equipped to execute technical solutions that enable the competitiveness of the customer companies, the surrounding society and the future of the environment. Social sustainability, therefore, refers to the social responsibility of software development, and ecological sustainability focuses on minimising its climate impact.

By paying special attention to these areas of sustainable software development, we can better ensure the success and high customer satisfaction of projects.

Tuntuuko, että...

 …teidän softakehitystiimissä sekä palautteen antaminen että vastaanottaminen on vaikeaa?

Tilaa ilmainen miniopas tilanteen ratkaisemiseksi tästä:

    Kun tilaat oppaan, liityt samalla uutiskirjeemme tilaajaksi, ja saat lisää inhimillisen johtamisen vinkkejä. Voit poistua listalta koska vain.

    the eNPS calculation is based on the Employee Net Promoter Score formula developed by Fred Reichheld, which was originally used to study the customer experience and customer satisfaction of companies. Lately, it has also been used to research employee satisfaction (e as in employee + NPS).

    This is how the calculation is performed.

    We ask our employees once a year, “How likely are you to recommend your workplace to friends or acquaintances on a scale of 0 to 10?” Then we ask for clarification with an open question: “Why did you submit this score?”.

    Those who submit a score of 9 or 10 are called promoters. Those who submit a score from 0 to 6 are called detractors.

    The eNPS result is calculated by subtracting the relative percentage of detractors from the relative percentage of promoters. Other answers are allocated a score of 0.

    The calculation results can be anything from -100 to +100. Results between +10 and +30 are considered to be good, and results above +50 are considered to be excellent.