. . And here's what you can do about it on Monday morning with the definitive how-to book from the world's leading authority on innovationWhen it comes to innovation, Curt Carlson and Bill Wilmot of SRI International know what they are talking about--literally. SRI has pioneered innovations that day in and day out are part of the fabric of your life, such as:-The computer mouse and the personal computer interface you use at home and work-The high-definition television in your living room-The unusual numbers at the bottom of your checks that enable your bank to maintain your account balance correctly-The speech-recognition system used by your financial services firm when you call for your account balance or to make a transaction.Each of these innovations--and literally hundreds of others--created new value for customers. And that's the central message of this book. Innovation is not about inventing clever gadgets or just "creativity." It is the successful creation and delivery of a new or improved product or service that provides value for your customer and sustained profit for your organization. The first black-and-white television, for example, was just an interesting, cool invention until David Sarnoff created an innovation--a network--that delivered programming to an audience.The genius of this book is that it provides the "how" of innovation. It makes innovation practical by getting two groups who are often disconnected--the managers who make decisions and the people on the front lines who create the innovations--onto the same page. Instead of smart people grousing about the executive suite not recognizing a good idea if they tripped over it and the folks on the top floor wondering whether the people doing the complaining have an understanding of market realities, Carlson and Wilmot's five disciplines of innovation focus attention where it should be: on the creation of valuable new products and services that meet customer needs.Innovation is not just for the "lone genius in the garage" but for you and everyone in your enterprise. Carlson and Wilmot provide a systematic way to make innovation practical, one intimately tied to the way things get done in your business.Teamwork isn't enough; Creativity isn't enough; A new product idea isn't enoughTrue innovation is about delivering value to customers. Innovation reveals the value-creating processes used by SRI International, the organization behind the computer mouse, robotic surgery, and the domain names .com, .org, and .gov. Curt Carlson and Bill Wilmot show you how to use these practical, tested processes to create great customer value for your organization.

    It has made countless new businesses possible and presents a massive opportunity for large enterprises to innovate like startups and retire decades of technical debt. But making the most of the cloud requires much more from enterprises than just a technology change. Stephen Orban led Dow Jones’s journey toward digital agility as their CIO and now leads AWS’s Enterprise Strategy function, where he helps leaders from the largest companies in the world transform their businesses. As he demonstrates in this book, enterprises must re-train their people, evolve their processes, and transform their cultures as they move to the cloud. By bringing together his experiences and those of a number of business leaders, Orban shines a light on what works, what doesn’t, and how enterprises can transform themselves using the cloud.

    From lean and project management to statistics and data analysis, the DMAIC process is explained in a clear and insightful manner. Figures, tables, references, useful appendices, and a full sample test only add to this book's comprehensiveness.

    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.

    Our increasingly complex world demands that we continuously learn from failures (and successes) in order to survive and thrive. And yet, our learning is too often undermined. We construct biased but comfortable stories, which often feature a simple, single "root cause"--a villain, someone to take the blame. Having done that, we short-circuit the possibility of developing any deeper understanding of the complex systems we work with. With this common approach, our systems will become more fragile and drift into failure. In this concise and entertaining book, I.T. veteran Dave Zwieback describes an incident that threatens the very existence of a large financial institution, and the counterintuitive steps its leadership took to stop the downward spiral. Their novel approach is grounded in proven concepts from complexity science, resilience engineering, human factors, cognitive science, and organizational psychology. It allows us to identify the underlying conditions for failure, and make our systems (and organizations) safer and more resilient.- Get a clear understanding of the downside of blame- Learn how to identify (and counteract) cognitive biases in groups- See how organizations can determine the real root cause of problems- Establish real accountability with your organization- Use the Learning Review Framework to fully learn from failures of complex systems- Find practical insights and tips for moving beyond blame in your own organization

    The unexpected is often dramatic, as with hurricanes or terrorist attacks. But the unexpected can also come in more subtle forms, such as a small organizational lapse that leads to a major blunder, or an unexamined assumption that costs lives in a crisis. Why are some organizations better able than others to maintain function and structure in the face of unanticipated change? Authors Karl Weick and Kathleen Sutcliffe answer this question by pointing to high reliability organizations (HROs), such as emergency rooms in hospitals, flight operations of aircraft carriers, and firefighting units, as models to follow. These organizations have developed ways of acting and styles of learning that enable them to manage the unexpected better than other organizations. Thoroughly revised and updated, the second edition of the groundbreaking book Managing the Unexpected uses HROs as a template for any institution that wants to better organize for high reliability.

    It’s helpful for learning Agile and Scrum, and also for a basic preparation for the PSM I exam (Professional Scrum Master level 1). It can also act as a simple reference for Scrum practitioners.

    "This book is a guide to how we do product development at Basecamp. It’s also a toolbox full of techniques that you can apply in your own way to your own process.Whether you’re a founder, CTO, product manager, designer, or developer, you’re probably here because of some common challenges that all software companies have to face."

    Unfortunately, reliable guidance on Agile management has been scarce indeed. Now, leading Agile manager Jurgen Appelo fills that gap, introducing a realistic approach to leading, managing, and growing your Agile team or organization. Writing for current managers and developers moving into management, Appelo shares insights that are grounded in modern complex systems theory, reflecting the intense complexity of modern software development. Appelo's Management 3.0 model recognizes that today's organizations are living, networked systems; and that management is primarily about people and relationships. Management 3.0 doesn't offer mere checklists or prescriptions to follow slavishly; rather, it deepens your understanding of how organizations and Agile teams work and gives you tools to solve your own problems. Drawing on his extensive experience as an Agile manager, the author identifies the most important practices of Agile management and helps you improve each of them. Coverage includes - Getting beyond "Management 1.0" control and "Management 2.0" fads - Understanding how complexity affects your organization - Keeping your people active, creative, innovative, and motivated - Giving teams the care and authority they need to grow on their own - Defining boundaries so teams can succeed in alignment with business goals - Sowing the seeds for a culture of software craftsmanship - Crafting an organizational network that promotes success - Implementing continuous improvement that actually works Thoroughly pragmatic-and never trendy-Jurgen Appelo's Management 3.0 helps you bring greater agility to any software organization, team, or project.

    Even if you don't have change management in your job description, your job involves change. Change is a given as modern organizations respond to market and technology advances, make improvements, and evolve practices to meet new challenges. This is not a simple process on any level. Often, there is no indisputable right answer, and responding requires trial and error, learning and unlearning. Whatever you choose to do, it will interact with existing policies and structures in unpredictable ways. And there is, quite simply, a natural human resistance to being told to change.Rather than creating more rigorous preconceived plans or imposing change by decree, agile software developer turned organizational change expert Esther Derby offers change by attraction, an approach that is adaptive and responsive and engages people in learning, evolving, and owning the new way. She presents a set of seven heuristics--guides to problem-solving--that empower people to achieve outcomes within broad constraints using their personal ingenuity and creativity.When you work by attraction, you give space and support for people to feel the loss that comes with change and help them see what is valuable about the future you propose. Resistance fades because people feel there is nothing to push against--only something they want to move toward. Derby's approach clears the fog to provide a new way forward that honors people and creates safety for change.

    But how do you build the best team organization for your specific goals, culture, and needs? Team Topologies is a practical, step-by-step, adaptive model for organizational design and team interaction based on four fundamental team types and three team interaction patterns. It is a model that treats teams as the fundamental means of delivery, where team structures and communication pathways are able to evolve with technological and organizational maturity.In Team Topologies, IT consultants Matthew Skelton and Manuel Pais share secrets of successful team patterns and interactions to help readers choose and evolve the right team patterns for their organization, making sure to keep the software healthy and optimize value streams.Team Topologies is a major step forward in organizational design for software, presenting a well-defined way for teams to interact and interrelate that helps make the resulting software architecture clearer and more sustainable, turning inter-team problems into valuable signals for the self-steering organization.

    Their conclusion? Even among people who have spent decades learning the technical side of their jobs, most haven't really focused on the human component. Learning to collaborate is just as important to success. If you invest in the soft skills of your job, you can have a much greater impact for the same amount of effort.The authors share their insights on how to lead a team effectively, navigate an organization, and build a healthy relationship with the users of your software. This is valuable information from two respected software engineers whose popular series of talks--including Working with Poisonous People--has attracted hundreds of thousands of followers.

    But how much time you actually spend on your projects, and how much time do you spend responding to emergencies? This book will introduce you to different ways of ordering all of the projects you are working on now, and help you figure out how to staff those projects--even when you've run out of project teams to do the work. Once you learn to manage your portfolio better, you'll avoid emergency "firedrills." The trick is adopting lean and agile approaches to projects, whether they are software projects, projects that include hardware, or projects that depend on chunks of functionality from other suppliers. You may be accustomed to spending time in meetings where you still don't have the data you need to evaluate your projects. Here, with a few measures, you'll be able to quickly evaluate each project and come to a decision quickly. You'll learn how to define your team's, group's, or department's mission with none of the buzzwords that normally accompany a mission statement. Armed with the work and the mission, you can make those decisions that define the true leaders in the organization.

    With pedagogical use of second color, it covers devices in one place so that circuit characteristics are developed early.

    ―Jacob Boudreau CTO of Stord | Forbes 30 Under 30 Joel's book and show provide incredible insights for young startup developers and fellow CTOs alike. Joel offers a human perspective and real practical advice on the challenges and opportunities facing every Modern CTO. ― Christian Saucier | Entrepreneur and P2P Systems Architect I've really come to respect what Joel is doing in the community. His podcast and book are filling a much needed hole and I'm excited to see what else the future has in store. ― Don Pawlowski Chief Technology Officer at University Tees Modern CTO Everything you need to know to be a Modern CTO. Developers are not CTOs, but developers can learn how to be CTOs. In Modern CTO, Joel Beasley provides readers with an in-depth road map on how to successfully navigate the unexplored and jagged transition between these two roles. Drawing from personal experience, Joel gives a refreshing take on the challenges, lessons, and things to avoid on this journey.Readers will learn how Modern CTOs: Manage deadlines Speak up Know when to abandon ship and build a better one Deal with poor code Avoid getting lost in the product and know what UX mistakes to watch out for Manage people and create momentum … plus much more Modern CTO is the ultimate book when making the leap from developer to CTO. Update: Kindle Formatting issues resolved 5/13/18. Thank you for the feedback.