Discussion on quality management has not evolved much since the mid-1990s. Within executive circles, the discussions are not about the importance of quality, but rather on what quality is, how it is achieved and how it can be measured. The issues surrounding quality seem focused on definition and approach rather than on need. What is quality? What does senior management expect from the quality process, and how do these expectations apply to IT? Read on...
39 items found
We want to do quality work. We want our results to be seen as being quality. But what does that actually mean? And how do we test for it? How can we satisfy for ourselves—and demonstrate to others—that we’ve delivered on expectations in terms of quality?
Should quality matter to the project manager? Isn’t on schedule, on budget and to spec already a handful to manage? Use these quality tools and practices to ensure a positive project legacy.
Quality is everybody’s concern. The rising stakes resulting from increased investments—combined with a shift from traditional to complex project management—has made quality an important pillar of the project management discipline. A case study illustrates the organizational benefits of continuous improvement through Kaizen.
You're not going to have customers to manage if your business isn't providing quality. Here's a quick review of Deming's TQM concept; it's worth a reminder.
Instead of measuring quality, Agile enterprises commit to it by investing in integration and testing, developing a common language around quality, and nurturing motivated, disciplined teams. Ultimately, quality reigns when organizations value it as much as profitability and protect the agile processes that support it.
Quality takes time, effort and hard work to realize. So what does that mean for project managers? Does it mean we need to be investing even more in our project management processes? Do we need to be learning arcane techniques for statistical process control and total quality management? Do we really need that Sigma Six black belt after all? Not necessarily.
During the last few decades, many quality management programs have delivered real benefits to many organizations across the world in a number of areas including cost control, process improvement, customer retention and product development. That is why organizations have embraced the concept of quality management as a key business enabler and a critical success factor.
Quality process has to be built into a project and should not be seen as a waste of time or cost. The time invested in developing quality software is the best time to earn the reputation and goodwill of the customer, and the cost invested is the cost of reducing rework. In this article, we will see how and what needs to be considered for embedded software development to plan, execute, and control quality.
With more and more pressure to accelerate delivery and shorten the time to market, how do we ensure quality standards don’t suffer?