Continuous delivery should be treated as an agile project as it is about automating your deployment. You have to speed up in small steps and gain trust by doing small deliveries and solve problems fast. The story about how Klaverblad insurance has implemented Agile, DevOps, continuous delivery, and microservices.
Martin Fowler, described Maturity Model as a tool that helps people assess the current effectiveness of a person or group and supports figuring out what capabilities they need to acquire next in order to improve their performance.
Jan-Joost Bouwman and Mark Heistek, from ING Retail Banking Netherlands, presented at Devopsdays Amsterdam how a CMMI-ITIL organization transitioned to a more agile mindset. Somewhat unusually in this kind of sessions, ING presented quantitative evidence of the improvements, such as a marked increase in the number of changes deployed to production and a decrease of the risk value per change.
An exploration on how project management with Scrum and the project management process areas of the Capability Maturity Model Integration for Development are related.
Thoughtworks recently published a whitepaper including a maturity model for continuous delivery (or CD) as a response to research indicating that most companies understand the importance of innovation, but are not able to deliver software quickly enough to meet the needs of business leaders.
A Collection of Agile Resources by J. Sutherland, K. Schwaber, D. Star, M. Lacey, and D. J. Anderson
Microsoft has put together a number of resources for Visual Studio developers, containing principles, practices and guidelines for Agile development. These resources are condensed articles written by influential Agile leaders -Jeff Sutherland, Ken Schwaber, David Star, Mitch Lacey, David J. Anderson - containing the essence of several Agile methodologies and being usable by any software dev team.
With debates on comparing and contrasting REST with WS-* or SOA having died down, the debate moves on to have to measure how RESTful a system may be, or how "mature" it is. One approach that is referred to many times is the Richardson Maturity Model. However, there is disagreement within the community as to whether or not this model is the right approach to use.
While Scott Ambler, Ross Pettit and others continue to pursue the creation of a maturity model for agile, David Starr has looked at how and why an organization might want to measure things like: agility, craftsmanship, and organizational success. He found craftsmanship relatively easy to measure, while agility was the most difficult to measure in a useful way.
Scott Ambler, who once wrote 'Has Hell Frozen Over? An Agile Maturity Model?', has started writing about something that he is calling the Agile Process Maturity Model. The discussion around Scott's model has uncovered another model by the same name, and renewed the debate over the usefulness of a maturity model for agile.
In this article, Kjell-Sverre Jerijærvi presents with enough detail Microsoft’s SOA Maturity Model (SOAMM) which can be used to evaluate the maturity of a SOA implementation.
In this presentation filmed during Agile 2008, David Anderson talks about the history of Agile, the current status of it and his vision for the future. The role of Agile does not stand in just having a practice, but in finding ways to implement the principles contained by the Agile Manifesto.
The Software Engineering Institute (SEI) recently published a paper entitled "Evaluating and Improving Architectural Competence", which looks at using four models of human behaviour to help assess and improve software architecture competence.
In the past couple of weeks, two major reports on "The State of BPM in 2008" were published by BPTrends and BEA. The reports show a fast growing market lead by major SOA infrastructure vendors, a significant growth of the adoption of BPMN and a steady growth of BPEL. Drivers for adopting a BPM approach range from cost savings to compensating for missing functionality in enterprise applications.
With Software as a Service (SaaS) becoming more and more mainstream, the architecture behind the offering is getting more discussion. Dharmesh Shah wrote about the economics of the SaaS architecture maturity model.
Periodically an Agile Maturity Model or a Framework for Agile Adoption shows up on the radar. There are also several consulting companies performing Agile 'readiness assessments' as a precursor to helping their clients 'become' Agile. Are these indications of an unfulfilled need in the community?