In the decade since it was published, the international audience of watch lovers and watch collectors has grown exponentially. It’s time for The Watch, Thoroughly Revised. For this new edition, the original author, Gene Stone, is joined by Stephen Pulvirent of Hodinkee.com. Together, they have thoroughly revamped the book to reflect the current state of the watch world, with the addition of new brands, new models, and more focused and nuanced coverage of the traditional brand leaders, including Rolex, Patek Philippe, Omega, and TAG Heuer.

    You'll learn several tried and tested patterns and techniques that you can use as you migrate your existing architecture.*Ideal for organizations looking to transition to microservices, rather than rebuild*Helps companies determine whether to migrate, when to migrate, and where to begin*Addresses communication, integration, and the migration of legacy systems*Discusses multiple migration patterns and where they apply*Provides database migration examples, along with synchronization strategies*Explores application decomposition, including several architectural refactoring patterns*Delves into details of database decomposition, including the impact of breaking referential and transactional integrity, new failure modes, and more

    

    The reason? An inability to adapt quickly to new business realities. Established companies are at risk, but it’s no easier being an agile startup, because most of those fail due to their inability to scale. Tomorrow’s business winners—regardless of size or industry—will be the ones that know how to combine scale with agility. In Design to Grow, a Coca-Cola senior executive shares both the successes and failures of one of the world’s largest companies as it learns to use design to be both agile and big. In this rare and unprecedented behind-the-scenes look, David Butler and senior Fast Company editor, Linda Tischler, use plain language and easy-to-understand case studies to show how this works at Coca-Cola—and how other companies can use the same approach to grow their business. This book is a must-read for managers inside large corporations as well as entrepreneurs just getting started.

    As the first act of flight, a rocket launch requires an entire set of systems to lift the vehicle into orbit-not just the vehicle itself, but all the systems needed for smoothly moving off the ground into space. Likewise, your project needs its entire set of supporting systems in place to begin a successful journey to delivery. Whatever you call it (project kickoff, bootcamp, inception, or jump start), liftoff gives your team its trajectory, and launches your project. This critical practice informs, inspires, and aligns everyone to a singular purpose: the successful delivery of software. This success is in your hands! Agile veterans Diana Larsen and Ainsley Nies teach you how to organize and conduct liftoffs, hold team activities to discover what's most important, and offer a working framework for effective and lightweight agile chartering.

    Illustrates how programmer's, developer's, and software engineers can make their work a profession; not just a job!

    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

    Weinberg -- author of more than forty books and more than 400 articles over a forty-year career -- reveals his secrets for gathering, organizing, and discarding writing ideas. Drawing an analogy to the stone-by-stone method of building fieldstone walls, Weinberg shows writers how to construct fiction and nonfiction manuscripts from key insights, stories, and quotes. The elements, or stones, are collected nonsequentially, over time, and eventually find logical places in larger pieces. The method renders writer's block irrelevant and has proved effective for scores of Weinberg's writing class students, who have collectively published more than 100 books. If you've ever wanted to write a book or article -- or need a fresh approach to your writing career -- try what works for Weinberg and gather your best ideas into beautiful stone walls. Gerald M. Weinberg is one of the most influential thinkers in computer science. Weinberg on Writing isn't a computer book, though -- Weinberg describes his life and practices as a writer, enriching the text with more than 40 exercises appropriate for individual or group study. Inducted into the Computer Hall of Fame in its inaugural year (in the same class as Bill Gates), Weinberg's career highlights have included computer programming at IBM for Project Mercury (which put the first American in space), serving on the faculty of famed family therapist Virginia Satir, consulting for Fortune 500 companies through his firm, Weinberg & Weinberg, and teaching thousands of technical professionals how to improve their communication skills.

    Now, for the first time, leading agile methodologist Scott Ambler and renowned consultantPramodkumar Sadalage introduce powerful refactoring techniquesspecifically designed for database systems. Ambler and Sadalagedemonstrate how small changes to table structures, data, storedprocedures, and triggers can significantly enhance virtually anydatabase design - without changing semantic

    As a result of their different upbringings, they spend their lives chasing three very different things: Money, power and love.This is a human story: A tale about people like ourselves, cajoled by the whimsy of circumstance, who find themselves performing the most beautiful acts as well as the most vulgar.This is a historical story: A tale set in the early 1800s, which shines a light on how bankers, with the power to create money out of nothing, were able to shape the world we live in today.And this is a love story: A tale about three men, who fall in love with the same woman, at the very same time…

    For all but the most trivial software systems, you must pay close attention to its architecture, the conceptual glue that holds every phase of a project together.

    Through four years of groundbreaking research, Dr. Nicole Forsgren, Jez Humble, and Gene Kim set out to find a way to measure software delivery performance—and what drives it—using rigorous statistical methods. This book presents both the findings and the science behind that research. Readers will discover how to measure the performance of their teams, and what capabilities they should invest in to drive higher performance.

    In 1999, Tony introduced Clayton Christensen to the idea that “people have underlying needs or processes in their lives, that they are addressing in some way right now”—an insight that was to become Jobs-to-be-Done Theory. For 25 years, Ulwick and his company, Strategyn, have helped over 400 companies, applying Jobs-to-be-Done Theory in practice with a success rate of 86%—a 5-fold improvement. “Ulwick has taken the guesswork out of innovation,” says the ‘father of modern marketing,’ Philip Kotler, S. C. Johnson Distinguished Professor of International Marketing at the Kellogg School of Management, Northwestern University. “He has done this by introducing us to Jobs-to-be-Done theory, and converting it to practice using his rigorous innovation process known as Outcome-Driven Innovation. I call him the Deming of Innovation because, more than anyone else, Tony has turned innovation into a science,” adds Kotler. LEARN - Why companies fail at innovation and how to avoid critical mistakes. - How to employ the Jobs-to-be-Done Theory Needs Framework to categorize, define, capture, and prioritize customer needs. - A Jobs-to-be-Done Growth Strategy Matrix to categorize, understand, and employ the 5 strategies that drive growth. - Outcome-Based Segmentation: how does it create new opportunities? - The details of the innovation process known as Outcome-Driven Innovation. It ties customer-defined metrics to the customer’s Job-to-be-Done, transforming every aspect of opportunity discovery, marketing and innovation. - The Language of Job-to-be-Done – the syntax and lexicon of innovation.

    It describes the roles, teams, values, intentions, habits, activities, policies and work products of a small software development team forwhom time-to-market and development costs are critical considerations.Alistair Cockburn is one of the founders of the Agile software developmentmovement. He spells out proven best practices based on his extensiveexperience helping organizations build software quickly and with less cost. Theauthor understands that small teams cannot be burdened by process-heavysoftware methodologies. By advocating that developers stay close together andremain in steady, good-will communication with customers and users, thisbook teaches the reader how to develop software that not only does what it issupposed to do, but also gets completed on time and within budget.

    You’ll learn to spot which tests are performing, which need refactoring, and which need to be deleted entirely! Upgrade your testing suite with new testing styles, good patterns, and reliable automated testing.