Skip to main content


Rework is just another word for money down the drain. Not only does it wreak havoc with your delivery, but it can be unbearably demoralizing for your development teams. To minimize rework, think of it like a goldfish that grows as big as the space you give it – bigger bowl, bigger fish. You have to shrink the space that rework lives in before it becomes fishzilla….

How big is your bowl?

The rework monster lives in the gap between your developers and your QA teams. If coders and QA are on the same team, rework is kept to a minimum. But in organizations with a large gap between development and QA, rework can grow big enough to consume every resource in sight. What if circumstances force you to keep your coders and QA teams separate?

FDA compliance. Distant silos. And months of idle code.

We worked with a company in the medical equipment industry that faced a huge rework problem. It wasn’t all their fault. The equipment they manufacture must be approved by the Food and Drug Administration (FDA). This, of course, puts them in a highly regulated environment with stringent requirements. To ensure compliance, they had a separate quality department. Unfortunately, this separate department meant a wide gap had been created between developers and QA.

This gap gave the rework monster plenty of room to live and grow in. With everyone working in silos, code would sit for months before being validated. Costly cycles of rework had grown completely out of control.

How did they close the gap without closing the department?

Folding QE into IT was not an option. But, there’s always a way to close the gap. So here’s what the company did. They reorganized and added new QA people to their IT department, leaving QE in operations to work exclusively on FDA requirements. That way code could be tested internally before making its way up the line for FDA approval.

The result? Successful two-week agile cycles are now the norm.

Our client was able to stop the rework and adopt a faster, smoother cadence, propelling projects forward every two weeks with tested code. They are even beginning to identify bottlenecks and solve them – on their own initiative.

Learn more best practices for avoiding rework. Download our free e-book: The 2014 Bottleneck Report on Enterprise Mobile.

Randall McCroskey

About the author

Randall McCroskey

Vice President, Enterprise Solutions

Since 2006, Randall has been helping technology executives digitally transform their business as Vice President of Pyramid Consulting. Relationships are his daily driving force and his desire to trust and serve those in his professional and personal life constantly motivate him. Atlanta is a great city for Randall, as he hates the cold and prefers warm weather near the water. His greatest pride is the partnerships with colleagues, friends, and fellow professionals he has made along the way.

Cookie Notice

This site uses cookies to provide you with a more responsive and personalized service. By using this site you agree to our privacy policy & the use of cookies. Please read our privacy policy for more information on the cookies we use and how to delete or block them. More info

Back to top