Publicly available solutions are ubiquitous. These products can fill a team’s need so well that it is tempted to build its software from a mélange of packages sown together. A mishmash of libraries is an appealing approach. Yet, a unit is better off avoiding that method. Instead of the Frankenstein technique, a group should build the most impactful parts of its software to gain otherwise unattainable knowledge. When a team builds a consequential piece of its software, the unit acquires knowledge, which can be used to make well-informed estimations. A squad makes enlightened guesses when it has the expertise acquired…...
A Team Should Build the Most Impactful Parts of Its Software
3 min read
