Terence Parr discusses using automation tools including DSLs to automate the software creation process as much as possible in order to increase output, effectiveness, correctness and velocity.
Interruptions are something that every team has to deal with and, if not managed appropriately, they can potentially have a detrimental affect on their ability to deliver. In a recent post on the Agile Advice blog, Mishkin Berteig described seven options that teams could consider to deal with interruptions when using Scrum or iterative Agile approaches.
As technologists we often never question how technology is affecting us and our world. This interview with Eric Brende presents an a different view on progress, innovation and technology.
Agile practices should foster high-performance self-organizing teams. It is important that high-performance equals value delivery, to ensure that the team solves the right problem. It is also important to create an environment where high-performance can flourish which requires thinking and action at a management level. We examine three commentators perspectives on enabling high performance.
The skills required to be hyper-productive in agile projects are different from those required by a traditional one. This article identifies behavioral and technical skills required for a team to have that edge. Anyone who acquires these "delta" traits should be equipped with the right set of behavioral and technical skills, which enable them to work effectively in an agile project.
Hamlet D`Arcy demonstrates some of the Groovy tools useful to increase productivity by generating code at compile time: Project Lombok and AST Transforms.
In this presentation filmed during Agile 2008, Michael Mah analyzes the development process in 5 companies: 2 Agile (one of them BMC) and 3 classic. He measures the development productivity and effectiveness and compares the results with industry averages. He also presents the factors which contributed to the success of BMC's Agile adoption.
Joe Armstrong and Dave Thomas take a look back on the evolution of software and progress that has been made. They make some observations about the actual state of the industry and highlight problems that prevent it from delivering quality software. They try to identify reasons of these issues and suggest craftsmanship as possible solution.
Zed Shaw and Matt Pelletier sat down with InfoQ's Obie Fernandez at RailsConf to explore some of the reasoning behind setting up the mongrel project, getting adoption in enterprise and dealing with developers who just aren't ready. Watch the interview to find out how much Shaw's Enterprise Mongrel product will cost, where the support contracts are and who'll come out on top when the vultures land.
