Managing the Dynamic Datacenter

Datacenter Automation

Subscribe to Datacenter Automation: eMailAlertsEmail Alerts newslettersWeekly Newsletters
Get Datacenter Automation: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Datacenter Automation Authors: Shelly Palmer, Automic Blog, Pat Romanski, Elizabeth White, Liz McMillan

Related Topics: Datacenter Automation, Sarbanes Oxley on Ulitzer, DevOps for Business Application Services, DevOps Journal

Blog Feed Post

5 Habits of Highly-Successful Continuous Delivery Practitioners [Guest Blog]

By Furkan Khan, Director of Product Management at Perforce

continuous deliveryThis article was originally published on the Perforce Blog.

For all the talk about Continuous Delivery these days, it can be hard to find best practices from the companies that are actually doing it.

Because Continuous Delivery puts additional demands on the underlying versioning system, we work closely with a lot of companies who are already practicing it. To see an example, watch the Salesforce.com presentation on how they do Continuous Delivery on Perforce.

What do the most successful Continuous Delivery practitioners have in common? We’ve put together a list of 5 key things…

  1. Think Beyond Code: Continuous Delivery is focused on more than just code. Every element of a product needs to be consistently versioned from development to deployment, including artwork and other binary files, chip architectures, CAD designs, documentation, configuration scripts, and more.

  2. Automate, Automate, Automate: In a highly automated environment, changes to code can be almost instantly checked for integration into the delivery package. “Failed” changes can then be immediately corrected by the development team to ensure a high level of efficiency, predictability and repeatability—key attributes to a successful Continuous Delivery approach.

  3. Make Everything Fully Visible: Stakeholders must have visibility and input into what gets built and released. Peers should participate in reviews and collectively push for a higher bar for quality.

  4. Track Every Change: Recording every change, event and transaction is hugely valuable in situations where a rollback to a previous version is required. Altering history should be prohibited, especially when compliance and industry regulations demand stringent recordkeeping.

  5. Put It All in One Place: Instead of maintaining silos of code and assets, and project-specific branches, implement a “single source of truth” for the entire production environment. If assets and artifacts are distributed in multiple locations and multiple stores, there is a risk of introducing new errors and failing to meet delivery deadlines.

But wait...there's more!

To get the full lowdown on Continuous Delivery best practices, check out our new report, “Continuous Delivery: Five Habits of Highly Successful Practitioners.

 

fkhan's pictureAbout the Author

Furkan Khan is Director of Product Management at Perforce Software. See all posts by Furkan Khan

Learn More Habits of 5 Habits of Highly-Successful Continuous Delivery PractitionersAttend the  SDLC Acceleration Summit

Want to explore Continuous Delivery trends and best practices along with your peers and industry experts? 

Join us on May 13 in San Francisco for the SDLC Acceleration Summit  as we explore best practices for getting applications to market on time, on budget, and with a high degree of quality. 

 

sdlc_banner_continuous

Hear from industry leaders from vokeSalesforceIntuitAmazonSchwabLowes, ZipCar, BlueShield and the Department of Homeland Security as we discuss Testing, Software Quality, Continuous Release, Application Delivery, and Automation.  

  • What: SDLC Acceleration Summit
  • When: Tuesday, May 13, 2014
  • Where: South San Francisco Conference Center
  • Who: DevOps, Development, QA, and Testing

LAST CALL... only  a few seats available. 

 

Read the original blog entry...

More Stories By Wayne Ariola

Wayne Ariola is Vice President of Strategy and Corporate Development at Parasoft, a leading provider of integrated software development management, quality lifecycle management, and dev/test environment management solutions. He leverages customer input and fosters partnerships with industry leaders to ensure that Parasoft solutions continuously evolve to support the ever-changing complexities of real-world business processes and systems. Ariola has more than 15 years of strategic consulting experience within the technology and software development industries. He holds a BA from the University of California at Santa Barbara and an MBA from Indiana University.