Why do we promise more than we can deliver? Why do we say yes when we are already too busy? Chronic Overcommitment is a pervasive problem in the IT industry. In this article we take a look at the behaviors that drive over commitment and the dynamics at play in your organization the make it a difficult problem to solve. Finally, we offer some advice to those who suffer from this affliction.
In the last couple of years terms like Specification by Example, Executable Specifications and Feature Injection have showed up quite frequently in the community, often in relation to Behaviour Driven Development (BDD) or tools like Cucumber or SpecFlow. InfoQ have talked to some of the leading experts in this domain about what these practices are and how they relate to BDD.
Microsoft's Neal Gafter, who was primary designer and implementer of the Java SE 4 and 5 language enhancements and now works for Microsoft on .NET platform languages, discusses the impact of Oracle's acquisition of Sun on Java,makes the case for adding segmented stacks and a meta-object protocol to Java,, and offers some insights into how Java and C#/.NET compare.
Elisabeth Hendrickson talks about the inclusive and collaborative nature of the agile community and how it has changed the nature of work in organisations large and small. 1
AgileJapan held it's third incarnation this year in Tokyo. Linda Rising was the keynote speaker and her words of encouragement for Japan echoed those felt by the rest of the world. 1
Mike Beedle states that agile is in a state of contradiction, we need to focus on quality to prevent poor implementations tarnishing the reputation of good agile practices. 3
Angela Martin provides advice on practices which encourage team collaboration and cohesion, with some ideas on how to create truly cross functional collaborative teams. 2
Johanna Rothman discusses the way in which agile practices work together to improve project outcomes, how this is not restricted to software development and challenges teams to become truly agile.
Mike Cohn reflects on a decade of Agility and looks forward to the day when we no longer see being agile as something special, rather agile is just the way software development is done. 2
James Coplien looks at the Agile Manifesto as a checkpoint in the cycle of fashion and change, and a tool that became an instrument of broad mainstream acceptance of prevailing technical practices. 4
Stephen J Mellor is one of the original signatories of the Manifesto. His focus is on the use of models in software development works to overcome the perceived conflict between Agile and modelling. 6
Chris Matts who has been part of the Agile Conference submission review team gives advice to submitters of Agile 2011 candidate sessions on how improve their changes of acceptance. 1