Most technical incident response plans typically account for stakeholder communications—for both internal teams and external customers. But at PagerDuty, what we’ve learned from our customers is that there’s still a painful and expensive gap in alignment between IT and business teams. To close that gap, we need to focus on what incident response means for business teams.
Are you a practitioner looking to attend the speaking sessions at PagerDuty Summit 2019 and want to get into the weeds with the PagerDuty developer community? This year, the PagerDuty Community Team is drumming up many special activities that puts users at the front lines of real-time operations.
Imagine this: An airline encounters a major IT incident in a data center that affects their ticketing system. Behind the scenes, technical responders are scrambling to diagnose and fix the issue. However, because today’s systems are so complex, this issue is taking longer than expected to resolve, and hours have passed since the system went down. Meanwhile, passengers are stranded and taking their anger out on customer service agents and sharing their frustrations on social media.
Nearly two years ago, I joined PagerDuty as an Agile Coach with limited experience working with Kanban delivery teams. I started coaching two Scrum teams, but as soon as my teams got word that their peers using Kanban were happier and higher-performing, they pushed for the switch. Today, nearly all delivery teams here have transitioned from Scrum to Kanban.
Many organizations are transitioning to DevOps, a software practice where developers both write and operate their code. This transition is often driven by digital transformation and the need to innovate faster while being always on, 24/7. But what does DevOps have to do with diversity, inclusion, and belonging?
This week’s AWS Summit in New York was an exciting one for both AWS and PagerDuty. The AWS team rolled out Amazon EventBridge, a set of APIs for AWS CloudWatch Events that makes it easy for AWS SaaS partners to inject events for their customers to process in AWS. PagerDuty is excited to continue and deepen our long partnership with AWS by supporting EventBridge as a launch partner.
Last year at PagerDuty Summit 2018, we officially launched PagerDuty University (PDU), a training program that provides hands-on classroom training to current and prospective customers so they can get the most out of the PagerDuty platform. Since its debut, PDU has taught hundreds of learners how they can optimize their instances to minimize downtime and improve responders’ quality of on-call life, in addition to providing thought leadership best practices to customers around the globe.
This week at re:Inforce in Boston, the AWS team showed off its Security Hub service—a powerful service that provides SecOps teams a comprehensive view of their high-priority security alerts and compliance status across their AWS accounts. We’re excited to join AWS at re:Inforce this week as a Security Hub partner, where we’ll show users how PagerDuty and AWS Security Hub work together to provide real-time SecOps to any team using AWS.
Making the move to DevOps can be a daunting undertaking, with many organizations not knowing where to start. I recently had some fun taking a few DevOps assessments to see what solutions are currently in the market. I varied my answers from an organization that fully embraced DevOps to an organization at the beginning of its journey.
The PagerDuty Incident Response Process is a detailed document that provides a framework for how to structure your incident response process. But sometimes it helps to understand how these seemingly abstract concepts play out during real-world scenarios. You can now hear an incident call recording that’s based on a real PagerDuty incident. Due to the nature of incident response practices, the process guide we publish is filled with very explicit details regarding a variety of situations.
