Merging Business Process With Continuous Delivery

Sauce AI for Test Authoring: Move from intent to execution in minutes.|xBack to ResourcesBlogPosted

March 18, 2026 · 5 min read · Testing Guide

Sauce AI for Test Authoring: Move from intent to execution in minutes.

|

x

Back to Resources

Blog

Posted November 20, 2015

Merging Business Process With Continuous Delivery

quote

One of the biggest hurdles in getting to Continuous Delivery and truly being Agile perform not lie within the development squad itself. Change requires a mindset that all citizenry (managers and executive too) must adopt. Just as it takes a village to elevate a nipper, it besides takes a (corporate) village to raise a new culture. The motility away from Waterfall to Agile and Continuous can not be address merely by one person.

Does the following situation sound familiar? Someone asks you for an estimate for the Level of Effort (LOE) of a feature. Not but a t-shirt sizing, but in years — something to be present sometime that year. You don ’ t have much time to really dive into it (it could even be during the like meeting that you first learn about the new feature), but you have to know all the point up front. So you give a bit that you aren ’ t guess to be held to because of all sorts of caveats you listed. But, someone remembers that act. And since soul said you are Agile (and Continuous Delivery), now you feature to not only converge that estimate you gave up front, you are now tied to an Agile sprint with no way for error. This goes against everything you say you are!

To truly get to Continuous Delivery, you may need to step out of your comfort zone. Step away from prognosticate a characteristic in a particular timeframe. Think priority. Think small chunks. Think iteratively. Get used to the unnamed, but plan for it. Forecasting is not accurate and outcome in broken promise across the board. It certainly doesn ’ t help to hold someone ’ s feet to the fire if what they built today doesn ’ t match what they thought four month ago. The inexact nature of estimation doesn ’ t matter as much when you are delivering often and iteratively. Release former and often, and you can be dynamic in responding to customer feedback.

It is so crucial to have this grain not just in the squad make the work, but also in the people making decisions, prioritizing lineament, and verbalise to customer. If they are stuck in a Waterfall mentality, how can you progress to a Continuous model? I conceive everyone postulate to know what it really means to be Continuous and Agile. It is a civilization and a mindset — not just a process — that everyone want to understand and believe in, from the item-by-item contributor to the CEO.

Turning the Tides

Let ’ s take a look at some ways teams may be scramble, and how they can adjust to turn the tide and get to Continuous Delivery.

The Struggle

The Agile (or Continuous Delivery) Way

One somebody (or a small group) pre-defining granular storey and what is in or out of setting before it even gets to the team.

Team gets epic, maybe milepost.

Team discusses epic together see unfastened interrogation and overall definition of functionality.

Team defines milestones.

Team defines the stories for first the milepost and starts the backlog.

Team defines technical or planning ear for subsequent milestones.

Team determine granular estimates for initial work, rough idea for following work where possible.

Iterate.

Telling someone WHAT to build (Example - “ Just build this feature ”).

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

Understanding WHY you are building it and WHO you are build it for.

(Example — “ As a I want to be capable to do so that I can ”).

Planning and scoping everything (all stories, all tasks) in approach.

Iterative planning that occurs every dash, in priority order. Maybe you don ’ t get to a few stories. THAT ’ S OK.

You don ’ t know the effort for everything up front. Just what you are direct into the sprint.

Use reserve dressing and story function to flesh out stories and assign story point.

Focus on the higher priority things. Lower priority things can wait.

Iterate.

Dev Managers make conclusion on prioritizing reserve based on ad hoc conversations with various people.

Priorities need to be clearly communicated by PM, with casual (or at least weekly) involution in backlog preparation

Prioritization can not happen in a vacuum. Overall feature/theme/epic priorities need to happen at the cross-tribe level and be seeable to all.

Accepting thing into a sprint without knowing adoption criterion.

Don ’ t start employment untileveryone on the squadknow what is needed to be successful.

Driving towards feature complete, and not releasing until an epic is complete.

Release former and often. Get client feedback as soon as possible. The Minimum Viable Product (MVP) needs to be small. Think of it as a preview. This way you can pivot from customer feedback, and work on epics doesn ’ t go on for long periods of time.

Making feature arm live for long periods of time make a maintenance, merge, and regression.

Headache.

Leverage feature switches so that you can merge feature work into freeing branch as presently as it ’ s execute, even if it won ’ t be visible to client.

No Agile training or prescribed procedure for team extremity.

PM/management needs preparation in Agile and needs to commit to changing along with the dev team.

All engineers, UID, QA, and PM affect in scrum teams need Agile grooming.

Let ’ s be clear, though — The Continuous model is not something that just befall nightlong. It takes hard work and discipline, and understanding what is ask to direct each aspect in order to be utilise successfully. If your leadership understands what it really takes to be Agile, they can aid you recognize your finish. Without their transition to the Agile mindset, you are still Waterfall compressed into the pressing of an Agile timeframe.

(1) The opinions in this column are a combination of experience and research derived fromAgile Testing: A Practical Guide for Testers and Agile Teams by Lisa Crispin and Janet Gregory, Chapter 3 – Cultural Challenges.

Ashley Hunsberger is a Quality Architect at Blackboard, Inc. and co-founder of Quality Element. She ’ s passionate about making an impact in education and enjoy train squad members in production and client-focused quality practices. Most lately, she has focalize on trial strategy implementation and training, development process efficiency, and advocate Test Driven Development to anyone that will listen. In her downtime, she enjoy to travel, read, quilt, hike, and spend clip with her family.

Published:
Nov 20, 2015
Topics
Share this post
Copy Share Link
LinkedIn
© 2026 Sauce Labs Inc., all rights reserve. SAUCE and SAUCE LABS are registered trademarks have by Sauce Labs Inc. in the United States, EU, and may be registered in former jurisdictions.
robot
quote

Automate This With SUSA

Upload your APK or URL. SUSA explores like 10 real users — finds bugs, accessibility violations, and security issues. No scripts needed.

Try SUSA Free

Test Your App Autonomously

Upload your APK or URL. SUSA explores like 10 real users — finds bugs, accessibility violations, and security issues. No scripts.

Try SUSA Free