When Used for Software Development

When Used for Software Development

This is an extension of Deming's work. Deming's is definitely a top-down management style. Do not make changes in implementation unless the change has been vetted through change control which includes management participation.
This is compatible with waterfall, structured development and not so much so with an iterative or agile approach.
In the agile methodologies, change authority is delegated downward to small development teams with representatives of customer, quality, designers, programmers, who incrementally build up the new application building many prototypes progressively approaching what will be the final product.
This is tight loop within Planning and Executing while being observed and monitored. I suggest the agile team size be about 15 max. I recommend it for GUI type (web pages, use cases) projects.