What does Continuous Delivery say about Test Strategy?

"90% done." The three most dangerous words in tech.

We've all been there! The team grinds for six weeks. Energy is high. Progress charts look great. Then comes the big reveal, only to hear, "This isn't quite what I had in mind." Suddenly, that 90% feels more like 10%. The frustration is crushing. What went wrong?

It wasn't a lack of effort. It was a lack of feedback.
The project's most critical test—"Did we build the right thing?"—was saved for the very end. This is a broken pattern. Testing isn't a final phase you tack on; it's a continuous conversation that should start on day one. It's a whole-team activity, not just a QA function.

A truly robust test strategy, as seen in Continuous Delivery, isn't just about automated unit and integration tests. It also includes crucial business-facing checks like usability testing, showcases, and exploratory sessions. It answers two questions constantly: "Are we building it right?" and "Are we building the right thing?"
By integrating these feedback loops throughout the process, you kill surprises. You replace a massive, painful course correction at the end with tiny, manageable adjustments along the way.

What's the costliest bug your team has ever fixed after saying you were "almost done?"

Agile SoftwareDevelopment ContinuousDelivery ProjectManagement TechLeadership

From the desk of,
Jasdev Singh
E: singhjasdev@gmail.com



Comments

Post a Comment

Popular posts from this blog

Increasing your Agile Team's Outcome Predictability

Image
Understanding Predictability in Agile Team Outcomes   "Understanding Predictability in Agile Team Outcomes" refers to the study or analysis of how consistent and reliable the results or achievements of a team practicing agile methodologies can be. This involves examining the factors that contribute to the team's ability to deliver on time and within scope, as well as identifying potential challenges or obstacles that may impact their predictability. By understanding these dynamics, organizations can better manage and optimize their agile teams for more consistent and successful outcomes. In today's rapidly changing world, the significance of accurate weather forecasts cannot be overstated. Similarly, in the world of software development, predictability is crucial for Agile teams. The ability to deliver outcomes predictably is a key factor in Agile team success. Achieving predictability can be challenging for Agile teams due to various factors such as capacity planning...
Read more

When you equate story points with time...

Image
Agile becomes fragile! When you are "doing" agile (most likely because it's in vogue) but have not come out of the "sequential " SDLC execution syndrome or the traditional waterfall way of thinking and executing a project, you are most likely headed for a disaster! Of many things that may or will go wrong, is the estimation of work . The traditional methods of estimation like function-point analysis helped us answer the question - "how long (or duration) will a piece of work take to complete?". On the contrary, Agile keeps it simple and takes a minimalistic approach to estimation. In my opinion, estimation in agile is no rocket science as long as you are clear with the basics and understand "what story points are" and how to use them. Visit my blog post on story points for an understanding. Story Points vs. Time (Person Days) Mike Cohn shares a mantra that makes estimation easy - " Estimate size, measure velocity, derive ...
Read more