Don’t forget the most important consideration in quality management: human beings. In this article, the writer addresses a way of handling quality management with this most important aspect at the forefront.
13 items found
How managers change with agile approaches is vital. The more management excellence—the more quality in management—the easier it is to use an agile approach. That requires a change in how managers think about and create the agile culture.
Quality analysis and quality management can be a full-time occupation for an entire team of people on a project. Unfortunately, not all projects have the scope or resources available to hire a quality team to work on a project. This article explores some basic guidelines for using analysis to manage quality on a project.
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...
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 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.
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?
A quality process is typically entrenched as a documented procedure or a quality document or standard that governs the creation of services, products and activities that produce results. Here is some help developing this important document.