As teams become more and more global and distributed, visualization provides an important channel of communication--one that opens up the group's mind to improving work systems and processes by understanding relationships, interconnections, and big picture contexts.Visual Teams shares best practices and uses visualization as a power tool for process improvement by providing teams with a common language for high performance. The book:Explores how any kind of team can draw on the principles and practices of creative design teams in the software, architectural, engineering, and information design professions Introduces the Drexler/Sibbet Team Performance(TM) Model and related tools--a system used throughout companies such as Nike, Genentech, Becton Dickinson, Chevron, and others Visual Teams presents a comprehensive framework, best practices, and unique visual tools for becoming an innovative, high-performance team.

    He needed a way to keep track of software development over time – whatever he was thinking about or working on. He researched subjects he found interesting, then documented his research with a public blog post, which he could easily find and refer to later. Over time, increasing numbers of blog visitors found the posts helpful, relevant and interesting. Now, approximately 100,000 readers visit the blog per day and nearly as many comment and interact on the site.In “How to Stop Sucking and Be Awesome Instead” you’ll find a thought-provoking and entertaining collection of Jeff’s writings on several programming-related topics.

    Every leader knows this to be true, yet few have systematic methods for converting organizational knowledge into economic value. This book argues that communities of practice--groups of individuals formed around common interests and expertise--provide the ideal vehicle for driving knowledge-management strategies and building lasting competitive advantage. Written by leading experts in the field, Cultivating Communities of Practice is the first book to outline models and methods for systematically developing these essential groups. Through compelling research and company examples, including DaimlerChrysler, McKinsey & Company, Shell, and the World Bank, authors Etienne Wenger, Richard McDermott, and William M. Snyder show how world-class organizations have leveraged communities of practice to drive strategy, generate new business opportunities, solve problems, transfer best practices, develop employees' professional skills, and recruit and retain top talent. Underscoring the new central role communities of practice are playing in today's knowledge economy, Cultivating Communities of Practice is the definitive guide to fostering, designing, and developing these powerful groups within and across organizations.

    Visible Ops is comprised of four prescriptive and self-fueling steps that take an organization from any starting point to a continually improving process. MAKING ITIL ACTIONABLE Although the Information Technology Infrastructure Library (ITIL) provides a wealth of best practices, it lacks prescriptive guidance: What do you implement first, and how do you do it? Moreover, the ITIL books remain relatively expensive to distribute. Other information, publicly available from a variety of sources, is too general and vague to effectively aid organizations that need to start or enhance process improvement efforts. The Visible Ops booklet provides a prescriptive roadmap for organizations beginning or continuing their IT process improvement journey. WHY DO WE NEED VISIBLE OPS? The Visible Ops methodology was developed because there was not a satisfactory answer to the question: "I believe in the need for IT process improvement, but where do I start?" Since 2000, Gene Kim and Kevin Behr have met with hundreds of IT organizations and identified eight high-performing IT organizations with the highest service levels, best security, and best efficiencies. For years, they studied these high-performing organizations to figure out the secrets to their success. Visible Ops codifies how these organizations achieved their transformation from good to great, showing how interested organizations can replicate the key processes of these high-performing organizations in just four steps: 1. Stabilize Patient, Modify First Response - Almost 80% of outages are self-inflicted. The first step is to control risky changes and reduce MTTR by addressing how changes are managed and how problems are resolved. 2. Catch and Release, Find Fragile Artifacts - Often, infrastructure exists that cannot be repeatedly replicated. In this step, we inventory assets, configurations and services, to identify those with the lowest change success rates, highest MTTR and highest business downtime costs. 3. Establish Repeatable Build Library - The highest return on investment is implementing effective release management processes. This step creates repeatable builds for the most critical assets and services, to make it "cheaper to rebuild than to repair." 4. Enable Continuous Improvement - The previous steps have progressively built a closed-loop between the Release, Control and Resolution processes. This step implements metrics to allow continuous improvement of all of these process areas, to best ensure that business objectives are met.

    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.

    I would love to write that book, but at this time I have no indication that such a book would be worth writing. Most books fail in the market, and most of them fail not because they are poorly written or edited, but because there aren’t enough people interested in them. They are not the right it.What you are reading now is a pretotype edition of the book. I wrote and “edited” it in days instead of months, just to test the level of interest in such a book. I had a few friends and colleagues review it, but don’t be surprised if you find typos, misspellings, bad grammar, awkward formatting and all sorts of misteaks.Releasing it in its present state is not easy for me.The toughest thing about pretotyping is not developing pretotypes, that’s the fun part. The tough part is getting over our compulsion for prema- ture perfectionism and our desire to add more features, or content, before releasing the first version. The tough part is getting our pretotypes in front of people, where they will be judged, criticized and – possibly – rejected.Reid Hoffman, founder of LinkedIn once said: “If you are not embarrassed by the first version of your product, you’ve launched too late.”I am plenty embarrassed. I must be on the right track.http://www.pretotyping.org/pretotype-...

    Establishing and maintaining processes that greatly reduce the chances of project failure is paramount to achieving the competitive edge your company seeks."The Handbook of Program Management" gives program managers at all levels the techniques to put such processes in place as well as consistently integrate new technology and new people into these processes, thus producing superior products and services. Dr. James Brown, an internationally recognized authority in program and project management, explains how to strike a crucial balance between operations and project implementations-the precise point where you must nurture repeatable success.Outlining the differences between the roles of program and project managers, Dr. Brown provides proven principles for establishing a successful program management culture that is supported by enthusiastic personnel and stakeholders. He shows you how to develop the attributes of an effective program manager, from having a vision and strategy for long-term improvement to assessing people and building relationships to analyzing a myriad of means for accomplishing program objectives. You'll see how to Readily adapt to changing business conditions and turn chaos into clarity Mentor and coach project managers in terms of stakeholder management Make strategic program process decisions that positively impact your culture Build strong teams on multiple levels Plan an effective program execution Manage risk in an environment of uncertaintyYou'll also learn the keys to proper portfolio management and how to capitalize on positive program outcomes. Nowhere else will you find such comprehensive, authoritative information on meeting the new standards of program management--Dr. Brown's "The Handbook of Project Management" is the definitive resource.

    Ben Horowitz has long been fascinated by history, and particularly by how people behave differently than you’d expect. The time and circumstances in which they were raised often shapes them—yet a few leaders have managed to shape their times. In What You Do Is Who You Are, he turns his attention to a question crucial to every organization: how do you create and sustain the culture you want?To Horowitz, culture is how a company makes decisions. It is the set of assumptions employees use to resolve everyday problems: should I stay at the Red Roof Inn, or the Four Seasons? Should we discuss the color of this product for five minutes or thirty hours? If culture is not purposeful, it will be an accident or a mistake.What You Do Is Who You Are explains how to make your culture purposeful by spotlighting four models of leadership and culture-building—the leader of the only successful slave revolt, Haiti’s Toussaint Louverture; the Samurai, who ruled Japan for seven hundred years and shaped modern Japanese culture; Genghis Khan, who built the world’s largest empire; and Shaka Senghor, a man convicted of murder who ran the most formidable prison gang in the yard and ultimately transformed prison culture.Horowitz connects these leadership examples to modern case-studies, including how Louverture’s cultural techniques were applied (or should have been) by Reed Hastings at Netflix, Travis Kalanick at Uber, and Hillary Clinton, and how Genghis Khan’s vision of cultural inclusiveness has parallels in the work of Don Thompson, the first African-American CEO of McDonalds, and of Maggie Wilderotter, the CEO who led Frontier Communications. Horowitz then offers guidance to help any company understand its own strategy and build a successful culture.What You Do Is Who You Are is a journey through culture, from ancient to modern. Along the way, it answers a question fundamental to any organization: who are we? How do people talk about us when we’re not around? How do we treat our customers? Are we there for people in a pinch? Can we be trusted?Who you are is not the values you list on the wall. It’s not what you say in company-wide meeting. It’s not your marketing campaign. It’s not even what you believe. Who you are is what you do. This book aims to help you do the things you need to become the kind of leader you want to be—and others want to follow.

    And this may sound weirdly obvious, but every single one of those pieces of software was written by a programmer. Programmers are thus among the most quietly influential people on the planet. As we live in a world made of software, they're the architects. The decisions they make guide our behavior. When they make something newly easy to do, we do a lot more of it. If they make it hard or impossible to do something, we do less of it.If we want to understand how today's world works, we ought to understand something about coders. Who exactly are the people that are building today's world? What makes them tick? What type of personality is drawn to writing software? And perhaps most interestingly -- what does it do to them?One of the first pieces of coding a newbie learns is the program to make the computer say "Hello, world!" Like that piece of code, Clive Thompson's book is a delightful place to begin to understand this vocation, which is both a profession and a way of life, and which essentially didn't exist little more than a generation ago, but now is considered just about the only safe bet we can make about what the future holds. Thompson takes us close to some of the great coders of our time, and unpacks the surprising history of the field, beginning with the first great coders, who were women. Ironically, if we're going to traffic in stereotypes, women are arguably "naturally" better at coding than men, but they were written out of the history, and shoved out of the seats, for reasons that are illuminating. Now programming is indeed, if not a pure brotopia, at least an awfully homogenous community, which attracts people from a very narrow band of backgrounds and personality types. As Thompson learns, the consequences of that are significant - not least being a fetish for disruption at scale that doesn't leave much time for pondering larger moral issues of collateral damage. At the same time, coding is a marvelous new art form that has improved the world in innumerable ways, and Thompson reckons deeply, as no one before him has, with what great coding in fact looks like, who creates it, and where they come from. To get as close to his subject has he can, he picks up the thread of his own long-abandoned coding practice, and tries his mightiest to up his game, with some surprising results.More and more, any serious engagement with the world demands an engagement with code and its consequences, and to understand code, we must understand coders. In that regard, Clive Thompson's Hello, World! is a marvelous and delightful master class.

    Vaughn Vernon couples guided approaches to implementation with modern architectures, highlighting the importance and value of focusing on the business domain while balancing technical considerations.Building on Eric Evans’ seminal book, Domain-Driven Design, the author presents practical DDD techniques through examples from familiar domains. Each principle is backed up by realistic Java examples–all applicable to C# developers–and all content is tied together by a single case study: the delivery of a large-scale Scrum-based SaaS system for a multitenant environment.The author takes you far beyond “DDD-lite” approaches that embrace DDD solely as a technical toolset, and shows you how to fully leverage DDD’s “strategic design patterns” using Bounded Context, Context Maps, and the Ubiquitous Language. Using these techniques and examples, you can reduce time to market and improve quality, as you build software that is more flexible, more scalable, and more tightly aligned to business goals.

    The Wall Street Journal says the method can “help anyone to focus.”The new version of the Pomodoro Technique includes a chapter on how to make the Technique work for you. Readers will also learn how to predict the time it takes to complete a task, monitor their productivity and set personal goals.Having fun with time management might seem like an oxymoron to some but it’s actually possible with the Pomodoro Technique!

    Abbott and Michael T. Fisher cover everything IT and business leaders must know to build technology infrastructures that can scale smoothly to meet any business requirement. Drawing on their unparalleled experience managing some of the world s highest-transaction-volume Web sites, the authors provide detailed models and best-practice approaches available in no other book. Unlike previous books on scalability, "The Art of Scalability" doesn t limit its coverage to technology. Writing for both technical and nontechnical decision-makers, this book covers everything that impacts scalability, including architecture, processes, people, and organizations. Throughout, the authors address a broad spectrum of real-world challenges, from performance testing to IT governance. Using their tools and guidance, organizations can systematically overcome obstacles to scalability and achieve unprecedented levels of technical and business performance. Coverage includes Staffing the scalable organization: essential organizational, management, and leadership skills for technical leaders Building processes for scale: process lessons from hyper-growth companies, from technical issue resolution to crisis management Making better build versus buy decisions Architecting scalable solutions: powerful proprietary models for identifying scalability needs and choosing the best approaches to meet them Optimizing performance through caching, application and database splitting, and asynchronous design Scalability techniques for emerging technologies, including clouds and grids Planning for rapid data growth and new data centers Evolving monitoring strategies to tightly align with customer requirements "

    This is the missing book about agile that shows how designers, product managers, and development teams can integrate experience design into lean and agile product development. It equips you with tools, techniques and a framework for designing great experiences using agile methods so you can deliver timely products that are technically feasible, profitable for the business, and desirable from an end-customer perspective. This book will help you successfully integrate your design process on an agile project and feel like part of the agile team. do good design faster by doing just enough, just in time. use design methods from disciplines such as design thinking, customer-centered design, product design, and service design. create successful digital products by considering the needs of the end-customer, the business, and technology. understand the next wave of thinking about continuous design and continuous delivery.

    Learn the principles and guiding philosophies of Bill Gates, Jeff Bezos, Ruth Bader Ginsburg, Warren Buffett, Oprah Winfrey, and many others through illuminating conversations about their remarkable lives and careers. For the past five years, David M. Rubenstein—author of The American Story, visionary cofounder of The Carlyle Group, and host of The David Rubenstein Show—has spoken with the world’s highest performing leaders about who they are and how they became successful. How to Lead distills these revealing conversations into an indispensable leadership guidebook. Gain advice and wisdom from CEOs, presidents, founders, and master performers from the worlds of finance (Warren Buffett, Jamie Dimon, Christine Lagarde, Ken Griffin), tech (Jeff Bezos, Bill Gates, Eric Schmidt, Tim Cook), entertainment (Oprah Winfrey, Lorne Michaels, Renee Fleming, Yo-Yo Ma), sports (Jack Nicklaus, Adam Silver, Coach K, Phil Knight), government (President Bill Clinton, President George W. Bush, Ruth Bader Ginsburg, Nancy Pelosi), and many others. -Jeff Bezos harnesses the power of wandering, discovering that his best decisions have been made with heart and intuition, rather than analysis. -Richard Branson never goes into a venture looking to make a profit. He aims to make the best in field. -Phil Knight views Nike as a marketing company whose product is its most important marketing tool. -Marillyn Hewson, who grew up in a fatherless home with four siblings in Kansas, quickly learned the importance of self-reliance and the value of a dollar. How to Lead shares the extraordinary stories of these pioneering agents of change. Discover how each luminary got started and how they handle decision making, failure, innovation, change, and crisis. Learn from their decades of experience as pioneers in their field. No two leaders are the same.

    Seddon argues that while many commentators acknowledge command and control is failing us, no one provides an alternative. His contention is the alternative can only be understood when you see the failings of command and control by taking the better - systems - view. There is little in the book that you would find in a normal management curriculum. Seddon is scathing and controversial about leadership theorists, maintaining that leadership is being able to talk about how the work works with the people who do it. The book provides practical advice and examples of how to put this into place. Packed with illustrations of the unintended consequences of command and control thinking, you will be amazed that management of our organizations should be so appalling. You will see how customer service is poor and carries high costs and that changing the way the work is designed and managed will result in lower costs and better service. But, as Seddon points out, these are things managers cannot "see" from their current position. Managers don't know what they don't know. Seddon's case is that taking this view teaches managers to change their thinking, and he shows how the very observations they make when understanding what he calls "the what and why of current performance as a system" become the building blocks of the systems solution. And also illustrates the solutions for the cases he uses.