I’ve published a new article on the Equal Experts website, describing why product teams still need major incident management…
Recent Posts
- Why you need alignment with autonomy at scale
- 4 ways to successfully scale agile delivery
- Why product teams still need major incident management
- 4 ways to remove the treacle in change management
- The maintenance mode myth
- 5 ways to minimise your run costs with You Build It You Run It
- How to decide when to use You Build It You Run It (and when not to use it)
- GitOps is a placebo
- Investing in Continuous Delivery
- Continuous Delivery levels
Tags
Agile (14)
Antipattern (12)
API Examples (2)
Batch Size (4)
Build Operability In (3)
Build Quality In Book (1)
Consumer Driven Contracts (3)
Continuous Delivery levels (3)
Cost Of Delay (5)
DevOps (1)
Measuring Continuous Delivery (4)
Multi-Demand (5)
No Projects (6)
No Release Testing (4)
Pattern (9)
Pipeline (8)
Resilience As A Continuous Delivery Enabler (4)
Risk (12)
SRE (2)
Strangler Pipeline (5)
Testing (7)
Theory Of Constraints (2)
Trunk Based Development (4)
Version Control (5)
Who Runs It (8)
Within our IT Service Management structure, we don’t have a specific role called Incident Commander; rather, we only have the Incident Manager role. However, in other departments, such as Occupational Health and Safety, the Incident Commander role is present and plays a crucial role in managing safety-related incidents effectively.