In innovation the mantra "fail fast" is often used to explain that people should quickly try out ideas and then learn from the things that fail to develop new products and services. Some people challenged the need for failure and have come up with alternative approaches for effective innovation.
The Puppet Labs: State of DevOps Report 2015 shows the current DevOps trends in IT, comparing the high and low performers in terms of deployment success and stability, and observing the link between architecture and developer productivity.
Matthew Badgley, shares ten tips for measuring agile success in a recent VersionOne blog based on the 9th annual State of Agile Survey.
Agile suggest that teams should fail-fast to enable quick learning from mistakes. Learning from failure is one approach, you can also learn early and fast from successes, by doing experimentation, or by using a plan for knowledge acquisition.
Working in an agile team can sometimes be stressful, when the needs of the customers are unclear, if there is a lot of work to be done, or when team members are having difficulties doing their work. You might ask the question if having fun could reduce the feelings of stress, increase motivation, or increase productivity? And if that is true, then what can you do to have more fun in agile teams?
Scott Ambler published the results of his annual IT project success survey, in which he examined the impact of methodology on project outcome. He looked at five different "development paradigms" and how they influence project outcome: ad-hoc, iterative, traditional/waterfall, agile and lean. Ambler's definition of success is deliberately subjective - how did the customer feel about the outcome?
Agile adoption and transformation is sometimes effective, and sometimes not. Is there a common thread to the failures? Does fear have anything to do with it? And what can we expect if we start an agile adoption initiative in an environment that is full of fear?