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.
Find answers to these questions and more in this Quality Practice Area. If you are new to Quality, take advantage of the resources below and don't be shy about commenting or asking questions. If you're a seasoned pro, help others out and become an influencer. We welcome contributions from all sources and the more you participate, the more visible you become. Let us help you move down the road from "giver of sage advice" to "Thought Leader".
| Network:123 |
| Network:0 |
| Network:1909 |
| Network:145 |
| Network:1929 |
| Network:915 |
| Network:599 |
| Network:402 |
| Network:3262 |
| Network:2208 |
Lean practices have revolutionized the manufacturing industry; the application of lean principles have also had a big impact in construction, IT, services and health care. In this webinar we will share some of those principles and practices and give examples how they can be used in a large variety of projects.
Has your organization or quality management team gone through the effort of adopting the Plan, Do, Check, Act (PDCA) strategy for making improvements to various processes? This talk will dive into what it really takes for an organization, or even a department within, to make true gains from the PDCA process.
While numerous key performance indicators (KPIs) typically influence IT projects generally, the benefit of tracking all of them may be outweighed by the cost to do so. Therefore, each project must carefully select and manage those KPIs most relevant to its specific situation. This sample template can be used to define KPIs; also included is a table with examples of possible KPIs for each of the previously defined project-critical success factors (PCSFs) and a metric (measure and dimension) for each KPI. Use in conjunction with the article Determining IT Project Health.
Use this assessment to determine if a system is ready to go to production. It is a series of spreadsheets that allow different modules to have both ticket tracking (bugs) and other criteria; then based on thresholds, the system can be assessed as ready or not ready to go live.
This deliverable relates both a project charter and a project record form to be used during the initiating phase of a given project. It gives a high-level overview of the project including the budget, scope, resources and roles and responsibilities.
This single-page PDF flowchart shows the workflow diagram that clearly illustrates the stages of a typical project, which consists of relations between all parts of the project cycle. Workflow diagrams are used to represent the transferring of deliverables during the project phases, to study and analyze the working processes, and to optimize a workflow. Use it as a visual refresher or teaching tool.
Do you know how to thoroughly and efficiently test the software product you have so painstakingly built? Don't risk delivering a faulty software product due to insufficient or unfocused testing. Use this list to check whether you are testing smart--or just testing!
Thanks to pressure on prices and the need for increased project capacity, IT project delivery has been transformed into a complex model that utilizes both onshore and offshore activities. What delivery model is best for your needs: horizontal or vertical?
When you think of the leaders who look at your status reports as users, the look and feel of the report you use may be inadequate. Give leaders the information they need in a compelling manner by using design thinking to make improvements in how information is presented.
Project-status reporting is intended to enable decision makers to make informed decisions that will increase the chances of achieving a favorable outcome. The process of establishing an effective and proactive reporting system that ensures engagement of the project executive team is discussed here.
Our webinar Lean-Driven Project Management shared some lean principles and practices and gave examples of how they could be used in a large variety of projects. Here, the presenter continues the conversation with this Q&A session that followed his presentation.
Instead of making agile a tool to speed up development and manufacturing, many organizations use it as a means to cut corners—which often leads to loss of time due to rework, or to inferior quality being delivered.
Traditional testing practices are the hands that slow agile teams to a stagnant, waterfall state. Testing itself isn’t bad or anti-agile...but how you think about testing can make or break your agile success.
Designing complexity out of the project process begins with ensuring that needless complexity is kept clear of things. Let’s look at some of the drivers that tend to introduce needless complexity into the project management process...
What is the ideal tester-to-developer ratio for the development team? On the surface, this might sound like a perfectly reasonable question—one that should be easy for an experienced practitioner to answer. However, when you look deeper into the question, you will see that it has layers of underlying assumptions—including ones about corporate culture, politics and the likely skills of their own staff.
Transferring a team deliverable from continent to continent carries with it additional risks in addition to those expected from co-located workforces. There are planning and facilitation tactics you can use to mitigate these risks—and even build improved collaboration in the process.
Ask a Question |
Discussion Rules |
|
"If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time--a tremendous whack." - Winston Churchill |
