Tue.Apr 18, 2017

7 Steps to Build a Continuous Improvement Culture

LiquidPlanner

After World War II, new theories about quality began to be implemented. Many of these ideas were brought to Japan and embraced by the country as it rebuilt in the years after the war. These ideas would ultimately change manufacturing and the world. Continuous improvement” was one of these ideas.

A Project Team’s Guide to Data Conversion: Book Review & Interview with Dave Gordon

Project Bliss

For full disclosure, this article contains affiliate links. For more information, see my disclosure page. However, I have purchased this book myself and can honestly highly recommend it. .

2013 15

Trending Sources

Encountering PMO Failures and How to Combat Them

Project-Management.pm

Accomplishing tasks are one of the important goals of a project that are usually time-sensitive and otherwise somehow complicated. Large organizations have their own Project Management Office ( PMO ) that covers this area; organizing the best practices and methodologies of doing tasks and achieving them. These PMO practices and processes are sold to CIO for executive support in order to ensure that such practices are amended. This arrangement is wrong altogether. Why so?

Integrated product teams

Musings on Project Management

The US DoD has had the concept of the Integrated Product Team (IPT) for a couple of decades. If you search "Crosstalk, the journal of defense software engineering", you'll find zillions of articles that reference the IPT. And, if you search www.dau.mil, you'll also find a wealth of material. As the agile folks go about with multi-functional and persistent teams, they'll find that's an idea. dod Project Management

Task Management For Project Managers

How can project planning that stretches over months or years remain relevant and account for new ad-hoc activities that arrive every day?

More Trending

?A Quick Guide to 9 Essential Project Documents

Brad Egeland

​ What is going to be more successful - a project with two or three project documents or a project with hundreds of project documents? Unfortunately, there is no “one size fits all” answer to that question; a well-run project may need either and all of the in-between. Projects can vary in size, deliverables, life cycle, scope and that is just the tip of the variable iceberg. What is certain is that project documentation should be clear, relevant and up to date.

A Team Built for Collaboration [Guest Post]

Brightwork

Over 25 years ago, I was approached by a loyal client who wanted my team to build a complex application whose goal was an ideal end state (or maybe a dream state to be more accurate) for their business model but how to achieve it (its solution) was mostly undefined. The continued success of their business was threatened by technology and new competition and depended on the success of this very high risk project.