Each and every software defect adds unplanned work—essentially rework—to the schedule. IT must tackle rework head on to determine the most appropriate areas for improvement, investment, and increased quality.
This report provides cost of rework models for Agile and non-Agile projects and recommends ways to test earlier to reduce rework and its cost. Learn how to reduce the cost of rework in development and testing to help prevent catastrophic defects from occurring in production.
The concept of the Cost of Quality, that is, the cost of rework to remove defects, is that the later in the lifecycle a defect is identified, the more expensive it is to resolve the issue. With its shift in requirements ownership from the business to developers who will discover requirements through changes to the source code, the Agile movement is effectively pushing requirements definition to later in the lifecycle. Applying models for the cost of rework to Agile projects reveals the hidden costs of the late definition of requirements. This report provides economic models for evaluating project results and selecting the most appropriate practices.
Theresa Lanowitz's slides from Cognizant's exclusive Testing Summit.
Presentation slides from the joint Borland/VMware webcast with Theresa Lanowitz from voke talking about what it takes to test and deliver applications that hit their mark using virtualization. And why getting the most out of virtualization depends on how seamlessly it can be integrated with your software testing processes.
Presentation slides from SQC-UK Software & Systems Quality Conferences in London, United Kingdom.
Keynote presentation slides from the Software and Systems Quality Conference in Zurich, Switzerland.
In this requirements.net exclusive podcast, Theresa discusses a rather unconventional report (titled: Fortune 500 Spending Required for IT Cost Savings”) which looks at the economy and smart moves for IT.
In this report, the voke research team makes some very interesting reminders about the fall out of the dot-com bubble bursting, and the lesson’s from IT’s reaction in 2001 and 2002.
The voke research teams make some important recommendations which tie directly to Business Analyst empowerment and investments in requirements definition as a critical element to surviving the IT downtown.
The Podcast is 40 minutes of a fact-based, fresh dialog on efficient outsourcing, IT virtualization, lifecycle management, and the importance of the BA and requirements.
In this joint Borland/VMware webcast, Theresa Lanowitz from voke will talk about what it takes to test and deliver applications that hit their mark using virtualization. And why getting the most out of virtualization depends on how seamlessly it can be integrated with your software testing processes.Read More...
Hewlett-Packard (HP) is in the Pivotal band of the voke Market Mover Array chart. HP’s position shows it is strong in both market leadership and technology. HP has continued to show progress and commitment to the application lifecycle market through its acquisition and partnering strategies. HP’s acquisition of Mercury in November 2006 has allowed the vendor to catapult its application lifecycle status to a higher level. The Mercury acquisition with market leading quality assurance offerings gave HP a core competency to work with as the vendor navigated the application lifecycle path.
HP is working to prove itself as an enterprise-worthy partner in the application lifecycle market. Its partnerships and acquisitions have proven to be strategic over the past 24 months. Watch for HP to deliver more value through organic growth of its offerings.