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.
Introduction webinar for November Book Club: Project Management Simplified: A Step-by-Step Process by Barbara Karten
Save Time With Tools + Templates
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.
Need to document a non-conformance identified in a quality audit or other process review? This form helps you document the problem so that corrective action can be initiated. To be signed by the resident engineer, quality manager and contractor.
The project workbook allows project managers, team members, sponsors, and stakeholders to easily track and monitor project activities. Any of these worksheets can easily be broken out into separate documents. This workbook contains templates for Input Data, Minicharter, Status Report, Budget, CBA, Risks, Issues, Action Items, Milestones, WBS, Roster, R&R, RAM, RCM, A&C, Decision Log, Communication Plan, Stakeholder Analysis, Expectations, Change Log, DAL, PERT, Delphi, TimeSum and Qual Metrics.
This blank sample presentation can be used as a general project status report that includes an overall project status review; detailed tasks/modules review; and quality incidents/discussion of mitigation steps for continuous improvement.
Learn From Others
This article describes a useful technique for tracking project and task progress in situations where project resources are less than fully cooperative due to conditions outside project manager or sponsor control. It can also be applied with specialized or uniquely skilled resources that are challenged to accurately report progress due to communication issues--or are over-loaded with work for other projects or operations.
Agile is all about managing change, but every organization has a different rate of change. We generally think about agile as removing impediments to accelerate development and keep up with change. It also has an important role to play in placing constraints on change so that it doesn’t spin out of control. This article is a case study of how too much change can lower quality and lead to products that completely miss the mark.
For a long time, the constraints of time, scope and cost have been the key attributes that a project management professional had to handle effectively for project success. However, project success encompasses much more.
Many organizations consider quality improvement as a critical factor of success for competitiveness. The goal of continuous improvement attempts to not only meet customer requirements, but to also do it at the lowest cost. Values obtained as a result of the calculation need to be analyzed to prepare plans for improvement and set goals for reducing the cost of quality.
Not every project is a multi-year, billion-dollar implementation. Sometimes, you need to get something done in a few weeks or a few months…and the approach to these projects is much different.
Building information modeling (BIM) has grown tremendously in just a few years. Meanwhile, factors are pushing the construction world to innovate opportunities for improving efficiency and productivity. In this scenario in any project, the project manager has the overall responsibility for project success.
Addressing seven common risks can help companies better prepare for transformational programs, save time and money, and lay the groundwork for a positive return on investment.
The objective of governance is benefits realization, risk optimization and resource optimization. A good governance framework can help a performing organization develop a more holistic approach toward analytics.
The work breakdown structure is fundamental to project execution. When we expend insufficient time and develop inadequate detail on the WBS, the project will yield poor results and we can expect to see last-minute identification of critical elements. Here we look in greater detail at this essential tool.
When teams transition to agile development and the QA/testers continue to follow the same testing processes and tools they used before joining the agile team, you're asking for trouble. In this article, we contrast agile and traditional testing--and give an example of how a mind map can facilitate the testing process.
Ask a Question