40 years after the NATO Conference on Software Engineering, Tom DeMarco paused to reflect on the discipline's evolution, wondering whether the metrics orientation he championed has distracted from the real point of computing: "transformation, creating software that changes the world." Is his earlier advice valid, though? "No", he said, in Software Engineering: An Idea Whose Time Has Come and Gone?
Recently the Scrum Alliance asked a number of user groups to sign a licensing agreement. This turned out be to a big public relations mistake in the Scrum Community. In cleaning from this mistake the Scrum Alliance issued a new policy, hired Cory Foy as Community Organizer and promised to listen to feedback in the future. Will this be succesful?
Today a Scrum User Group closed shop, in response to a Scrum Alliance request "to sign ... a licensing document for a logo they created for Orlando Scrum users group." Community reaction varies widely. Despite clarification from the SA's managing director, it is unclear what, if anything, this trademark application will mean for existing groups.
Looking back at the year that is coming to its conclusion, we wanted to have a retrospective and find out which were the most read news and exclusive content items during 2008. We compiled a list containing top 5 news for each community and top 3 exclusive content items for each type: articles, interviews and presentations. This list considers the number of unique readers for each news.
James Shore has declared agile to be in decline. He cites the many teams doing 'sprints' and stand-up meetings, without adopting any of the technical practices necessary to produce high-quality software over the long-haul. In his estimation, this has led to thousands of Scrum teams doing agile so poorly that they will almost certainly fail, and possibly take the agile movement with them.
In this presentation filmed during Agile 2008, Jim McCarthy talks about 11 commitments team members should adhere to if they want to achieve a state of shared vision. Such a state empowers a team to reach their full potential and ultimately attain greatness.
Jacky Li of InfoQ China spoke with Martin Fowler during ThoughtWorks' AgileChina conference. In this print interview, Martin Fowler talked about Scrum certification and the future of Agile.
According to Clay Shirky, the success key for social software is “a brutally simple mental model [...] shared by all users”. Referring to it as Shirky’s law, Michael Nielsen analyzes why programmers often fail to obey it. His arguments as well as the discussion that has followed provide interesting insights into pitfalls that need to be avoided for building successful social applications.
In this presentation filmed during QCon London 2007, Martin Fowler and Dan North talk about the communication gap existing between the developers and the customers or users. Closing this gap is extremely important in order to create successful software.
Declan Whelan wrote a thought-provoking blog citing an idea he learned from Mishkin Berteig about an (unspoken) principle behind successful Agile teams: truthfulness. The idea is simple: without individuals being honest and open, most agile practices will not work.
In a recent post, Michael Feathers argues against the widely held idea that unit testing, by itself, improves code quality. Michael talks about unit testing, integration tests, TDD and Clean Room Software Development, concluding that code quality is a function of thought and reflection, not bug prevention.
The involvement of customer in an Agile project is taken for granted, however in many situations, intentionally or unintentionally, the customer may not follow the Agile practices. An interesting discussion on the Extreme Programming group tries to decipher the situation and find possible solutions.
In which David Longstreet claims Agile Software Development is a Fairy Tale that just tries to legitimise Cowboy development, and Geoff Slinker invites him to write a Serious Article based on Logical Arguments and Citing Sources.
In a moment of relaxation, Alistair Cockburn had the insight that we may be quibbling over inconsequentialities: "test before" or "test after," what's important to professional programmers is Good Unit Tests. Eureka!
At JAOO '07 Bob Martin asserted: "it is irresponsible for a developer to ship a line of code he has not executed in a unit test." In this InfoQ video, Martin debated with another well respected software thought leader, Jim Coplien, on this and other topics, including Design by Contract vs. TDD and how much up-front architecture is needed to keep a system consistent with the business domain model.