Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Does success at the team level always result in success at the organization level? Sanjiv Augustine and Arlen Bankston discuss the Seven Deadly Sins that organizations repeatedly make so you can steer clear of them and benefit from a successful Enterprise Agile Adoption.
Jean Bezivin retraces the path that lead to our current software engineering practices and explore new avenues for the coming decade as, he notes, "there are some indications that we are currently crossing some new frontiers in technology and practices".
"Simplicity" is a core agile tenet, particularly when it comes to software design and testing. Since 2006, Naresh Jain has been running a worldwide conference, the Simple Design & Testing Conference, for practitioners to collectively push the boundaries on the topic. Naresh tells InfoQ what's going on behind this small, but well-known conference and why he is so passionate about the topic.
In the nature vs. nurture debate, researchers have declared nurture the winner. People who excel are the ones who work the hardest; it takes ten+ years of deliberate practice to become an expert. Deliberate practice is not about putting in hours, it’s about working to improve performance. It does not mean doing what you are good at; it means challenging yourself under the guidance of a teacher.
In this interview at Agile 2011, Jez Humble discusses continuous delivery and the deployment pipeline, emphasizing the importance of feedback and automating tests at every level to validate deployments. Gone are the days of massive acceptance test scripts. He also talks about the evils of feature branching, and speaks on the DevOps practices to collaborate all the way through the delivery cycle.
Mik Kersten discusses the role of Mylyn and Tasktop in Agile development and how these tools return control to developers. Also: how Mylyn streamlines development in Eclipse.
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.
