voke Market Mover Blog

The analysts at voke are embarking on a busy time of year! Join voke founder, Theresa Lanowitz, on October 28, 2014 at 8:30AM Pacific / 11:30AM Eastern to discuss “ The Hidden Cost of Rework ”. Each and every software project has defects – that is just a fact. However, the longer the defect is ignored, the more expensive it is to remediate. Join Theresa Lanowitz of voke and Jon Jarboe of Coverity to learn how to identify defects earlier and reduce the cost of rework involved with every software project. Register here to learn about “The Hidden Cost of Rework”  Next up, voke founder, Theresa Lanowitz, will be the keynote presenter at the Cognizant Quality Engineering and Assurance Summit in Sydney, Australia! The theme of the event is “The Future of Quality: Challenge the Conventional Status Quo”. The event is Thursday, November 6. If you are in the ANZ region, register here .  Theresa’s keynote will discuss “Software Quality in the Sound Bite Era”. Join T...

Are you aware of what your cost of rework is for your software? Yes, the very software that runs your business and is an integral part of your brand promise. Most organizations are either not aware or not interested in what the cost of rework means. However, this cavalier stance to the cost of rework is dangerous. Each and every software project has an associated cost of rework – that is the cost involved with removing defects. The later in the lifecycle a defect is discovered, the more expensive it is to remediate. Defects create the hidden cost of rework in every software project. The new voke Strategic Brief TM Report: Reducing the Cost of Rework highlights: The business impact of defect leakage with real-world use cases The cost of rework models for both Agile and non-Agile projects Ways to test earlier to reduce rework and its costs The Strategic BriefTM Report: Reducing the Cost of Rework is available here or at www.vokeinc.com for su...

In 2012, voke published economic models to evaluate the hidden costs of software projects.  Our key findings show that since the Global Financial Crisis (GFC) of 2009, the average cost of software projects is rising dramatically, this is in spite of smaller teams working shorter durations.  At the same time, rework costs remain high or unknown and high profile software failures continue to make headlines daily. Organizations must understand how defects create a hidden cost of rework in every software project and how these costs manifest differently in Agile and Non-Agile projects. Given the impact of catastrophic software failures on the brand, we should be witnessing a movement toward increased quality, not a reactionary call for more testing after the software has shipped. Software engineering professionals are familiar with the concept of Cost of Quality , or more specifically, the cost involved with removing defects , essentially the cost of “rework .” The prem...

The Agile Dilemma Who doesn’t want to be agile? Ballet dancers, weight lifters, and business executives alike aspire to be agile – that liveliness, coordination, and quickness is something we all desire in life and business. Why then is there an “ Agile Dilemma ” in software development? voke defines the “ Agile Dilemma ” as the inherent risk and confusion created by the business desire for speed and flexibility misinterpreted as a mandate to participate in the developer-centric movement called Agile, which may not be appropriate to all organizations or projects. What this really means is that business executives are expressing the need to be flexible, nimble, and responsive to customers to ensure satisfaction and a competitive edge. The software development team is listening to this business mandate and interpreting it as a call to participate in the Agile movement. But, is participation in the Agile movement right for every organization or every project? We wanted to find o...