Less inventory. The highest quality cars with the fewest defects of any competing manufacturer. In factories around the globe, Toyota consistently raises the bar for manufacturing, product development, and process excellence. The result is an amazing business success story: steadily taking market share from price-cutting competitors, earning far more profit than any other automaker, and winning the praise of business leaders worldwide.The Toyota Way reveals the management principles behind Toyota's worldwide reputation for quality and reliability. Dr. Jeffrey Liker, a renowned authority on Toyota's Lean methods, explains how you can adopt these principles--known as the "Toyota Production System" or "Lean Production"--to improve the speed of your business processes, improve product and service quality, and cut costs, no matter what your industry.Drawing on his extensive research on Toyota, Dr. Liker shares his insights into the foundational principles at work in the Toyota culture. He explains how the Toyota Production System evolved as a new paradigm of manufacturing excellence, transforming businesses across industries. You'll learn how Toyota fosters employee involvement at all levels, discover the difference between traditional process improvement and Toyota's Lean improvement, and learn why companies often think they are Lean--but aren't.

    This makes improving your business processes more critical than ever. In this book, you'll learn key steps for carrying out a business process improvement initiative, including how to:-Plan a business process improvement initiative-Analyze and redesign a current process that needs improvement-Obtain the resources needed to change a process-Develop a systematic approach for creating and implementing change

    It is based on the Toyota (lean) model, which combines operational excellence with value-based strategies to produce steady growth through a wide range of economic conditions. In contrast with the crash-and-burn performance of companies trumpeted by business gurus in the 1990s, the firms profiled in Lean Thinking -- from tiny Lantech to midsized Wiremold to niche producer Porsche to gigantic Pratt & Whitney -- have kept on keeping on, largely unnoticed, along a steady upward path through the market turbulence and crushed dreams of the early twenty-first century. Meanwhile, the leader in lean thinking -- Toyota -- has set its sights on leadership of the global motor vehicle industry in this decade. Instead of constantly reinventing business models, lean thinkers go back to basics by asking what the customer really perceives as value. (It's often not at all what existing organizations and assets would suggest.) The next step is to line up value-creating activities for a specific product along a value stream while eliminating activities (usually the majority) that don't add value. Then the lean thinker creates a flow condition in which the design and the product advance smoothly and rapidly at the pull of the customer (rather than the push of the producer). Finally, as flow and pull are implemented, the lean thinker speeds up the cycle of improvement in pursuit of perfection. The first part of this book describes each of these concepts and makes them come alive with striking examples. Lean Thinking clearly demonstrates that these simple ideas can breathe new life into any company in any industry in any country. But most managers need guidance on how to make the lean leap in their firm. Part II provides a step-by-step action plan, based on in-depth studies of more than fifty lean companies in a wide range of industries across the world. Even those readers who believe they have embraced lean thinking will discover in Part III that another dramatic leap is possible by creating an extended lean enterprise for each of their product families that tightly links value-creating activities from raw materials to customer. In Part IV, an epilogue to the original edition, the story of lean thinking is brought up-to-date with an enhanced action plan based on the experiences of a range of lean firms since the original publication of Lean Thinking. Lean Thinking does not provide a new management "program" for the one-minute manager. Instead, it offers a new method of thinking, of being, and, above all, of doing for the serious long-term manager -- a method that is changing the world.

    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.

    The hands of a pocket watch reveal the time of day without following every spring, cog, and movement behind the face. Similarly, an OPPM template reduces any project--no matter how large or complicated--to a simple one-page document, perfect for communicating to upper management and other project stakeholders. Now in its Second Edition, this practical guide, currently saving time and effort in thousands of organizations worldwide, has itself been simplified, then refined and extended to include the innovative AgileOPPM(TM).This Second Edition will include new material and updates including an introduction of the ground-breaking AgileOPPM(TM) and an overview of MyOPPM(TM) template builder, available on-line Includes references throughout the book to the affiliated sections in the Project Management Body of Knowledge (PMBOK(R)) Shows templates for the Project Management Office (PMO) This new and updated Second Edition will help you master the one-page approach to both traditional project management and Agile project management.(PMBOK is a registered marks of the Project Management Institute, Inc.)

    This internationally recognized standard provides the essential tools to practice project management and deliver organizational results.

    Usually this involves doing what other people have overlooked, as well as avoiding what is unproductive.He identifies five talents as essential to effectiveness, and these can be learned; in fact, they must be learned just as scales must be mastered by every piano student regardless of his natural gifts. Intelligence, imagination and knowledge may all be wasted in an executive job without the acquired habits of mind that convert these into results. One of the talents is the management of time. Another is choosing what to contribute to the particular organization. A third is knowing where and how to apply your strength to best effect. Fourth is setting up the right priorities. And all of them must be knitted together by effective decision-making. How these can be developed forms the main body of the book. The author ranges widely through the annals of business and government to demonstrate the distinctive skill of the executive. He turns familiar experience upside down to see it in new perspective. The book is full of surprises, with its fresh insights into old and seemingly trite situations.

    The Software Requirements Memory Jogger provides every member of your project team with the tools and techniques to foster communication between business and technical teams on the necessary requirements for producing successful software. The Software Requirements Memory Jogger will benefit all stakeholders at any organizational level involved in software development projects management team, practitioners, QA/QC personnel. - Explore practical steps, tips, and examples to help you develop and manage requirements - Follow the User Requirements Roadmap a toolkit of techniques for discovering and analyzing user requirements - Streamline communications between all requirements stakeholders - Learn how to write clear, concise requirements documents

    The tools and recipes in this book will help you uncover and solve hidden (and not-so-hidden) problems with your technology, your methodology, and those difficult "people" issues on your team.Project retrospectives help teams examine what went right and what went wrong on a project. But traditionally, retrospectives (also known as "post-mortems") are only helpful at the end of the project--too late to help. You need agile retrospectives that are iterative and incremental. You need to accurately find and fix problems to help the team today.Now, Derby and Larsen show you the tools, tricks, and tips you need to fix the problems you face on a software development project on an on-going basis. You'll see how to architect retrospectives in general, how to design them specifically for your team and organization, how to run them effectively, how to make the needed changes, and how to scale these techniques up. You'll learn how to deal with problems, and implement solutions effectively throughout the project--not just at the end.With regular tune-ups, your team will hum like a precise, world-class orchestra.ContentsForwardPrefaceIntroduction1. Helping your team inspect and adapt2. A retrospective custom-fit for your team3. Leading retrospectives4. Activities to set the stage5. Activities to gather data6. Activities to gather insights7. Activities to decide what to do8. Activities to close the retrospective9. Releases and project retrospectives10. Make it soA1. Facilitation suppliesA2. Debriefing activitiesA3. Activities quick reference matrixA4. Resources for learning facilitation skillsA5. Bibliography

    People need to be effective.Productivity books focus on doing more, Jim and Tonianne want you to focus on doing better. Personal Kanban is about choosing the right work at the right time. Recognizing why we do the things we do. Understanding the impact of our actions. Creating value - not just product. For ourselves, our families, our friends, our co-workers. For our legacy.Personal Kanban takes the same Lean principles from manufacturing that led the Japanese auto industry to become a global leader in quality, and applies them to individual and team work. Personal Kanban asks only that we visualize our work and limit our work-in-progress. Visualizing work allows us to transform our conceptual and threatening workload into an actionable, context-sensitive flow. Limiting our work-in-progress helps us complete what we start and understand the value of our choices. Combined, these two simple acts encourage us to improve the way we work and the way we make choices to balance our personal, professional, and social lives.Neither a prescription nor a plan, Personal Kanban provides a light, actionable, achievable framework for understanding our work and its context. This book describes why students, parents, business leaders, major corporations, and world governments all see immediate results with Personal Kanban.

    For decades, technology leaders have struggled to balance agility, reliability, and security. The consequences of failure have never been greater whether it's the healthcare.gov debacle, cardholder data breaches, or missing the boat with Big Data in the cloud.And yet, high performers using DevOps principles, such as Google, Amazon, Facebook, Etsy, and Netflix, are routinely and reliably deploying code into production hundreds, or even thousands, of times per day.Following in the footsteps of The Phoenix Project, The DevOps Handbook shows leaders how to replicate these incredible outcomes, by showing how to integrate Product Management, Development, QA, IT Operations, and Information Security to elevate your company and win in the marketplace."Table of contentsPrefaceSpreading the Aha! MomentIntroductionPART I: THE THREE WAYS1. Agile, continuous delivery and the three ways2. The First Way: The Principles of Flow3. The Second Way: The Principle of Feedback4. The Third Way: The Principles of Continual LearningPART II: WHERE TO START5. Selecting which value stream to start with6. Understanding the work in our value stream…7. How to design our organization and architecture8. How to get great outcomes by integrating operations into the daily work for developmentPART III: THE FIRST WAY: THE TECHNICAL PRACTICES OF FLOW9. Create the foundations of our deployment pipeline10. Enable fast and reliable automated testing11. Enable and practice continuous integration12. Automate and enable low-risk releases13. Architect for low-risk releasesPART IV: THE SECOND WAY: THE TECHNICAL PRACTICES OF FEEDBACK14*. Create telemetry to enable seeing abd solving problems15. Analyze telemetry to better anticipate problems16. Enable feedbackso development and operation can safely deploy code17. Integrate hypothesis-driven development and A/B testing into our daily work18. Create review and coordination processes to increase quality of our current workPART V: THE THRID WAY: THE TECHNICAL PRACTICES OF CONTINUAL LEARNING19. Enable and inject learning into daily work20. Convert local discoveries into global improvements21. Reserve time to create organizational learning22. Information security as everyone’s job, every day23. Protecting the deployment pipelinePART VI: CONCLUSIONA call to actionConclusion to the DevOps HandbookAPPENDICES1. The convergence of Devops2. The theory of constraints and core chronic conflicts3. Tabular form of downward spiral4. The dangers of handoffs and queues5. Myths of industrial safety6. The Toyota Andon Cord7. COTS Software8. Post-mortem meetings9. The Simian Army10. Transparent uptimeAdditional ResourcesEndnotes

    My easy-to-follow guide will enable you to make better decisions about how to organize your life in the electronic world. It is a book that you can revisit continuously to refine your process and keep you on track.

    Combining his candid insights with a rigorous analysis of Toyota's attempts at Lean production, Ohno's book explains how Lean principles can improve any production endeavor. A historical and philosophical description of just-in-time and Lean manufacturing, this work is a must read for all students of human progress. On a more practical level, it continues to provide inspiration and instruction for those seeking to improve efficiency through the elimination of waste.

    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.

    The author incudes OOD, UML, Design Patterns, Agile and XP methods with a detailed description of a complete software design for reusable programs in C++ and Java. Using a practical, problem-solving approach, it shows how to develop an object-oriented application -- from the early stages of analysis, through the low-level design and into the implementation. Walks readers through the designer's thoughts -- showing the errors, blind alleys, and creative insights that occur throughout the software design process. KEY TOPICS: Covers: Statics and Dynamics; Principles of Class Design; Complexity Management; Principles of Package Design; Analysis and Design; Patterns and Paradigm Crossings. Explains the principles of OOD, one by one, and then demonstrates them with numerous examples, completely worked-through designs, and case studies. Covers traps, pitfalls, and work arounds in the application of C++ and OOD and then shows how Agile methods can be used. Discusses the methods for designing and developing big software in detail. Features a three-chapter, in-depth, single case study of a building security system. MARKET: For Software Engineers, Programmers, and Analysts who want to understand how to design object oriented software with state of the art methods.