developer productivity

A core tenet of many modern Agile approaches is estimating work effort using story points or abstract units instead of time estimates. Proponents argue points are more accurate because they supposedly account for variability in developer productivity. But this concept is deeply flawed. Points are always eventually deconstructed into dates on a calendar for planning purposes. No business can operate solely in an abstract point system detached from real-world time constraints. [Read More]

It’s a common scenario in software development: a new project is starting up, and the team is faced with the decision of which languages and tools to use. While it might seem like a good idea to let every team choose their own technologies, the long-term costs of this approach can be significant. One of the main drawbacks of letting every team choose their own languages and tools is the lack of flexibility it creates within the organization. [Read More]