PDCA as a project tool

Mikael

Quite Involved in Discussions
Hi

Today I found a big headline "Continuous Improvements" and then the PDCA circle presented, though illustrated as a project management tool.

What do you think about PDCA (/PDSA) as a project management tool with start and end/finished ?

I never thought it was intended to be used as a project tool, but perhaps I got that wrong ?
 

RoxaneB

Change Agent and Data Storyteller
Super Moderator
I consider the PDCA descriptions to be higher level "titles" of activities within project management.

Plan = project charter, team, scope, deployment plan, measures for success
Do = execute to plan, collect data/results
Check = compare reality to plan, compare actual results to desired results
Act = lessons learned, project closure
 

Miner

Forum Moderator
Leader
Admin
I agree. PDCA is more of a conceptual tool used to illustrate the cycle of improvement. Project management requires much greater levels of detail. PDCA could be used to define phases of the project the same way that six sigma uses DMAIC, but that would be personal preference.
 

Mikael

Quite Involved in Discussions
My point is that the concept and purpose of "Continuous" is not to be considered a project?

Yes, I believe that there are tools which are a bit more nuance for greater levels of details and made for projects.

To what extent should the level be understood, some would say that you do this on the operative everyday tasks?
How loyal should you be to the order ?

Thanks
 
Last edited:

somashekar

Leader
Admin
My point is that the concept and purpose of "Continuous" is not to be considered a project?

Yes, I believe that there are tool which are a bit more nuance for greater levels of details and made for projects.

To what extent should the level be understood, some would say that you do this on the operative everyday tasks?
How loyal should you be to the order ?

Thanks
A project may end, but the learning from projects is continual.
PDCA can be understood on a macro scale for the total project as said by @RoxaneB.
However every activity of the project can be more systematically approached by smaller PDCA thinking
Perhaps even an e-mail writing can be approached this way....

P lan : Do I have all the data, information and direction, senders list (to, cc, bcc) to write out an e-mail or to reply to an e-mail
D o : Draft the e-mail
C heck : Check the e-mail for all correctness and completeness including grammar as necessary... and send (Do)
A ct : When the e-mail is responded, what else to do ? did it communicate well or raised more questions. Did the cc list persons have any comments. Could the e-mail have been better ? Can you Act to make the next e-mail more good than the previous ??
 

Mikael

Quite Involved in Discussions
somashekar, I would say that you have at least two sprints around the circle with the e-mail example. Thanks for being specific :)
 
Top Bottom