It gives you the tools to address a wider range of important VSM issues than any other such book, including the psychology of change, leadership, creating teams, building consensus, and charter development.Karen Martin is principal consultant for Karen Martin & Associates, LLC, instructor for the University of California, San Diego's Lean Enterprise program, and industry advisor to the University of San Diego's Industrial and Systems Engineering program. Mike Osterling provides support and leadership to manufacturing and non-manufacturing organizations on their Lean Transformation Journey. In a continuous improvement leadership role for six years, Mike played a key role in Square D Company's lean transformation in the 1990s.

    To grow professionally, you also need soft skills and effective learning techniques. Honing those skills is what this book is all about. Authors Dave Hoover and Adewale Oshineye have cataloged dozens of behavior patterns to help you perfect essential aspects of your craft. Compiled from years of research, many interviews, and feedback from O'Reilly's online forum, these patterns address difficult situations that programmers, administrators, and DBAs face every day. And it's not just about financial success. Apprenticeship Patterns also approaches software development as a means to personal fulfillment. Discover how this book can help you make the best of both your life and your career. Solutions to some common obstacles that this book explores in-depth include:Burned out at work? "Nurture Your Passion" by finding a pet project to rediscover the joy of problem solving.Feeling overwhelmed by new information? Re-explore familiar territory by building something you've built before, then use "Retreat into Competence" to move forward again.Stuck in your learning? Seek a team of experienced and talented developers with whom you can "Be the Worst" for a while. "Brilliant stuff! Reading this book was like being in a time machine that pulled me back to those key learning moments in my career as a professional software developer and, instead of having to learn best practices the hard way, I had a guru sitting on my shoulder guiding me every step towards master craftsmanship. I'll certainly be recommending this book to clients. I wish I had this book 14 years ago!" -Russ Miles, CEO, OpenCredo

    This one's a keeper." --Robert C. Martin "If you want to be an expert in the state of the art in TDD, you need to understand the ideas in this book."--Michael Feathers Test-Driven Development (TDD) is now an established technique for delivering better software faster. TDD is based on a simple idea: Write tests for your code before you write the code itself. However, this simple idea takes skill and judgment to do well. Now there's a practical guide to TDD that takes you beyond the basic concepts. Drawing on a decade of experience building real-world systems, two TDD pioneers show how to let tests guide your development and "grow" software that is coherent, reliable, and maintainable. Steve Freeman and Nat Pryce describe the processes they use, the design principles they strive to achieve, and some of the tools that help them get the job done. Through an extended worked example, you'll learn how TDD works at multiple levels, using tests to drive the features and the object-oriented structure of the code, and using Mock Objects to discover and then describe relationships between objects. Along the way, the book systematically addresses challenges that development teams encounter with TDD--from integrating TDD into your processes to testing your most difficult features. Coverage includes - Implementing TDD effectively: getting started, and maintaining your momentum throughout the project - Creating cleaner, more expressive, more sustainable code - Using tests to stay relentlessly focused on sustaining quality - Understanding how TDD, Mock Objects, and Object-Oriented Design come together in the context of a real software development project - Using Mock Objects to guide object-oriented designs - Succeeding where TDD is difficult: managing complex test data, and testing persistence and concurrency

    Some books try to give you copy-and-paste instructions for how to deal with every single system issue that may arise, but How Linux Works actually shows you how the Linux system functions so that you can come up with your own solutions. After a guided tour of filesystems, the boot sequence, system management basics, and networking, author Brian Ward delves into open-ended topics such as development tools, custom kernels, and buying hardware, all from an administrator's point of view. With a mixture of background theory and real-world examples, this book shows both "how" to administer Linux, and "why" each particular technique works, so that you will know how to make Linux work for you.

    But being a great ScrumMaster, one who truly embodies the principles of servant-leadership and helps move a team to the high performance levels possible with Scrum, is much harder and much more elusive. In his over ten years of coaching numerous Scrum teams, the highly-respected and experienced Scrum coach Geoff Watts has identified patterns that separate a good ScrumMaster from a great one. In this book, he not only illustrates these patterns through stories of his own experiences and those of the many Scrum teams he has encountered but offers practical guidance for you on your own path to greatness.In this book you will learn:The skills and characteristics of great ScrumMastersHow to generate, maintain and increase engagement from the teamHow to increase the effectiveness of the Scrum meetings, such as retrospectives and daily scrums.How to foster a more creative and collaborative teamHow to increase the performance of the teamHow to know when you are a successful ScrumMaster\Scrum Mastery is for practicing ScrumMasters who want to develop themselves into a great servant-leader capable of taking their teams beyond simple process compliance.Comments on the bookMike Cohn, in his foreword for the book, said:"Most books rehash well-trod territory and I don’t finish them any wiser. I am positive I will be referring back to this book for many years" Roman Pichler, author of Agile Product Management with Scrum: Creating Products That Customers Love said:"I am thoroughly impressed with how comprehensive and well-written the book is. It will be indispensable for many people"Jean Tabaka, Agile Fellow, Rally Software:"Geoff brings us a personal and inspired peak into what truly moves us from good to great: great in how we serve; great in how we lead; great in how we create mastery in our teams and organizations; and, great in how we recognize the impediments to our own growth to greatness. Scrum mastery is a skill that can be honed and Geoff gives us rich tools to sharpen our craft."

    Perfect for small teams producing software with fast-changing requirements, XP can save time and money while dramatically improving quality. In XP Installed, three participants in DaimlerChrysler's breakthrough XP project cover every key practice associated with XP implementation. The book consists of a connected collection of essays, presented in the order the practices would actually be implemented during a project. Ideal as both a start-to-finish tutorial and quick reference, the book demonstrates exactly how XP can promote better communication, quality, control, and predictability. An excellent complement to the best selling Extreme Programming Explained, it also works perfectly on a standalone basis, for any developer or team that wants to get rolling with XP fast.

    As an agile coach, I've found the combination of straightforward advice and colorful anecdotes to be invaluable in guiding and focusing interactions with my teams. Jean's wealth of experience is conveyed in a carefully struck balance of reference guides and prose, facilitating just-in-time learning in the agile spirit. All in all, a superb resource for building stronger teams that's fit for agile veterans and neophytes alike." --Arlen Bankston, Lean Agile Practice Manager, CC Pace "If Agile is the new 'what, ' then surely Collaboration is the new 'how.' There are many things I really like about Jean's new book. Right at the top of the list is that I don't have to make lists of ideas for collaboration and facilitation anymore. Jean has it all. Not only does she have those great ideas for meetings, retrospectives, and team decision-making that I need to remember, but the startling new and thought-provoking ideas are there too. And the stories, the stories, the stories! The best way to transfer wisdom. Thanks, Jean!" --Linda Rising, Independent Consultant The Hands-On Guide to Effective Collaboration in Agile Projects To succeed, an agile project demands outstanding collaboration among all its stakeholders. But great collaboration doesn't happen by itself; it must be carefully planned and facilitated throughout the entire project lifecycle. Collaboration Explained is the first book to bring together proven, start-to-finish techniques for ensuring effective collaboration in any agile software project. Since the early days of the agile movement, Jean Tabaka has been studying and promoting collaboration in agile environments. Drawing on her unsurpassed experience, she offers clear guidelines and easy-to-use collaboration templates for every significant project event: from iteration and release planning, through project chartering, all the way through post-project retrospectives. Tabaka's hands-on techniques are applicable to every leading agile methodology, from Extreme Programming and Scrum to Crystal Clear. Above all, they are practical: grounded in a powerful understanding of the technical, business, and human challenges you face as a project manager or development team member. - Build collaborative software development cultures, leaders, and teams - Prepare yourself to collaborate--and prepare your team - Define clear roles for each participant in promoting collaboration - Set your collaborative agenda - Master tools for organizing collaboration more efficiently - Run effective collaborative meetings--including brainstorming sessions - Promote better small-group and pair-programming collaboration - Get better information, and use it to make better decisions - Use non-abusive conflict to drive positive outcomes - Collaborate to estimate projects and schedules more accurately - Strengthen collaboration across distributed, virtual teams - Extend collaboration from individual projects to the entire development organization

    His factory is rapidly heading for disaster. So is his marriage. He has ninety days to save his plant—or it will be closed by corporate HQ, with hundreds of job losses. It takes a chance meeting with a colleague from student days—Jonah—to help him break out of conventional ways of thinking to see what needs to be done.The story of Alex's fight to save his plant is more than compulsive reading. It contains a serious message for all managers in industry and explains the ideas which underline the Theory of Constraints (TOC) developed by Eli Goldratt.

    Whether you agree or disagree with him, and you're likely to do both, the essays in this book will always give you something worth thinking about.Mike Cohn, author of Succeeding with Agile: Software Development using ScrumTobias Mayer’s signature move is to pick up a stone and throw it through our glass house, smashing our old paradigms and causing us, after some pain and turmoil, to say, “OK, my comfortable way doesn’t work anymore. Now what?”Lyssa Adkins, author of Coaching Agile TeamsTobias Mayer has a really interesting mind: wide, deep, imaginative, and quirky. I value the quirky most because it's unpredictable. But in hindsight his jumps reveal themselves as the result of intelligence and rigor. What's more, he gets those jumps gracefully down on paper so that we can all participate.Lee Devin, author of Artrful Making and The Soul of DesignTobias Mayer is known in the agile community as a brilliant and evangelical orator, an innovative trainer and an extraordinary trouble maker. You could call him the Hunter S. Thompson of the software arena, and no one who knows him would laugh. This book is a collection of essays drawn from his writing over the past seven years on the blogs Agile Thinking and Agile Anarchy, missives from the front lines of agile practice that represent the next generation of thinking on conventional agile topics like self-organization, technical debt and estimation–and utterly original writing on new topics like organizational anarchy, corporate oppression, the effect of testosterone on business practices, and artisanal product development.Moving beyond the mere how-to, this is a book to excite the emotions and the intellect in those of us who have chosen the path of scrum to guide us in our work lives. Not since Paul Graham’s Hackers and Painters has the discussion of software development been elevated to this level of world-view-changing discourse. In Tobias Mayer, technology has an exciting new voice to lead us into the brave new world of agile practice.

    The modern economy—the world itself—relies on technology. Demand for the people who can produce it far outweighs the supply. So why do developers occupy largely subordinate roles in the corporate structure? Developer Hegemony explores the past, present, and future of the corporation and what it means for developers. While it outlines problems with the modern corporate structure, it’s ultimately a play-by-play of how to leave the corporate carnival and control your own destiny. And it’s an emboldening, specific vision of what software development looks like in the world of developer hegemony—one where developers band together into partner firms of “efficiencers,” finally able to command the pay, respect, and freedom that’s earned by solving problems no one else can. Developers, if you grow tired of being treated like geeks who can only be trusted to take orders and churn out code, consider this your call to arms. Bring about the autonomous future that’s rightfully yours. It’s time for developer hegemony.

    Getting actions out of a retrospective that are doable, and getting them done helps teams to learn and improve. We hope that this book helps you and your teams to do retrospectives effectively and efficiently to reflect upon your ways of working, and continuously improve them!

    Who are these people, what motivates them, and why should you care?Consider these facts: Everything around us is turning into computers. Your typewriter is gone, replaced by a computer. Your phone has turned into a computer. So has your camera. Soon your TV will. Your car was not only designed on computers, but has more processing power in it than a room-sized mainframe did in 1970. Letters, encyclopedias, newspapers, and even your local store are being replaced by the Internet.Hackers & Painters: Big Ideas from the Computer Age, by Paul Graham, explains this world and the motivations of the people who occupy it. In clear, thoughtful prose that draws on illuminating historical examples, Graham takes readers on an unflinching exploration into what he calls “an intellectual Wild West.”The ideas discussed in this book will have a powerful and lasting impact on how we think, how we work, how we develop technology, and how we live. Topics include the importance of beauty in software design, how to make wealth, heresy and free speech, the programming language renaissance, the open-source movement, digital design, internet startups, and more.

    This book surveys the most important computer algorithms currently in use and provides a full treatment of data structures and algorithms for sorting, searching, graph processing, and string processing -- including fifty algorithms every programmer should know. In this edition, new Java implementations are written in an accessible modular programming style, where all of the code is exposed to the reader and ready to use.The algorithms in this book represent a body of knowledge developed over the last 50 years that has become indispensable, not just for professional programmers and computer science students but for any student with interests in science, mathematics, and engineering, not to mention students who use computation in the liberal arts.The companion web site, algs4.cs.princeton.edu contains An online synopsis Full Java implementations Test data Exercises and answers Dynamic visualizations Lecture slides Programming assignments with checklists Links to related material The MOOC related to this book is accessible via the "Online Course" link at algs4.cs.princeton.edu. The course offers more than 100 video lecture segments that are integrated with the text, extensive online assessments, and the large-scale discussion forums that have proven so valuable. Offered each fall and spring, this course regularly attracts tens of thousands of registrants.Robert Sedgewick and Kevin Wayne are developing a modern approach to disseminating knowledge that fully embraces technology, enabling people all around the world to discover new ways of learning and teaching. By integrating their textbook, online content, and MOOC, all at the state of the art, they have built a unique resource that greatly expands the breadth and depth of the educational experience.

    In this book, you'll learn how to become an entrepreneur, driving your career in the direction of your choosing. You'll learn how to build your software development career step by step, following the same path that you would follow if you were building, marketing, and selling a product. After all, your skills themselves are a product. The choices you make about which technologies to focus on and which business domains to master have at least as much impact on your success as your technical knowledge itself--don't let those choices be accidental. We'll walk through all aspects of the decision-making process, so you can ensure that you're investing your time and energy in the right areas. You'll develop a structured plan for keeping your mind engaged and your skills fresh. You'll learn how to assess your skills in terms of where they fit on the value chain, driving you away from commodity skills and toward those that are in high demand. Through a mix of high-level, thought-provoking essays and tactical "Act on It" sections, you will come away with concrete plans you can put into action immediately. You'll also get a chance to read the perspectives of several highly successful members of our industry from a variety of career paths. As with any product or service, if nobody knows what you're selling, nobody will buy. We'll walk through the often-neglected world of marketing, and you'll create a plan to market yourself both inside your company and to the industry in general. Above all, you'll see how you can set the direction of your career, leading to a more fulfilling and remarkable professional life.

    Cooper details many of these meta functions to explain his central thesis: programmers need to seriously re-evaluate the many user-hostile concepts deeply embedded within the software development process. Rather than provide users with a straightforward set of options, programmers often pile on the bells and whistles and ignore or de-prioritise lingering bugs. For the average user, increased functionality is a great burden, adding to the recurrent chorus that plays: "computers are hard, mysterious, unwieldy things." (An average user, Cooper asserts, who doesn't think that way or who has memorised all the esoteric commands and now lords it over others, has simply been desensitised by too many years of badly designed software.) Cooper's writing style is often overblown, with a pantheon of cutesy terminology (i.e. "dancing bearware") and insider back-patting. (When presenting software to Bill Gates, he reports that Gates replied: "How did you do that?" to which he writes: "I love stumping Bill!") More seriously, he is also unable to see beyond software development's importance--a sin he accuses programmers of throughout the book. Even with that in mind, the central questions Cooper asks are too important to ignore: Are we making users happier? Are we improving the process by which they get work done? Are we making their work hours more effective? Cooper looks to programmers, business managers and what he calls "interaction designers" to question current assumptions and mindsets. Plainly, he asserts that the goal of computer usage should be "not to make anyone feel stupid." Our distance from that goal reinforces the need to rethink entrenched priorities in software planning. -- Jennifer Buckendorff, Amazon.com