In a recent post, see here, I summarized four of the key DevOps principles, namely: 

1. Automate as much of the deployment pipeline as feasible
2. Develop and test against a production-like system
3. Deploy frequently
4. Continuously validate operational quality characteristics

Programs and projects adopting continuous delivery practices must create software in such a way that the software can be released to production at any time.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Roles:

Business Stakeholder: represents the organization to adopt DevOps

DevOps Expert: Expert in DevOps adoption (may be a consultant from IBM).

DevOps Adoption Manager: Plans and establishes a core team to steer the adoption.

DevOps Adoption Core team: Responsible for steering the adoption initiative, including monitoring and mentoring.

Development Team (pilot): responsible for the development on the pilot program/project.

 

In order to release regularly, project must have an effective quality management strategy that provides timely feedback on the state of the software at any time.  Regardless of whether the project is following a traditional or agile methodology, making quality an integral part of the software lifecycle requires the whole team to collaborate effectively. 

Here are seven best practices for improving quality using Continuous Delivery

1. Adopt Concurrent Testing practices (e.g., embed skilled testing resources on each teams)
2. Synchronize agile teams and independent test teams around a common release plan
3. Ensure test planning is incorporate into release and sprint plans
4. Automate labor-intensive activities (test execution, test case creation, virtualization of environments configuration)
5. Share information seamlessly using dashboards and easy to understand reports
6. Conduct exploratory testing to improve overall quality
7. Report on project metrics for informed release decisions (e.g., track Burndown, team velocity, defects and accepted stories ready for delivery)

For additional information check out the following resources

• 7 Proven Practices to Strengthen Release Management

Tags:  devops safe scaled-agi​le-framewo​rk agile_tran​sformation #agile agile-deve​lopment ids developmen​t agile-alm-​study-grp scaling tip softlayer dad ibmagile process rational-t​eam-concer​t agile-alm discipline​d-agile-de​liv... governance agile-safe practices ibmstory testing clm continuous​-integrati​on enablement saas software enterprise story agile-alm-​template adoption ibm rtc event rational agile-plan​ning continuous​-delivery cloud team how-to ibminnovat​e scrum scale bluemix lean agile alm ibmrationa​l