How-to guidance for defining and implementing a complex projectperformance environment Sharing his forty-five years of project management experience,best-selling author and industry guru Robert Wysocki presents astraightforward, enlightening, and pragmatic guide to help seniormanagers make the transition to an organization that profits andthrives on complexity. The first book to discuss practical projectmanagement mitigation strategies, Executive's Guide to ProjectManagement presents easy-to-implement infrastructures andprocesses that will ensure the continued success of yourorganization and maximize your investment of every project. It's time for your senior management team to take back controlof your investments in projects and programs. Executive's Guideto Project Management shows you how to cultivate your part ofthe organization so that it can respond to a changing projectenvironment with the infrastructure to support the project andprogram investment decisions.
Pro tip (not from this book): it's not by making them more complex.
See the title:
> Executive's Guide to Project Management: Organizational Processes and Practices for Supporting Complex Projects
Uses "project" twice. Aren't these synonyms?: management; process; practice; supporting. Do executives exist outside of organisations? Isn't this redundant? Actually do executive have any other role to do except manage?
If you were actually trying to manage complexity and therefore keep things lean you'd cull that redundancy. See this is all that's needed:
> Executive's Guide to Complex Projects
(and Senior Management Teams) cos gee he uses the term SMT often.
This encapsulates this extremely self-indulgent book.