The massive pressure on CIOs continues to increase as the opportunities to use technology in business become more prevalent and more competitive. As CIOs often find themselves at the center of business conflict, they must not only familiarize themselves with Machiavellian tactics as a defensive weapon, but also learn to use them as an offensive weapon in extreme situations so that they can increase IT’s contribution to their enterprises.As Italian political philosopher Niccolo Machiavelli implied, you're either predator or prey, and the animal you most resemble determines your position on the food chain. In The Wolf in CIO's Clothing Gartner analyst and author Tina Nunno expands on Machiavelli's metaphor, examining seven animal types and the leadership attributes of each. Nunno posits the wolf — a social animal with strong predatory instincts — as the ideal example of how a leader can adapt and thrive.Technology may be black and white, but successful leadership demands an ability to exist in the grey. Drawing on her experience with hundreds of CIOs, Nunno charts a viable way to master the Machiavellian principles of power, manipulation, love, and war. Through compelling case studies, her approach demonstrates how CIOs and IT leaders can adjust their leadership styles in extreme situations for their own success and that of their teams.

    Their days are defined by a relentless barrage of incoming messages and back-and-forth digital conversations--a state of constant, anxious chatter in which nobody can disconnect, and so nobody has the cognitive bandwidth to perform substantive work. There was a time when tools like email felt cutting edge, but a thorough review of current evidence reveals that the hyperactive hive mind workflow they helped create has become a productivity disaster, reducing profitability and perhaps even slowing overall economic growth. Equally worrisome, it makes us miserable. Humans are simply not wired for constant digital communication.We have become so used to an inbox-driven workday that it's hard to imagine alternatives. But they do exist. Drawing on years of investigative reporting, author and computer science professor Cal Newport makes the case that our current approach to work is broken, then lays out a series of principles and concrete instructions for fixing it. In A World without Email, he argues for a workplace in which clear processes--not haphazard messaging--define how tasks are identified, assigned and reviewed. Each person works on fewer things (but does them better), and aggressive investment in support reduces the ever-increasing burden of administrative tasks. Above all else, important communication is streamlined, and inboxes and chat channels are no longer central to how work unfolds.The knowledge sector's evolution beyond the hyperactive hive mind is inevitable. The question is not whether a world without email is coming (it is), but whether you'll be ahead of this trend. If you're a CEO seeking a competitive edge, an entrepreneur convinced your productivity could be higher, or an employee exhausted by your inbox, A World Without Email will convince you that the time has come for bold changes, and will walk you through exactly how to make them happen.

    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.

    As technology companies succeed and grow, so do their engineering departments. In your career, you’ll may suddenly get the opportunity to lead teams: to become a manager. But this is often uncharted territory. How can you decide whether this career move is right for you? And if you do, what do you need to learn to succeed? Where do you start? How do you know that you’re doing it right? What does “it” even mean? And isn’t management a dirty word? This book will share the secrets you need to know to manage engineers successfully.

    But they couldn't get investors interested. Today, Android is a large team at Google, shipping an operating system (including camera software) to over three billion devices worldwide.This is the inside story, told by the people who made it happen.“What are the essential ingredients that lead a small team to build software at the sheer scale and impact of Android? We may never fully know, but this first person account is probably the closest set of clues we have.”–Dave Burke, VP of Android Engineering“Androids captures a strong picture of what the early development of Android, as well as the Android team, was like.”–Dianne Hackborn, Android Framework Engineer“Androids is the engaging tale of a motley group of coders with a passion to make insanely great products who banged out the operating system when that idea seemed nuts.True to his geek genes, Chet Haase tells this remarkable tale of technical and business success from the trenches, an inspiring, massive collective effort of dozens of programmers who flipped their seemingly late timing to their advantage, and presaged a generation of platform builders. Read Androids to discover what it takes to create a hot tech team that shipped a product running today on more than 3 billion devices.”–Jonathan Littman, co-author of The Entrepreneurs Faces: How Makers, Visionaries and Outsiders Succeed, and author of The Fugitive Game

    In this book, author Gojko Adzic distills interviews with successful teams worldwide, sharing how they specify, develop, and deliver software, without defects, in short iterative delivery cycles.About the Technology Specification by Example is a collaborative method for specifying requirements and tests. Seven patterns, fully explored in this book, are key to making the method effective. The method has four main benefits: it produces living, reliable documentation; it defines expectations clearly and makes validation efficient; it reduces rework; and, above all, it assures delivery teams and business stakeholders that the software that's built is right for its purpose.About the Book This book distills from the experience of leading teams worldwide effective ways to specify, test, and deliver software in short, iterative delivery cycles. Case studies in this book range from small web startups to large financial institutions, working in many processes including XP, Scrum, and Kanban.This book is written for developers, testers, analysts, and business people working together to build great software.Purchase of the print book comes with an offer of a free PDF, ePub, and Kindle eBook from Manning. Also available is all code from the book.What's InsideCommon process patterns How to avoid bad practices Fitting SBE in your process 50+ case studies For additional resources go to specificationbyexample.com.

    In the past, discoveries often had to wait for the rise of the next generation to see questions in a new light and let go of old truisms. Today, in a world that is defined by a rapid rate of change, staying on the cutting edge has as much to do with shedding outdated notions as adopting new ones. In this spirit, John Brockman, publisher of the online salon Edge.org ("the world's smartest website"—The Guardian), asked 175 of the world's most influential scientists, economists, artists, and philosophers: What scientific idea is ready for retirement?Jared Diamond explores the diverse ways that new ideas emerge * Nassim Nicholas Taleb takes down the standard deviation * Richard Thaler and novelist Ian McEwan reveal the usefulness of "bad" ideas * Steven Pinker dismantles the working theory of human behavior * Richard Dawkins renounces essentialism * Sherry Turkle reevaluates our expectations of artificial intelligence * Physicist Andrei Linde suggests that our universe and its laws may not be as unique as we think * Martin Rees explains why scientific understanding is a limitless goal * Alan Guth rethinks the origins of the universe * Sam Harris argues that our definition of science is too narrow * Nobel Prize winner Frank Wilczek disputes the division between mind and matter * Lawrence Krauss challenges the notion that the laws of physics were preordained * plus contributions from Daniel Goleman, Mihaly Csikszentmihalyi, Nicholas Carr, Rebecca Newberger Goldstein, Matt Ridley, Stewart Brand, Sean Carroll, Daniel C. Dennett, Helen Fisher, Douglas Rushkoff, Lee Smolin, Kevin Kelly, Freeman Dyson, and others.

    

    More than four dozen architects -- including Neal Ford, Michael Nygard, and Bill de hOra -- offer advice for communicating with stakeholders, eliminating complexity, empowering developers, and many more practical lessons they've learned from years of experience. Among the 97 principles in this book, you'll find useful advice such as:Don't Put Your Resume Ahead of the Requirements (Nitin Borwankar) Chances Are, Your Biggest Problem Isn't Technical (Mark Ramm) Communication Is King; Clarity and Leadership, Its Humble Servants (Mark Richards) Simplicity Before Generality, Use Before Reuse (Kevlin Henney) For the End User, the Interface Is the System (Vinayak Hegde) It's Never Too Early to Think About Performance (Rebecca Parsons) To be successful as a software architect, you need to master both business and technology. This book tells you what top software architects think is important and how they approach a project. If you want to enhance your career, 97 Things Every Software Architect Should Know is essential reading.

    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.

    Kanban leverages visual management techniques to involve stakeholders and to facilitate understanding of how the work works. Through limiting the amount of work in process, and by focusing on finishing that work as soon as possible, kanban helps you to adjust demand to capacity, to reduce lead times and to create a driver for continuous improvement.Kanban in Action is a down-to-earth, no-frills, get-to-know-the-ropes introduction to kanban. It's based on the real-world experience and observations from two kanban coaches who have introduced this process to dozens of teams. In this book, you'll discover basic but powerful techniques on how to visualize and track work, how to construct a kanban board, how to visualize queues and bottlenecks, and much much more. You'll learn the principles of why kanban works as well as nitty-gritty details like how to use different color stickies to help you organize and track your work items.

    It can almost be summed up by the button on every page: "Buy now with one click."Why has Amazon been so successful? Much of it has to do with Jeff Bezos, the CEO and founder, whose unique combination of character traits and business strategy have driven Amazon to the top of the online retail world.Richard Brandt charts Bezos's rise from computer nerd to world- changing entrepreneur. His success can be credited to his forward-looking insights and ruthless business sense. Brandt explains: Why Bezos decided to allow negative product reviews, correctly guessing that the earned trust would outweigh possible lost sales. Why Amazon zealously guards some patents yet freely shares others. Why Bezos called becoming profitable the "dumbest" thing they could do in 1997. How Amazon.com became one of the only dotcoms to survive the bust of the early 2000s. Where the company is headed next.Through interviews with Amazon employees, competitors, and observers, Brandt has deciphered how Bezos makes decisions. The story of Amazon's ongoing evolution is a case study in how to reinvent an entire industry, and one that anyone in business today ignores at their peril.

    This book demystifies agile methodologies: why they’re designed the way they are, what problems they address, and the values, principles, and ideas they embody.Learning Agile helps you recognize the principles that apply to development problems specific to your team, company, and projects. You’ll discover how to use that information to guide your choice of methodologies and practices.With this book you’ll learn:Values that effective software teams possessThe methodologies that embody those valuesThe practices that make up those methodologiesAnd principles that help you bring those values, methodologies, and practices to your team and your company

    C. R. Licklider, whose visionary dream of a human-computer symbiosis transformed the course of modern science and led to the development of the personal computer. Reprint.

    They face monumental decisions in unpredictable times; their actions have implications far beyond their own organizations; and they are judged mercilessly and incessantly by both their constituents and the media. Professionals, then, would do well to study the leadership traits that made Kennedy one of the most respected, beloved, and influential world leaders in modern history. John F. Kennedy on Leadership analyzes what made Kennedy, both before and during his Presidency, a unique and dominant force who would serve as the standard by which future leaders would be judged. Readers will learn the value of: * Planning and decision making: Consult widely, then act. * Crisis management: Don’t let events manage you. * Building a team: Find your own "Bobby." * Independence: Don’t follow the crowd. * Mistakes: Learn from them and move on. This timely (and timeless) book will be of interest to anyone involved in leadership.