Why retrospectives and post-mortems work | #DOES15
by Heather Johnson | Nov 13, 2015
Engineering consulting firm Release Engineering Approaches is currently working with Salesforce.com on DevOps issues such as retrospectives, a process that determines what went well and what didn’t go well, as well as how to improve next time.
“They have a complex system that they operate for their customers, and sometimes it has service impacts or outages due to changes that they make,” said J. Paul Reed, principal consultant at Release Engineering Approaches. “There’s an incident and a team that works on those incidents. The challenge is how to take that data, collect it in an actionable way, talk about it in a healthy way and then feed that back into the system to make improvements.”
The meaning of accountability
Reed also discussed post-mortem processes with Brian Gracely, cohost of theCUBE, from the SiliconANGLE Media team, during the DevOps Enterprise Summit in San Francisco. “There is a difference between accountability and responsibility,” he said. “Everyone is held accountable for their behavior, but that doesn’t necessarily mean that they are responsible for a particular failure.”
Some technicians may wonder where the value in DevOps lies.
“Humans contribute to the success of the organization and the successful operation of the technology just as much as they contribute to the failure,” Reed explained.
Forgot Password
Almost there!
We just sent you a verification email. Please verify your account to gain access to
DevOps Enterprise Summit 2015. If you don’t think you received an email check your
spam folder.
In order to sign in, enter the email address you used to registered for the event. Once completed, you will receive an email with a verification link. Open this link to automatically sign into the site.
Register For DevOps Enterprise Summit 2015
Please fill out the information below. You will recieve an email with a verification link confirming your registration. Click the link to automatically sign into the site.
You’re almost there!
We just sent you a verification email. Please click the verification button in the email. Once your email address is verified, you will have full access to all event content for DevOps Enterprise Summit 2015.
I want my badge and interests to be visible to all attendees.
Checking this box will display your presense on the attendees list, view your profile and allow other attendees to contact you via 1-1 chat. Read the Privacy Policy. At any time, you can choose to disable this preference.
Select your Interests!
add
Upload your photo
Uploading..
OR
Connect via Twitter
Connect via Linkedin
EDIT PASSWORD
Share
Forgot Password
Almost there!
We just sent you a verification email. Please verify your account to gain access to
DevOps Enterprise Summit 2015. If you don’t think you received an email check your
spam folder.
In order to sign in, enter the email address you used to registered for the event. Once completed, you will receive an email with a verification link. Open this link to automatically sign into the site.
Sign in to gain access to DevOps Enterprise Summit 2015
Please sign in with LinkedIn to continue to DevOps Enterprise Summit 2015. Signing in with LinkedIn ensures a professional environment.
Are you sure you want to remove access rights for this user?
Details
Manage Access
email address
Community Invitation
J. Paul Reed - DevOps Enterprise Summit 2015 - theCUBE - #DOES15
Why retrospectives and post-mortems work | #DOES15
by Heather Johnson | Nov 13, 2015
Engineering consulting firm Release Engineering Approaches is currently working with Salesforce.com on DevOps issues such as retrospectives, a process that determines what went well and what didn’t go well, as well as how to improve next time.
“They have a complex system that they operate for their customers, and sometimes it has service impacts or outages due to changes that they make,” said J. Paul Reed, principal consultant at Release Engineering Approaches. “There’s an incident and a team that works on those incidents. The challenge is how to take that data, collect it in an actionable way, talk about it in a healthy way and then feed that back into the system to make improvements.”
The meaning of accountability
Reed also discussed post-mortem processes with Brian Gracely, cohost of theCUBE, from the SiliconANGLE Media team, during the DevOps Enterprise Summit in San Francisco. “There is a difference between accountability and responsibility,” he said. “Everyone is held accountable for their behavior, but that doesn’t necessarily mean that they are responsible for a particular failure.”
Some technicians may wonder where the value in DevOps lies.
“Humans contribute to the success of the organization and the successful operation of the technology just as much as they contribute to the failure,” Reed explained.
