In the November/December issue of IEEE Software the Voice of Evidence addresses Test Driven Development (TDD). Researcher Forrest Shull and several colleagues have reviewed the research literature on TDD. They posed three questions: Does TDD improve delivered quality? Does TDD improve internal code quality? Does TDD improve productivity? They found…
Requirements are highly controversial in software development. There is always too much and too little requirements. They are often blamed for project failure or seen as required for project success. I have seen cases where there were too detailed and complex requirements. The result was that everyone worked around the…
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…
[bibshow]
Does personality matter in pair programming? According to this Norwegian study – http://www.computer.org/portal/web/csdl/doi/10.1109/TSE.2009.41 – it does not. [bibcite key=”citeulike:9782651″] So what does matter? Experience and expertise.
[/bibshow]
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?
While there has been a bit of research detailling the advantages of agile software development not that much systematic work has been done to find the issues arising from using the agile paradigm. So, what are the issues with agile software development? In “A Comparison of Issues and Advantages in…
When you review documents, test applications etc it is very easy to get stuck on shallow problems and give comments which are not really helpful for the developers. Using checklists can be one way to force yourself to look beyond the most obvious things. I recently found two good checklists/protocols.
Daniel Markham has written a rant about how many people feel that Agile has “ruined their lives”. Basically, he is saying that to these people Agile is just a new name for snake oil. Agile coaches are nothing but scamsters. The books they write are nothing but positively biased stories…
