![]() | ||
Project Quality PlanDepending on how closely your organisation follows project management methodologies you may well find yourself having to follow a project quality plan. The general idea is that this ensures there are clear checks and balances on the project which will result in a quality product being delivered. The good news is that this is not something which a project manager devises. It is usually the role of ITQA (IT Quality Assurance). The bad news is that you unfortunately need to deliver it!
![]() As you will see above, the type of things included when project quality planning are project artefacts which are basically project management documents. So things such as plans, project management requirements and test scripts would be within scope of a quality plan. The general idea is that a project quality plan is developed and approved before project initiation. Therefore you would include it whilst writing a project initiation document quality plan. However once project initiation is over, the fun really starts as the first ESA (End Stage Assessment) will need to be done. Basically what this means is that the ITQA person will need to check that all the product deliverables ie documentation is in order and has been completed so that the project can move onto the next phase. At this stage it will usually include:
There will be a number of other ESA's scheduled at key points in the project. Usually this will be after the project management requirements phase, the process of software development phase which should include the defining of the software requirements specification (SRS). You will also probably have ESA's during the software testing life cycle and finally on project closure. However please note there may be less or more of these depending on what you agree with your ITQA representative. After each ESA the ITQA person will write a report on their finding and traffic light it. Basically you are aiming for Green if posssible, but more realistically Amber for each stage. Project Quality Plan - TipSuccesssful project management is really hard to achieve in the real world. There is so much paperwork to fill in from the weekly project management report to managing project teams. Then there are the project cost controls which additionally need to be managed through the project lifecycle all which is a time consuming job.Therefore you need to minimise the amount of deliverables which are included within a project quality plan otherwise you and your team leads will be spending your entire time bogged down with paperwork and conducting project quality management, none of which will actually get your project delivered on time. After all you don't need perfection in order to launch, just good enough quality!
Sign Up for Our Free
|
Spare 2 Mins & Win an iPod ShuffleWe're running a survey to enable us to better focus our site and products. Please spare 2 minutes to answer our 6 questions and we'll enter you into a draw to win an iPod Shuffle. This way you help us to better help you. Go on, you know it makes sense!Click here for the Survey. Sign Up for Our Free
|
|
|
|
||
|
Return to top |
Home |
Project Management Basics | Project Management Life Cycle | Project Management Documents | Writing a Project Initiation Document (PID) | Project Management Report | Project Management Plans | Project Risk Management | Project Management Scope | Project Costs and Budget | Project Resource Management | Project Communications | Project Software Development | Sitemap | Contact Us | |
||
|
Original Content Copyright © 2009 My-Project-Management-Expert.com
All other content is in the public domain or is copyright by the credited author. | ||

