By presenting actual experiences and analyzing them as they are described, the author conveys the developmental thought processes employed and shows a style of thinking that leads to successful results is something that can be learned. Along with spectacular successes, the author also conveys how failures contributed to shaping the thought processes. Provides the reader with a style of thinking that will enhance a person's ability to function as a problem-solver of complex technical issues. Consists of a collection of stories about the author's participation in significant discoveries, relating how those discoveries came about and, most importantly, provides analysis about the thought processes and reasoning that took place as the author and his associates progressed through engineering problems.

    Significant numbers of poorly designed programs have been created by less-experienced developers, resulting in applications that are inefficient and hard to maintain and extend. Increasingly, software system professionals are discovering just how difficult it is to work with these inherited, non-optimal applications. For several years, expert-level object programmers have employed a growing collection of techniques to improve the structural integrity and performance of such existing software programs. Referred to as refactoring, these practices have remained in the domain of experts because no attempt has been made to transcribe the lore into a form that all developers could use... until now. In Refactoring: Improving the Design of Existing Software, renowned object technology mentor Martin Fowler breaks new ground, demystifying these master practices and demonstrating how software practitioners can realize the significant benefits of this new process.

    With a vivid, humorous, and too familiar scenario they show a manager loaded down by all the monkeys that have jumped from their rightful owners onto his back. Then step by step they show how managers can free themselves from doing everyone else's job and ensure that every problem is handled by the proper staff person. By using Oncken's Four Rules of Monkey Management managers will learn to become effective supervisors of time, energy, and talent -- especially their own.If you have ever wondered why you are in the office on the weekends and your staff is on the golf course, The One Minute Manager Meets the Monkey is for you. It's priceless!

    But, as Mandi Walls explains in this Velocity report, DevOps is really about changing company culture—replacing traditional development and operations silos with collaborative teams of people from both camps. The DevOps movement has produced some efficient teams turning out better products faster. The tough part is initiating the change. This report outlines strategies for managers looking to go beyond tools to build a DevOps culture among their technical staff. Topics include: Documenting reasons for changing to DevOps before you commit Defining meaningful and achievable goals Finding a technical leader to be an evangelist, tools and process expert, and shepherd Starting with a non-critical but substantial pilot project Facilitating open communication among developers, QA engineers, marketers, and other professionals Realigning your team’s responsibilities and incentives Learning when to mediate disagreements and conflicts Download this free report and learn how to the DevOps approach can help you create a supportive team environment built on communication, respect, and trust. Mandi Walls is a Senior Consultant with Opscode.

    Clear, powerful and urgent, it's a must read for anyone who cares about where they work and how they work."--Seth Godin, author of This is Marketing "This book is a breath of fresh air. Read it now, and make sure your boss does too."--Adam Grant, New York Times bestselling author of Give and Take, Originals, and Option B with Sheryl Sandberg When fast-scaling startups and global organizations get stuck, they call Aaron Dignan. In this book, he reveals his proven approach for eliminating red tape, dissolving bureaucracy, and doing the best work of your life.He's found that nearly everyone, from Wall Street to Silicon Valley, points to the same frustrations: lack of trust, bottlenecks in decision making, siloed functions and teams, meeting and email overload, tiresome budgeting, short-term thinking, and more.Is there any hope for a solution? Haven't countless business gurus promised the answer, yet changed almost nothing about the way we work?That's because we fail to recognize that organizations aren't machines to be predicted and controlled. They're complex human systems full of potential waiting to be released.Dignan says you can't fix a team, department, or organization by tinkering around the edges. Over the years, he has helped his clients completely reinvent their operating systems--the fundamental principles and practices that shape their culture--with extraordinary success.Imagine a bank that abandoned traditional budgeting, only to outperform its competition for decades. An appliance manufacturer that divided itself into 2,000 autonomous teams, resulting not in chaos but rapid growth. A healthcare provider with an HQ of just 50 people supporting over 14,000 people in the field--that is named the "best place to work" year after year. And even a team that saved $3 million per year by cancelling one monthly meeting.Their stories may sound improbable, but in Brave New Work you'll learn exactly how they and other organizations are inventing a smarter, healthier, and more effective way to work. Not through top down mandates, but through a groundswell of autonomy, trust, and transparency.Whether you lead a team of ten or ten thousand, improving your operating system is the single most powerful thing you can do. The only question is, are you ready?

    Without it, we forget what's important to us and lose sight of the steps we might take to reach those goals. Conscious business, explains Fred Kofman, means shining this awareness on every area of your work: in recognizing the needs of others and expressing your own; in seeing the hidden emotional obstacles that may be holding your team back; in making good decisions under pressure; and even in delving into such spiritual questions as "Who am I?" and "What is my real purpose here?" In Conscious Business, this visionary teacher and consultant to Google, Microsoft, Yahoo! and other leading companies presents the complete training manual in the breakthrough techniques he has shared with over 20,000 executives on four continents.

    Team leads usually have little to no idea how to handle people related issues – issues that affect how the morale, quality of work, and overall performance of the team, and of course impacts how easy or hard it is to implement “the new stuff”.Most team leaders are clueless as to how to handle their manager giving them an impossible due date, a team member reluctant to try anything new, or another team member teaching all the other members practices from 25 years ago that today only hurt the team.Why?No one teaches that to software team leads. Team leads today, in the overwhelming majority of places, are just developers who worked hard and stayed with the company long enough to be promoted. But they have no people or management skills - and those are very painfully needed when you are trying to drive the things you believe in inside an organization that has very little interest in changing.Team leadership is the next big thing that software developers need to conquer, or none of this unit testing, TDD, Agile or Lean thing is going to catch on, except in very small circles, that, by chance, happen to have the right people leading their teams.

    Today, software organizations are transforming the way work gets done through practices like Agile, Lean, and DevOps. But as commonly implemented as these methods are, many transformations still fail, largely because the organization misses a critical step: transforming their culture and the way people communicate. Agile Conversations brings a practical, step-by-step guide to using the human power of conversation to build effective, high-performing teams to achieve truly Agile results. Consultants Douglas Squirrel and Jeffrey Fredrick show readers how to utilize the Five Conversations to help teams build trust, alleviate fear, answer the "whys," define commitments, and hold everyone accountable.These five conversations give teams everything they need to reach peak performance, and they are exactly what's missing from too many teams today. Stop focusing on processes and practices that leave your organization stuck with culture-less rituals. Instead, unleash the unique human power of conversation.

    He draws ideas from three very useful intellectual pools: classical management practices, Agile methods, and lean product development. By combining the strengths of these three approaches, he has produced something that works better than any one in isolation." -From the Foreword by Don Reinertsen, President of Reinertsen & Associates; author of Managing the Design Factory; and leading expert on rapid product development Effective requirements discovery and analysis is a critical best practice for serious application development. Until now, however, requirements and Agile methods have rarely coexisted peacefully. For many enterprises considering Agile approaches, the absence of effective and scalable Agile requirements processes has been a showstopper for Agile adoption. In Agile Software Requirements, Dean Leffingwell shows exactly how to create effective requirements in Agile environments. Part I presents the "big picture" of Agile requirements in the enterprise, and describes an overall process model for Agile requirements at the project team, program, and portfolio levels Part II describes a simple and lightweight, yet comprehensive model that Agile project teams can use to manage requirements Part III shows how to develop Agile requirements for complex systems that require the cooperation of multiple teams Part IV guides enterprises in developing Agile requirements for ever-larger "systems of systems," application suites, and product portfolios This book will help you leverage the benefits of Agile without sacrificing the value of effective requirements discovery and analysis. You'll find proven solutions you can apply right now-whether you're a software developer or tester, executive, project/program manager, architect, or team leader.

     The master teacher of positive change through powerful communication, Susan Scott wants her readers to succeed. To do that, she explains, one must transform everyday conversations employing effective ways to get the message across. In this guide, which includes exercises and tools to take you step by step through the Seven Principles of Fierce Conversations, Scott teaches readers how to: * Overcome barriers to meaningful communication * Expand and enrich conversations with colleagues, friends, and family * Increase clarity and improve understanding * Handle strong emotions-on both sides of the table

    What should we do, or leave undone, in a day or a lifetime? How much messiness should we accept? What balance of new activities and familiar favorites is the most fulfilling? These may seem like uniquely human quandaries, but they are not: computers, too, face the same constraints, so computer scientists have been grappling with their version of such issues for decades. And the solutions they've found have much to teach us.In a dazzlingly interdisciplinary work, acclaimed author Brian Christian and cognitive scientist Tom Griffiths show how the algorithms used by computers can also untangle very human questions. They explain how to have better hunches and when to leave things to chance, how to deal with overwhelming choices and how best to connect with others. From finding a spouse to finding a parking spot, from organizing one's inbox to understanding the workings of memory, Algorithms to Live By transforms the wisdom of computer science into strategies for human living.

    The worst managers undermine inner work life, often unwittingly.As Teresa Amabile and Steven Kramer explain in The Progress Principle, seemingly mundane workday events can make or break employees’ inner work lives. But it’s forward momentum in meaningful work—progress—that creates the best inner work lives. Through rigorous analysis of nearly 12,000 diary entries provided by 238 employees in 7 companies, the authors explain how managers can foster progress and enhance inner work life every day.The book shows how to remove obstacles to progress, including meaningless tasks and toxic relationships. It also explains how to activate two forces that enable progress: (1) catalysts—events that directly facilitate project work, such as clear goals and autonomy—and (2) nourishers—interpersonal events that uplift workers, including encouragement and demonstrations of respect and collegiality.Brimming with honest examples from the companies studied, The Progress Principle equips aspiring and seasoned leaders alike with the insights they need to maximize their people’s performance.

    This book draws on material Michael created for his renowned Object Mentor seminars, techniques Michael has used in mentoring to help hundreds of developers, technical managers, and testers bring their legacy systems under control. The topics covered include: Understanding the mechanics of software change, adding features, fixing bugs, improving design, optimizing performance Getting legacy code into a test harness Writing tests that protect you against introducing new problems Techniques that can be used with any language or platform, with examples in Java, C++, C, and C# Accurately identifying where code changes need to be made Coping with legacy systems that aren't object-oriented Handling applications that don't seem to have any structureThis book also includes a catalog of twenty-four dependency-breaking techniques that help you work with program elements in isolation and make safer changes.

    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.

    Along the way, we encounter black holes, turtles, snakes, dragons, axe-sharpening, and yak-shaving—and take a guided tour through the theories and methods, both brilliant and misguided, that litter the history of software development, from the famous ‘mythical man-month’ to Extreme Programming. Not just for technophiles but for anyone captivated by the drama of invention, Dreaming in Code offers a window into both the information age and the workings of the human mind.