Written by Duke Okes
Duke Okes is an expert in Quality Management with 35 years of experience as a quality engineer, consultant and trainer. He has worked with dozens of companies in ten countries, and hundreds of organizations have attended his public workshops on auditing, quality systems, performance metrics and root cause analysis. He is an ASQ Fellow and certified by ASQ as a quality manager, engineer and auditor. He holds degrees in technology, business and education, and is a frequent conference speaker on quality management. He is the author of “Root Cause Analysis: The Core of Problem Solving and Corrective Action,” and has published dozens of articles on quality. He can be reached through his website.
Have your say!
00
Previous ArticleSolving the Information Technology Project PuzzleNext ArticleExporting Tasks from Project into Your Outlook Calendar
You May Also Like
1 Comment
Leave a Reply Cancel Reply
You must be logged in to post a comment.
Joan Tank
Agree – Every PMO should always be very clear on the overall objective and value added. So often I have watched PMOs report like a project plan on the work completed and next steps.