Usually, when Jean Tabaka lists practices, techniques, ideas, or recommendations about software development, she sticks with the number ten. It's nice and neat and has a fine history of enumeration cleanliness dating back to the Old Testament. But for agile adoption failures, Jean thinks it is time to invoke some Spinal Tap and go to eleven. Here are her top eleven signs that your agile adoption is headed down a slippery slope to failure.
Agile is being evangelized in executive boardrooms and introduced top-down with increasing frequency. Considering that Agile advocates self-management by the individual and within a team, what is the role of senior leadership? My experience from this top-down perspective has given me insight into attitudes and techniques that are successful and others that fail. I assert that there is an effective and appropriate stance for senior leadership that will improve the effectiveness of an Agile transformation. Key to my list of recommendations for making Agile work is the balanced involvement of both senior-level leaders and practitioners in the planning and executing the introduction of Agile practices.
Amr Elssamadisy presents one way to share our knowledge that is more specific than full methodologies and processes, more general than war stories, and will help new agile adopters get beyond the mantra "It depends!"
Why wait to discover how your users will react to your system when there are ways to measure such things during development? This column describes a simple tool to develop visibility into customer satisfaction. Learn how you can begin to manage expectations so that neither you nor the customer has an unpleasant surprise on release day.