Project management is a multidisciplinary profession requiring not only knowledge and experience but also a lot of personal skills. A project is defined as: A temporary organisation that is created for the purpose of delivÂering one or more business products according to an agreed business case (Prince2 [1]). A project is executed on behalf of and by people. In fact it is all about people. This book is a holistic approach of project management which not only describes items such as risk management in a very practical way but also pays attention to the project impact and psychological part. Furthermore the challenges regarding outsourcing are described in order to reduce the amount of 'surprises'.

Project implementation aligned with strategic advancement is a challenging endeavor, particularly in an environment of increasing complexity and productivity issues. Your prime issue is to plan for right action in right time, in right manner, and for the right purpose. Your attention determines the experience you end up with, and the experience determines the outcomes you have reached. Therefore, you must control your attention to control arriving at your desired outcomes. William James, in his book The Principles of Psychology (Vol I, 1890), wrote a simple statement, “My experience is what I agree to attend to.” The statement is highly relevant even in the 21st century for managing high productivity through “attention management.” This third volume provides areas for attention management and focuses on diversity, team building, meaningfulness, and growing to leadership, all of which are essentially required for maximizing and cultivating the real benefits with application of project management approach in business and industry.

Engineering and Product Development Management is a practical guide to the components of engineering management, using a holistic approach. It will help engineers and managers understand what they have to do to improve the product development process by deploying new technology and new methods of working in concurrent teams. The book takes elements from six well known and understood bodies of knowledge and integrates them into a holistic approach: integrated product development, project management, process management, systems engineering, product data management, and organizational change management. These elements are framed within an overall enterprise-wide architecture. The techniques discussed in this book work for both huge multinational organizations and smaller enterprises. The emphasis throughout is on practical tools which will be invaluable for engineers, managers, and consultants responsible for project and product development.

Scrum is an agile framework for completing complex projects. This book gives examples, tools, and tricks to do Scrum well. For each trick it is explained why it helps. The practices themselves may be worth trying, but by understanding why it works the readers will be able to come up with their own ideas that work better in their organization and situation. All the practical examples in this book have helped someone, some where to become a part of a better Scrum team. Scrum’s motto is: “Inspect and Adapt”; change small things one at a time and see what works. Scrum is not done by project leaders or managers, but really by the teams—to succeed in an organization, the teams must do Scrum well. If the teams do Scrum well, the whole organization will benefit from it. Scrum helps a team self-organize, which fits in well with developers, who usually don’t like to be micromanaged. At the same time, Scrum can scale: Self-organized teams work together well, and one manager doesn’t have to manage all the people. The lessons from this book help Scrum teams develop into autonomous, proud, and independent teams. Often teams fail to become powerful enough to change the organization, so they cannot perform to their full potential. A good team can lead the stakeholders into trusting them. They will then make plans based on the team’s release planning instead of making roadmaps out of thin air, and thus make the organization much more predictable.

There's no available information at this time. Author will provide once information is available.

Benefits realization is the common thread that runs from organizational strategy through project deliverables that contribute benefits. Yet, according to PMI's 2018 Pulse of the Profession Report: Success in Disruptive Times, only one in three organizations report high benefits realization maturity. This practice guide provides a comprehensive look at the topic of benefits realization in of portfolio, program, and project management. It will help readers tackle this important topic and drive more successful outcomes and better strategic alignment in your organization. Inside this practice guide readers will find: standardized definitions for benefits realization, benefits realization management and associated benefits realization terms; the core principles of benefits realization; the benefits realization management life cycle from organizational mission, vision, and strategy through project deliverables and success measurement, and how it contributes to the expected benefits and value that the organization intends to realize; and a framework and guidance to help practitioners manage benefits realization in organizational project management and portfolio, program, and project management. As with all PMI standards and publications, this practice guide also aligns with our other standards including: A Guide to the Project Management Body of Knowledge (PMBOK Guide)®—Sixth Edition; The Standard for Program Management—Fourth Edition; and The Standard for Portfolio Management—Fourth Edition.

Innoliteracy: From Design Thinking to Tangible Change encourages you to allocate resources in the earliest phases of your next development or change project—to the fuzzy front end, where the problem is unveiled and understood, scoped, defined, and challenged, and where the roadmap for how to introduce something new or replace something existing with something better is drawn. The book is based on a series of reflections, experiences, observations, and anecdotes as well as a guide to a better development process, referring to examples, case studies, and existing literature and research. Innoliteracy is for anyone who is engaged in—or even just curious about—change and development processes, especially how they are made more stakeholder-focused, thoroughly framed and reframed, and how one makes sure that the most relevant and imminent problem is addressed.