How Continuous Delivery Can Solve Root Cause Business Problems
Adrian Stanek
Daily Videos on Leadership & SaaS | Entrepreneurial CTO | Guiding Teams & Leaders, Mentoring, Dad ????????
No matter which company and tech organization I spoke with this year or which problem they initially saw as their pain point, after several days of working together, we concluded that their overall process was the root cause.
Common misconceptions:
Those are just some, but they already provide a good display of what is wrong. None of the mentioned things tackle the root-cause problem. Even if you do all those points, you will still miss one essential thing: a constant feedback loop.
This article is based on the Live Episode with Bryan Finster ( Defense Unicorns ) and Denis ?ahuk .
“The Three Wrongs of DevOps—Engineering Culture”.
??? The Podcast Video and Audio Version will be released tomorrow, on Monday.
When you miss feedback, you will miss the goal.
We are doing business with humans, and we humans have needs, requirements, and, most importantly, expectations. To meet expectations, the people building feature by feature need to know what those expectations are about, but this is often untrue.
Instead, Software Engineers are often fed with processed tickets in some form of Kanban or “Scrum” board. Tickets that are based on user feedback but already interpreted by at least one other person. Additionally, the tickets don’t seem to loop straight back to the Software Engineers; instead, I often see a temporal decoupling problem there as well–the tickets are gathered for days, sometimes weeks, before being formed as an “update” package handed off to the developers.
? Unfortunately, oftentimes, this is done with a tight deadline because much of the time has already been wasted with “ticket” management.
领英推荐
Be aware: Requirements, Needs, and Expectations change quickly.
The temporal gap between the actual feedback of the user and the engineer working on the next iteration is oftentimes huge, blended by an artificially tight deadline in the end for the engineer. This is a recipe for failure.
?? The shorter the time between user feedback and the next iteration gets, the more likely you are to hit the goal, meet the expectation, and satisfy the user.
Read the following sections on my Blog:
Deadlines are the arch-enemy of hitting quality.
When Software Engineers refuse responsibility
Conclusion – The Continuous Delivery’s Effect
?? ?? And there is a special End-of-Year Supporter offering, which will give you 30% off lifetime.
Have a great End-Of-Year, everyone!
Adrian
?????? & ?????????????? ???? ???? ???????????????????????????????? ????????????????. I am an expert at driving brand growth and visibility through personal branding, thought leadership, company brand building and PR.
11 个月Interesting article, Adrian Stanek. Continuous feedback is indeed crucial in creating great products and solving business problems.
Daily Videos on Leadership & SaaS | Entrepreneurial CTO | Guiding Teams & Leaders, Mentoring, Dad ????????
11 个月?? Tune in for the Full Video/Podcast featuring Bryan Finster and Denis ?ahuk on December 18th at 09:00 CET: https://open.substack.com/pub/snackablecto/p/the-three-wrongs-of-devops?r=2sxink&utm_campaign=post&utm_medium=web&showWelcome=true
Searching New Opportunities || Bachelor of Arts (B.A.) running student || HSC-BMT Passed || Fresher
11 个月Hi Adrian Stanek, Do you have any YouTube channel?
Helping You Avoid Pitfalls in Software Development (Internal or Agency) ??? Technical Consultant for Innovators & SMBs
11 个月We once developed an app for govt. The lack of user feedback (responsible people too busy) the project almost did not made it time (since one untold but crucious expectation was missing both from analysis - signed by both parties - and from the product). It could have spared some rework if we'd had feedback earlier...
Director of Technology
11 个月Great for teams, products, and also people. Thanks for sharing, Adrian!