Book picks similar to
Critical Chain Project Management by Lawrence P. Leach
management
project-management
business
theory-of-constraints
The Standard for Portfolio Management
Project Management Institute - 2006
Product DetailsPaperback: 79 pagesPublisher: Project Management Inst (May 31, 2006)Language: EnglishISBN-10: 1930699905ISBN-13: 978-1930699908Product Dimensions: 10.9 x 8.5 x 0.3 inchesShipping Weight: 1.2 poundsAverage Customer Review: 3.7 out of 5 stars See all reviews (6 customer reviews)Amazon Best Sellers Rank: #372,351 in Books (See Top 100 in Books)
Velocity: Combining Lean, Six Sigma and the Theory of Constraints to Achieve Breakthrough Performance - A Business Novel
Dee Jacob - 2009
Now, from the AGI-Goldratt Institute and Jeff Cox, the same creative writer who co-authored The Goal, comes VELOCITY, the book that reveals how to achieve outstanding bottom-line results by integrating the world's three most powerful continuous improvement disciplines: Lean, Six Sigma, and Goldratt's Theory of Constraints. Used by the United States Navy and United States Marine Corps to dramatically improve some of the most complex, logistically vast supply chains in the world, the VELOCITY APPROACH draws on the strengths of all three disciplines to deliver breakthrough performance gains. In physics, speed with direction is velocity; in business, the application of VELOCITY means your organization can achieve operational speed with strategic direction to outmaneuver competitors, gain loyalty with customers, and rapidly build sustainable earnings growth -- in as little as one or two business quarters. Dee Jacob and Suzan Bergland, two princi-pals of AGI, have been teaching the concepts, techniques, and tools of VELOCITY to major corporations, including Procter & Gamble, ITT, and Northrop Grumman, for years. Now they unlock the door for you to see how to apply their insights and methods to your organization -- be it business, not-for-profit, manufacturing, or service based -- in order to shorten lead times, slash inventories, reduce production variability, and increase sales. Writer Jeff Cox returns with the vivid, realistic style that made The Goal so readable yet so edifying. Thrust into the presidency of the subsidiary company where she has managed sales and marketing, Amy Cieolara is mandated by her corporate superiors to implement Lean Six Sigma (LSS) in order to appease a key customer. Assigned to help her is LSS Master Black Belt Wayne Reese, installed as her operations manager. But as time goes on and corporate pressure mounts, Amy finds she has to start thinking for herself -- and learning from everyone around her -- and she arrives at the series of steps that form the core of the VELOCITY APPROACH. VELOCITY offers keen insight into the human and organizational factors that so often derail growth while teaching you proven, practical techniques for restarting and revving up the internal engines of your company to reach new levels of success. Colorful characters, believable situations, and everything from dice games to AGI's "reality tree" techniques make this business novel a vital resource for everyone seeking to deliver business improvement in these challenging economic times -- and far into the future.
Earned Value Project Management
Quentin W. Fleming - 1996
In its most simple form, earned value equates to fundamental project management. This is not a new book, but rather it is an updated book. Authors Quentin Fleming and Joel Koppelman have made some important additions. In many cases, there will be no changes to a given section. But in other sections, the authors have made substantial revisions to what they had described in the first edition. Fleming and Koppelman’s goal remains the same with this update: describe earned value project management in its most fundamental form, for application to all projects, of any size or complexity. Writing in an easy-to-read, friendly, and humorous style characteristic of the best teachers, Fleming and Koppelman have identified the minimum requirements that they feel are necessary to use earned value as a simple tool for project managers. They have also witnessed the use of simple earned value on software projects, and find it particularly exciting. Realistically, a Cost Performance Index (CPI) is the same whether the project is a multibillion-dollar high-technology project, or a simple one hundred thousand-dollar software project. A CPI is a CPI … period. It is a solid metric that reflects the health of the project. In every chapter, Fleming and Koppelman stick with using simple stories to define their central concept. Their project examples range from peeling potatoes to building a house. Examples are in round numbers, and most formulas get no more complicated than one number divided by another. Earned Value Project Management—Second Edition may be the best-written, most easily understood project management book on the market today. Project managers will welcome this fresh translation of jargon into ordinary English. The authors have mastered a unique "early-warning" signal of impending cost problems in time for the project manager to react.
Prince2 for Dummies
Nick Graham - 2008
Fully updated with the 2009 practice guidelines, this book will take you through every step of a project - from planning and establishing roles to closing and reviewing - offering practical and easy-to-understand advice on using PRINCE2. It also shows how to use the method when approaching the key concerns of project management, including setting up effective controls, managing project risk, managing quality and controlling change. PRINCE2 allows you to divide your project into manageable chunks, so you can make realistic plans and know when resources will be needed. PRINCE2 For Dummies, 2009 Edition provides you with a comprehensive guide to its systems, procedures and language so you can run efficient and successful projects.PRINCE2 For Dummies, 2009 Edition includes: Part I: How PRINCE Can Help You - Chapter 1: So What's a Project Method and Why Do I Need to Use One? - Chapter 2: Outlining the Structure of PRINCE2 - Chapter 3: Getting Real Power from PRINCE2Part II: Working Through Your Project - Chapter 4: Checking the Idea Before You Start - Chapter 5: Planning the Whole Project: Initiation - Chapter 6: Preparing for a Stage in the Project - Chapter 7: Controlling a Stage - Chapter 8: Building the Deliverables - the Work of the Teams - Chapter 9: Finishing the Project - Chapter 10: Running Effective Project BoardsPart III: Help with PRINCE Project Management - Chapter 11: Producing and Updating the Business Case - Chapter 12: Deciding Roles and Responsibilities - Chapter 13: Managing Project Quality - Chapter 14: Planning the Project, Stages, and Work Packages - Chapter 15: Managing Project Risk - Chapter 16: Controlling Change and Controlling Versions - Chapter 17: Monitoring Progress and Setting Up Effective ControlsPart IV: The Part of Tens - Chapter 18: Ten Ways to Make PRINCE Work Well - Chapter 19: Ten Tips for a Good Business Case - Chapter 20: Ten Things for Successful Project Assurance Part V: Appendices - Appendix A: Looking into PRINCE Qualifications - Appendix B: Glossary of the Main PRINCE2 Terms
Scrappy Project Management: The 12 Predictable and Avoidable Pitfalls That Every Project Faces
Kimberly Wiefling - 2007
Unfortunately most of these are PREDICTABLE and AVOIDABLE. Tact and diplomacy can only get you so far in the wild and wacky world of project work. A combination of outrageous creativity, sheer bravado and nerves of steel will serve you far better than any fancy-schmancy Microsoft Project Gantt chart!'Scrappy Project Management' is about what REALLY happens in the project environment, how to survive it, and how to make sure that your team avoids the predictable and avoidable pitfalls that every project faces.
Pmp: Project Management Professional: Study Guide
Kim Heldman - 2002
This new edition of the best-selling PMP: Project Management Professional Study Guide covers the 2005 updates to both the Project Management Body of Knowledge (PMBOK) and the PMP exam. Author Kim Heldman presents the material in a clear and accessible manner, taking you through the process groups in their logical order so you understand the parts and the whole equally well.KEY TOPICS INCLUDE:Project Initiation. Determining project goals, determining deliverables, determining process outputs, documenting constraints, documenting assumptions, defining strategies, producing formal documentation.Project Planning. Refining a project, creating a WBS, developing a resource management plan, determining resource requirements, defining budgets, refining time and costs estimates, establishing project controls, obtaining plan approval.Project Execution. Committing and implementing resources, managing and communicating progress, implementing quality assurance procedures.Project Control. Measuring performance, refining control links, taking corrective action, evaluating effectiveness of corrective action, ensuring plan compliance, reassessing control plans, responding to risk event triggers, monitor project activity.Project Closing. Obtaining acceptance of deliverables, documenting lessons learned, facilitating closure, preserving product records and tools, releasing resources.Professional Responsibility. Ensuring integrity, contributing to knowledge base, balancing stakeholder interests, respecting differences.
The Deadline: A Novel about Project Management
Tom DeMarco - 1997
Rizzoli- Ex-General Markov- Abdul Jamid- The Sinister Minister Belok- The Numbers Man- QuickerStill- Morovia's First Programmer- Think Fast!- Planning for the Summer Games- The Guru of Conflict Resolution- Maestro Diyeniar- Interlude- Part and Whole- Standing on Ceremony- Endgame Begins- The Year's Hottest IPO- Passing Through Riga on the Way Home
Identifying and Managing Project Risk: Essential Tools for Failure-Proofing Your Project
Tom Kendrick - 2003
Important projects tend to be time constrained, pose huge technical challenges, and suffer from a lack of adequate resources. It's no wonder that project managers are increasingly focusing their attention on risk identification.Identifying and Managing Project Risk is a practical guide to minimizing the possibility of failure in critical projects. The book takes readers step by step through every phase of a project, showing them how to consider the possible risks involved at every point in the process. Relevant figures and diagrams support the text and illustrate key scenarios. At the end of each chapter is an analysis of how the principles just discussed applied to a supreme example of what many once considered a truly impossible project: the building of the Panama Canal.Packed with real-world information, this book is essential reading for any project manager seeking to complete projects smoothly and successfully."
Critical Chain
Eliyahu M. Goldratt - 1997
The novel aims to provoke readers to examine and reassess their business practices and transform the thinking and actions of managers.
Making Things Happen: Mastering Project Management
Scott Berkun - 2001
Each essay distills complex concepts and challenges into practical nuggets of useful advice, and the new edition now adds more value for leaders and managers of projects everywhere. Based on his nine years of experience as a program manager for Internet Explorer, and lead program manager for Windows and MSN, Berkun explains to technical and non-technical readers alike what it takes to get through a large software or web development project. Making Things Happen doesn't cite specific methods, but focuses on philosophy and strategy. Unlike other project management books, Berkun offers personal essays in a comfortable style and easy tone that emulate the relationship of a wise project manager who gives good, entertaining and passionate advice to those who ask. Topics in this new edition include:How to make things happenMaking good decisionsSpecifications and requirementsIdeas and what to do with themHow not to annoy peopleLeadership and trustThe truth about making datesWhat to do when things go wrongComplete with a new forward from the author and a discussion guide for forming reading groups/teams, Making Things Happen offers in-depth exercises to help you apply lessons from the book to your job. It is inspiring, funny, honest, and compelling, and definitely the one book that you and your team need to have within arm's reach throughout the life of your project. Coming from the rare perspective of someone who fought difficult battles on Microsoft's biggest projects and taught project design and management for MSTE, Microsoft's internal best practices group, this is valuable advice indeed. It will serve you well with your current work, and on future projects to come.
Goldratt's Theory of Constraints
H. William Dettmer - 1997
Goldratt's Theory of Constraints (TOC), a system improvement philosophy focusing on logic and identifying the weakest link in an organization in order to, as the author states, manage the living daylights out of it. Dettmer introduces TOC, defining the concepts of
Impact Mapping: Making a Big Impact with Software Products and Projects
Gojko Adzic - 2012
The result is a tremendous amount of time and money wasted due to wrong assumptions, lack of focus, poor communication of objectives, lack of understanding and misalignment with overall goals. There has to be a better way to deliver!This handbook is a practical guide to impact mapping, a simple yet incredibly effective method for collaborative strategic planning that helps organisations make an impact with software. Impact mapping helps to create better plans and roadmaps that ensure alignment of business and delivery, and are easily adaptable to change. Impact mapping fits nicely into several current trends in software product management and release planning, including goal-oriented requirements engineering, frequent iterative delivery, agile and lean software methods, lean startup product development cycles, and design thinking.Who is this book for?The primary audience of this book are senior people involved in building software products or delivering software projects, from both business and delivery sides. This includes business sponsors and those whose responsibilities include product ownership, project oversight or portfolio management, architecture, business analysis, quality improvement and assurance and delivery. - Business people assigned to software projects will learn how to communicate their ideas better.- Senior product or project sponsors will learn how to communicate their assumptions more effectively to delivery teams, how to engage delivery teams to make better strategic decisions, and how to manage their project portfolio more effectively.- Delivery teams that are already working under the umbrella of agile or lean delivery methods, and more recently lean startup ideas, will learn how to better focus deliverables and engage business sponsors and users.- Delivery teams moving to agile or lean delivery methods will get ideas on how to address some common issues with scaling these practices, such as creating a big picture view, splitting work into small chunks that still have business value and reporting progress more meaningfully.About the authorGojko Adzic is a strategic software delivery consultant who works with ambitious teams to improve the quality of their software products and processes. Gojko won the 2012 Jolt Award for the best book, was voted by peers as the most influential agile testing professional in 2011, and his blog won the UK Agile Award for the best online publication in 2010. To get in touch, write to gojko@neuri.co.uk or visit http://gojko.net.
Agile Product Management with Scrum: Creating Products That Customers Love
Roman Pichler - 2008
He describes a broad range of agile product management practices, including making agile product discovery work, taking advantage of emergent requirements, creating the minimal marketable product, leveraging early customer feedback, and working closely with the development team. Benefitting from Pichler's extensive experience, you'll learn how Scrum product ownership differs from traditional product management and how to avoid and overcome the common challenges that Scrum product owners face. Coverage includesUnderstanding the product owner's role: what product owners do, how they do it, and the surprising implicationsEnvisioning the product: creating a compelling product vision to galvanize and guide the team and stakeholdersGrooming the product backlog: managing the product backlog effectively even for the most complex productsPlanning the release: bringing clarity to scheduling, budgeting, and functionality decisionsCollaborating in sprint meetings: understanding the product owner's role in sprint meetings, including the dos and don'tsTransitioning into product ownership: succeeding as a product owner and establishing the role in the enterprise This book is an indispensable resource for anyone who works as a product owner, or expects to do so, as well as executives and coaches interested in establishing agile product management.
Essential Scrum: A Practical Guide to the Most Popular Agile Process
Kenneth S. Rubin - 2012
Leading Scrum coach and trainer Kenny Rubin illuminates the values, principles, and practices of Scrum, and describes flexible, proven approaches that can help you implement it far more effectively. Whether you are new to Scrum or years into your use, this book will introduce, clarify, and deepen your Scrum knowledge at the team, product, and portfolio levels. Drawing from Rubin's experience helping hundreds of organizations succeed with Scrum, this book provides easy-to-digest descriptions enhanced by more than two hundred illustrations based on an entirely new visual icon language for describing Scrum's roles, artifacts, and activities.
Essential Scrum
will provide every team member, manager, and executive with a common understanding of Scrum, a shared vocabulary they can use in applying it, and practical knowledge for deriving maximum value from it.
Management 3.0: Leading Agile Developers, Developing Agile Leaders
Jurgen Appelo - 2010
Unfortunately, reliable guidance on Agile management has been scarce indeed. Now, leading Agile manager Jurgen Appelo fills that gap, introducing a realistic approach to leading, managing, and growing your Agile team or organization. Writing for current managers and developers moving into management, Appelo shares insights that are grounded in modern complex systems theory, reflecting the intense complexity of modern software development. Appelo's Management 3.0 model recognizes that today's organizations are living, networked systems; and that management is primarily about people and relationships. Management 3.0 doesn't offer mere checklists or prescriptions to follow slavishly; rather, it deepens your understanding of how organizations and Agile teams work and gives you tools to solve your own problems. Drawing on his extensive experience as an Agile manager, the author identifies the most important practices of Agile management and helps you improve each of them. Coverage includes - Getting beyond "Management 1.0" control and "Management 2.0" fads - Understanding how complexity affects your organization - Keeping your people active, creative, innovative, and motivated - Giving teams the care and authority they need to grow on their own - Defining boundaries so teams can succeed in alignment with business goals - Sowing the seeds for a culture of software craftsmanship - Crafting an organizational network that promotes success - Implementing continuous improvement that actually works Thoroughly pragmatic-and never trendy-Jurgen Appelo's Management 3.0 helps you bring greater agility to any software organization, team, or project.