InLevel Up CodingbyAndrii Lazarenko·6d agoThe Sprint Was Green. The Release Wasn’tThe number of completed tasks cannot be the primary measure of an engineering team’s success.
InLevel Up CodingbyAndrii Lazarenko·Nov 4“The team stopped arguing — and that’s bad news”: the anatomy of a socio-technical conflictIf the product and technical teams have suddenly stopped arguing, don’t be too quick to celebrate. Perhaps they have genuinely learnt to…A response icon1A response icon1
InLevel Up CodingbyAndrii Lazarenko·Nov 4How Product and Engineering Can Stop Arguing About the Same ThingsIn the previous article, we looked at three recurring points of friction between product and engineering: speed vs. stability, tactics vs…
InLevel Up CodingbyAndrii Lazarenko·Aug 25Technical Debt: Manage It, Don’t Conquer It– “We need to deal with technical debt,” says Engineering.
InLevel Up CodingbyAndrii Lazarenko·May 27The Team Is Growing, but Delivery Is Slowing Down?The team keeps growing, but processes are not getting any better.
Andrii Lazarenko·May 27Incident Management in Practice: How We Built a Process from Chaos to SystemThe server is down, panic is everywhere, the team is running around trying to fix things — that’s an incident.