We all want to be better at what we do, so we climb the stairs of maturity, but sometimes the steps don’t need to new levels of quality and productivity. What are the factors that hold us back from gaining higher and higher levels of success?
The foolish man builds his house on loose sand but the rains and the winds will crash it. (Matthew 7:24-27) Things have not changed that much in the last two thousand years. Technical debt remains a major challenge for software development teams.
[bibshow] Software development success is organization dependent. Which organizations are successful in developing and delivering software? Which projects will be successful? That is a crucial question in an industry with an annual turnover of over 400 billion USD and only a 50% success rate. [bibcite key=”citeulike:4540645″] Is it enough to…
Software effort estimation is an important part of the daily lives of many software professionals. I have joined the #noestimates debate on Twitter because there is a lot to learn from a discussion on estimates. I’m not ready to fully abandon estimates but I am interested in discussing where, when…
Legacy Code… We all love to hate it. We all have it. Some of us keeps creating it. How do you deal with it once you have it? Sometimes we find problems with it. But then, what do we do? A colleague at Capgemini, Paul Oldfield, suggested I should read…
In my inbox today I found a link to an article about what constitutes success and failure in software development projects from a supplier perspective. While the authors were able to find three project success criteria from their systematic literature review they were unable to find failure criteria… The three…
Two days ago, I wrote about the kind of adversarial relationship possibly implicit in using requirements. I have started looking for research on what that relationship looks like and one of the first articles I came up with was a recent (April 2011) systematic literature review on success factors for…
Applications used to be monolithic, end-to-end do it all systems. Developing these mamooths often failed and still continues to fail today. Enter the idea of software ecosystems. For instance, Jan Bosch wrote about the concept in this article from 2009. Software systems are increasingly not developed any more. They are…
http://www.mendeley.com/research/extreme-programming-agile-processes-software-engineering/ In this article the authorsn suggests that many of the problems associated with changes in agile software development can be managed by treating the changes as ‘first-class objects’. Sounds complicated to me. What do you think?
