How do we define quality as a project manager? Is it managing a project really well, or managing a successful project? How about managing a successful project really well? That sounds pretty good. However, it poses the next question: What is a successful project? Let’s look at some examples of project success, failure and ambiguity.
Matt sent a particular system engineering document out for peer review. The quality assurance analyst on the project sent an email out asking the SE lead which version of the document templa ...
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.
Code inspections are an implicit, often unspoken best practice among agile project management teams. This silence has caused some people to question the quality control of the agile PM paradigm. Surprisingly, agile teams have not forgotten to mind the Ps and Qs of quality engineering--and not only continue to perform code inspections, but perform them more often. This results in even greater quality than traditional project management teams.
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...
Quality management concepts may not be welcome in a resource and cost-constrained environment. What you need is a secret plan to motivate workers to deliver better quality despite their rejection of common quality communications and programs.
Quality has to be one of the most elusive and vague concepts a person or organization can deal with. Perhaps this is because quality comes in many flavors and is so dependent upon its context. So how does IT develop a framework for quality if it is so indefinable?
|
"Enjoy yourself. It's later than you think." - Chinese Proverb |
