A key component of successful project management is the ability to glean key learnings from the experience throughout the lifecycle of the project, as well as at its conclusion. However, in practice, the lessons learned from a specific project are rarely incorporated into an organization's overall policies and procedures. Without a concerted effort to reflect on specific project learning's and a designated process to implement them across the organization, lessons are lost, mistakes are repeated and opportunities for operational efficiency are missed.
As tech giants and startups disrupt every market, those who master large-scale software delivery will define the economic landscape of the 21st century, just as the masters of mass production defined the landscape in the 20th. Unfortunately, business and technology leaders are woefully ill-equipped to solve the problems posed by digital transformation. At the current rate of disruption, half of S&P 500 companies will be replaced in the next ten years. A new approach is needed. In Project to Product, Value Stream Network pioneer and technology business leader Dr. Mik Kersten introduces the Flow Framework—a new way of seeing, measuring, and managing software delivery. The Flow Framework will enable your company’s evolution from project-oriented dinosaur to product-centric innovator that thrives in the Age of Software. If you’re driving your organization’s transformation at any level, this is the book for you.
How do you determine if your project was a success (beyond being within budget and completed on time)? How do you determine the impact of a project? How do you capture valuable knowledge from a current or past project to enhance future programs? The answer to all three questions is through project lessons learned. Recipient of the 2012 PMI David I.
For some organizations, Lessons Learned (LL) is an informal process of discussing and recording project experiences during the closure phase. For others, LL is a formal process that occurs at the end of each phase of a project. Regardless of when they are performed, if you are a project team member, chances are you will soon be required to present an evaluation of your project using Lessons Learned. Presenting new information that updates the award-winning first edition, The Basics of Project Evaluation and Lessons Learned, Second Edition supplies practical guidance on conducting project Lessons Learned. The first edition won the Project Management Institute's (PMI®) David I. Cleland Project Management Literature Award. Following in the footsteps of its popular predecessor, this second edition provides an easy-to-follow, systematic approach to conducting Lessons Learned on a project. Updated to align with the PMBOK® Guide, Fifth Edition Includes three new chapters—PRINCE2®, Agile Retrospectives, and Knowledge Transfer— in response to information requests from readers of the first edition from around the world Enhanced with valuable new resources in the Project Evaluation Resource Kit (PERK) found on the free CD included in the back of the book, including a fully functional MS Access Lessons Learned Database The research in this book is based on four years of doctoral dissertation research and is supported by renowned experts in the field of evaluation. The concepts covered are applicable to all types of organizations that implement projects and need to conduct Lessons Learned. Providing tools and techniques for active engagement, the text is founded on the principles of conducting project evaluations as recommended by the Project Management Institute (PMI), the world’s leading not-for-profit membership association for the project management profession, and PRINCE2® (Project in Controlled Environments version 2), a major governing body of project management. Simplifying and formalizing the methodology of conducting LL in projects, the contents of this book will help organizations, large and small, more effectively implement processes and systems to support effective LL. The text is supported by a Project Evaluation Resource Kit (PERK), which is found in CD format at the back of the book.
For some organizations, Lessons Learned (LL) is an informal process of discussing and recording project experiences during the closure phase. For others, LL is a formal process that occurs at the end of each phase of a project. Regardless of when they are performed, if you are a project team member, chances are you will soon be required to present
"Lessons Learned" is a knowledge management approach for organizational learning and improved performance and productivity. However beneficial this approach is, few organizations have been able to implement the processes necessary for organizational success. Utilizing Evidence-Based Lessons Learned for Enhanced Organizational Innovation and Change links the theoretical foundation of the lessons learned approach with current tools and evidence-based research in support of organizational development. Outlining best practices and emerging research in organizational learning, this publication is ideal for project managers, academicians, researchers, and upper-level students looking to implement these processes into their project management cycle, particularly in the risk management and quality control processes.
Softwaretests stellen eine kritische Phase in der Softwareentwicklung dar. Jetzt zeigt sich, ob das Programm die entsprechenden Anforderungen erfüllt und sich auch keine Programmierungsfehler eingeschlichen haben. Doch wie bei allen Phasen im Software-Entwicklungsprozess gibt es auch hier eine Reihe möglicher Fallstricke, die die Entdeckung von Programmfehlern vereiteln können. Deshalb brauchen Softwaretester ein Handbuch, das alle Tipps, Tricks und die häufigsten Fehlerquellen genau auflistet und erläutert, damit mögliche Testfehler von vornherein vermieden werden können. Ein solches Handbuch ersetzt gut und gerne jahr(zehnt)elange Erfahrung und erspart dem Tester frustrierende und langwierige Trial-und-Error-Prozeduren. Chem Kaner und James Bach sind zwei der international führenden Experten auf dem Gebiet des Software Testing. Sie schöpfen hier aus ihrer insgesamt 30-jährigen Erfahrung. Die einzelnen Lektionen sind nach Themenbereichen gegliedert, wie z.B. Testdesign, Test Management, Teststrategien und Fehleranalyse. Jede Lektion enthält eine Behauptung und eine Erklärung sowie ein Beispiel des entsprechenden Testproblems. "Lessons Learned in Software Testing" ist ein unverzichtbarer Begleiter für jeden Software Tester.
No project management training? No problem! In today’s workplace, employees are routinely expected to coordinate and manage projects. Yet, chances are, you aren’t formally trained in managing projects—you’re an unofficial project manager. FranklinCovey experts Kory Kogon and Suzette Blakemore understand the importance of leadership in project completion and explain that people are crucial in the formula for success. This updated and revised edition of Project Management for the Unofficial Project Manager offers practical, real-world insights for effective project management and guides you through the essentials of the value, people, and project management process: Scope Plan Engage Track and Adapt Close If you’re struggling to ensure multiple projects are finished with high value and on time, this book is for you. If you manage projects without the benefit of a team, this book is also for you. Change the way you think about project management—"project manager" may not be your official title, but with the right strategies, you can excel in this project economy.
Practitioners operate in a necessary reality. We work in a space where project performance is above theory or methodology. In the best environments, delivery and an affirmative culture are what matter most. In the worst, it is politics and survival. In any environment we are challenged to adopt best practices and adapt our style to the environment in which the project is occurring. This is a book about those best practices and practitioner experiences. It is a must have reference and guide book for project managers, general managers, business leaders and project management researchers. This book is the result of the hard work and dedication of more than 35 authors from more than 15 countries across four continents. It brings a diversity of experience, professional and personal. It includes practitioners, leading academics, renowned theorists and many who straddle those roles. The chapters cover experiences in software, large scale infrastructure projects, finance and health care, to name a few. The chapters themselves take many forms. Check out the table of contents to get a deeper sense of the topics included. All provide real-world guidance on delivering high performing projects and show you how to build, lead and manage high performing teams. The Practitioners Handbook of Project Performance is complete in itself. It can also be an enticing start to an ongoing dialogue with the authors and a pleasurable path to get deeper into the subject of project performance. Find your favorite place to begin learning from these chapters, to begin taking notes and taking away nuggets to use in your everyday. But don’t stop there. Contact information and further resources for this diverse team of experts authors are found throughout. The Practitioners Handbook is a modern guide to the leading edge of project performance management and a path to the future of project delivery.
