All I Need to Know About Manufacturing I Learned in Joe's Garage: World Class Manufacturing Made Simple

    Pink, author of TO SELL IS HUMAN and DRIVE "The Ballé books are a great way to get started or to speed up your pace of transformation, personal and organizational." —Jim Womack, Founder of Lean Enterprise Institute In their new business novel Lead With Respect, authors Michael and Freddy Ballé reveal the true power of lean: developing people through a rigorous application of proven tools and methods. And, in the process, creating the only sustainable source of competitive advantage—a culture of continuous improvement. In this engaging and insightful story, CEO Jane Delaney of Southcape Software discovers from her sensei Andy Ward that learning to lead with respect enables her to help people improve every day. “For us, lean is all about challenging yourself and each other to find the right problems, and working hard every day to engage people in solving them,” he says. Lead With Respect’s timely message brings a new understanding of lean. While lean has become essential for companies to compete in today’s global economy, most practitioners see it as a rigorous focus on process to produce higher quality goods and services—a limited understanding that fails to realize the true power of this approach. This new novel by the Ballés, the third in a series that includes Shingo Research Award-winners The Gold Mine and The Lean Manager, breaks new ground by sharing huge amounts of practical information on the most important yet least understood aspect of lean management: how to develop people through a rigorous application of lean tools. You’ll learn: • How to apply Lead With Respect attitudes to the lean tools you are using now so that you develop a truly sustainable lean culture. • What specific steps to follow to make lean leadership behaviors daily habits. • How to manage with respect through the emotion, conflict, tension, and self-doubt that you’ll face during a lean transformation.

    You’ll explore how four different teams used Kanban to make paradigm-changing improvements in software development. These teams were struggling with overwork, unclear priorities, and lack of direction. As you discover what worked for them, you’ll understand how to make significant changes in real situations.The four case studies in this book explain how to:Improve the full value chain by using Enterprise KanbanBoost engagement, teamwork, and flow in change management and operationsSave a derailing project with KanbanHelp an office team outside IT keep up with growth using KanbanWhat seems easy in theory can become tangled in practice. Discover why “improving IT” can make you miss your biggest improvement opportunities, and why you should focus on fixing quality and front-end operations before IT. Discover how to keep long-term focus and improve across department borders while dealing with everyday challenges. Find out what happened when using Kanban to find better ways to do work in a well-established company, including running multi-team development without a project office.You’ll inspire your team and engage management to make it easier to develop better products.

    It then identifies and describes the advantages of this system, which needs less of everything including time, human effort, inventories, and investment to produce products with fewer defects in smaller volumes at lower costs for fragmenting markets. The Machine That Changed the World even gave the system its name: lean.In the decade since its launch in the fall of 1990, The Machine That Changed the World has sold more than 600,000 copies in 11 languages and has introduced a whole generation of managers and engineers to lean thinking. No lean library is complete without this groundbreaking book."The fundamentals of this system are applicable to every industry across the globea[and] will have a profound effect on human society. It will truly change the world." - New York TimesPaperback / 1990 / 323 pages

    The way we think about leadership, for instance, has shifted radically from the genius of great entrepreneurs like Rockefeller, Carnegie and Ford, through leadership as a science, leadership that releases human potential, the leader as strategist and warrior, customer champion, globalist and shareholder advocate, to, more recently, leadership as stewardship of the environment. Hundreds of models have been developed to track, measure and forecast business solutions, but as fashions shift how can we apply them in real organizations that have to succeed outside the classroom? 10 Management Models is taken from the book, 100+ Management Models by the same authors.

    While it has been credited with improving productivity, slashing costs, and improving profit margins, it can cause much angst among employees who need to change the way they currently work and adhere to a new philosophy.  That's where characters Joe and Larry step in to deliver The Power of Six Sigma. This fictionalized tale simplifies a complicated topic through the lives of two typical business professionals. Contrary to other books on the subject, The Power of Six Sigma explains the overall philosophy of Six Sigma effectively in a nonthreatening way, taking no more than two hours to read.

    Long-term commitment to new learning and new philosophy is required of any management that seeks transformation. The timid and the fainthearted, and the people that expect quick results, are doomed to disappointment.According to W. Edwards Deming, American companies require nothing less than a transformation of management style and of governmental relations with industry. In Out of the Crisis, originally published in 1982, Deming offers a theory of management based on his famous 14 Points for Management. Management's failure to plan for the future, he claims, brings about loss of market, which brings about loss of jobs. Management must be judged not only by the quarterly dividend, but by innovative plans to stay in business, protect investment, ensure future dividends, and provide more jobs through improved product and service. In simple, direct language, he explains the principles of management transformation and how to apply them.Previously published by MIT-CAES

    It was the first such approach to bridge the gap between organization strategy and the individual. Now, in this revised and expanded new edition, Rummler and Brache reflect on the key needs of organizations faced with today's challenge of managing change. With multiple charts, checklists, hands-on tools and case studies, the authors show how they implemented their Performance Improvement methodology in over 250 successful projects with clients such as Hewlett-Packard, 3M, Shell Oil, and Citibank.

    W. Edwards Deming, a household name in Japan, became the prime catalyst behind the incredible success of Japanese industry. In fact, since 1951, the Deming Prize has been the most coveted and prestigious award among Japanese corporations, similar to the Malcolm Baldrige Award for quality in business in the United States. Today, Deming is finally becoming a household name in his own country. The lessons he has to teach American business are more urgent than ever. Just how different is the Deming Management Method? Compare just a few of the many differences in beliefs between conventional organizations and Deming organizations: Standard Company * Quality is expensive * Defects are caused by workers * Buy at lowest cost * Fear and reward are proper ways to motivate * Play one supplier off against another Deming Company * Quality leads to lower costs * Most defects are caused by the system * Buy from vendors committed to quality * Fear leads to disaster * Work with suppliers

    It helps readers to effectively apply all three types of maps to make work visible at the organization, process, and job/performer levels.

    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."

    This manual is aimed at everyone who works on interactive products in a design and development environment. It contains all of the basic information required for getting started with the project management method Scrum, but also offers a number of in-depth chapters looking at topics which even the most experienced Scrummers have trouble with on a daily basis. If you are experienced, you will find the advanced tips and tricks useful. If you are just considering Scrum, this book will most certainly get you enthusiastic.

    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

    Cash is needed and Alex Rogo's companies are to be put on the block. Alex faces a cruel dilemma. If he successfully completes the turnaround of his companies they can be sold for the maximum return: if he fails they will be closed down. Either way Alex and his team will be out of work. It looks like lose-lose, both for Alex and for his team. And as if he doesn't have enough to deal with, his two children have become teenagers. As Alex grapples with problems at work and at home, we begin to understand the full scope of Eli Goldratt's powerful techniques. It's Not Luck reveals more of the Thinking Process-techniques that consistently produce win-win solutions to seemingly impossible problems.

    Methodologies Aren't Enough2. Ambiguity in Stating Requirements3. Sources of Ambiguity4. The Tried but Untrue Use of Direct QuestionsPart II: Ways to Get Started5. Starting Points6. Context-Free Questions7. Getting the Right People Involved8. Making Meetings Work for Everybody9. Reducing Ambiguity from Start to FinishPart III: Exploring the Possibilities10. Idea-Generation Meetings11. Right-Brain Methods12. The Project's Name13. Facilitating in the Face of ConflictPart IV: Clarifying Expectations14. Functions15. Attributes16. Constraints17. Preferences18. ExpectationsPart V: Greatly Improving the Odds of Success19. Ambiguity Metrics20. Technical Reviews21. Measuring Satisfaction22. Test Cases23. Studying Existing Products24. Making Agreements25. EndingBibliographyIndex