Republicii Street, No. 9, TM, Romania +40-256-201279
Leadership, Tech

A study in collaboration with Oxford University provides extra details about IT software projects. The productivity paradox has a simple solution, according to this study. There is no need for stagnation – the customers can enjoy the increasing computer power. The secret stands in proper, timely testing.

Mapping out software projects in layman terms

The source article comes from a company specializing in software testing. Even so, their description applies to every IT project. Usually, teams that include consultants, developers and testers handle such projects. We structure our teams this way.

The scenario presents the client’s representative as “Mr. Requirements”. In their worst case scenario, Mr. Requirements uses its own words to describe the end result. This triggers a series of “meetings, workshops, presentations”. The Analyst prepares for translating the project into universal models. The Developer should receive this translation and know what he has to do.

However, as we mentioned, we are looking at a “what can go wrong, it does” version. The Developer doesn’t understand the current description of the project, either. (Rest assured, at LASTING Software this doesn’t happen, as our employees are in sync). But let’s humor this example – and see where it goes.

The software project unravels to the point where the tester comes in. Too much optimism, lack of strategy or other reasons manage to minimize the tester’s key role in IT projects. Thus, this point is belated in the timeline. Some stages need to repeat themselves, once the tester identifies what went wrong. The better solution means better timing. Involve the tester earlier on, when those stages are taking place for the first time – for great results.


The purpose and the way

The purpose is for the IT Projects to “spend less time; deliver more value for less money”. The way to get this is by making sure all the people involved in the project speak the same language. Standardize communications, train team members to understand each other and coordinate their work. These are mandatory.

A good strategy is yet another important thing. Sometimes the client sees this differently. Some come up with their own management style. This may disrupt the (validated) team practices. From case to case, there is an adjustment process taking place. Depending on how the two sides get on the same page (or not), the project runs more or less efficiently.

In view of those of the above, the article’s authors suggest that the missing link is the tester. Involve testers in the IT projects at the right moment. Here is the low-cost, efficient solution. The key for smooth development, deployments and seamless implementations is here.




Businesses deliver globally, and digital is the new-gen universal language. In sync, the workforce becomes increasingly dispersed. The horizons opened up. Now it’s just a matter of supply meeting the demand, in international software human resources.

An idea becomes a viable product or prototype in one place. The resulting product manufactures in several points around the world. Thus, producing closer to the customers decreases delivery costs.

Software engineering is free from geographical constraints. A solid digital infrastructure and local talents enable great achievements to come from any corner of the planet.

The businesses follow skills and cost savings. Browsing the local resources turned into browsing the globe. New business models are in practice. Each company just needs to find the perfect fit for its own operations.


The modern business models


Workforce engagement models take two classical forms. A company can decide to “organize the remote delivery of software development services”. Thus, it may choose the captive subsidiary option. This better suits large companies and conglomerates. Allotting core functions and critical activities to new subsidiaries is a common practice.

The other model is third-party outsourcing. Suited mostly to projects having clear requirements and deliverables, outsourcing is extremely popular. Maintenance and support can also benefit from outsourcing. In this case, we are talking about a type of dedicated development center.

IBM features a detailed article on the right choice between captive and outsourcing. Their presentation is backed by figures and studies. You may take a look here and get inspired on what your next step should be, BP-wise.



Our software engineers have had the occasion to test the strengths and weaknesses of containerization platforms themselves. When considering which platform works best for a team, the project in cause fuels the decision. Different projects may require different tools and consequently a certain suitable platform. What we need to achieve with the container-building tool matters most.

We recommend an article that compares Kubernetes and Docker in a fair, balanced manner. In the author’s own words “Kubernetes vs. Docker is not an easy comparison”. However, by going through this post, you may well form an idea of which platform suits your needs.

The TechnologyAdvice article is here – take a look.  

Image credit: source article



The modern economy favors software offshoring and outsourcing. Rich countries deindustrialize and a wave of structural transformation ripples globally. Therefore, companies reshape their boundaries. Consequently, the desire to increase the quality of services and to save costs materializes in outsourcing partnerships.

Software development outsourcing follows the trend

Externalizing the software development needs is a common business practice. While it is not deindustrialization, it is a form of process acceleration. The HQ staff design and coordinate, and the third-party handles the software engineering processes.

Get the overall image from this VoxDev comprehensive source-article. You will find out what is the forecast, as well as what are the biggest challenges the business world is facing now. You will be able to put software outsourcing into context.