Empfehlungen basierend auf "Not Just Another Job"

Design your networks to successfully manage their growing complexityNetwork professionals have often been told that today’s modern control planes would simplify their networks. The opposite has happened: Technologies like SDN and NFV, although immensely valuable, are exacerbating complexity instead of solving it. Navigating Network Complexity is the first comprehensive guide to managing this complexity in both deployment and day-to-day operations.Russ White and Jeff Tantsura introduce modern complexity theory from the standpoint of the working network engineer, helping you apply it to the practical problems you face every day. Avoiding complex mathematical models, they show how to characterize network complexity, so you can understand it and control it.The authors examine specific techniques and technologies associated with network control planes, including SDNs, fast reroute, segment routing, service chaining, and cloud computing. They reveal how each of these affects network design and complexity and help you anticipate causes of failure in highly complex systems.Next, they turn to modern control planes, examining the fundamental operating principles of SDNs, such as OpenFlow and I2RS, network and other service function virtualization, content distribution networks, Layer 2 fabrics, and service chaining solutions. You’ll learn how each of these might both resolve and increase complexity in network design and operations and what you can do about it.Coverage includes:Defining complexity, understanding its components, and measuring it Mastering a straightforward “state, speed, and surface” model for analyzing complexity Controlling complexity in design, deployment, operations, protocols, and programmable networks Understanding how complex network systems begin to fail and how to prevent failure Recognizing complexity tradeoffs in service virtualization and service chaining Managing new challenges of complexity in virtualized and cloud environments Learning why constructs such as hierarchical design, aggregation, and protocol layering work and when they work best Choosing the right models to contain complexity as your network changesFrom start to finish, Navigating Network Complexity helps you assess the true impact of new network technologies, so they can capture more value with fewer problems.

“Our job as Scrum professionals is to continually improve our ability to use Scrum to deliver products and services that help customers achieve valuable outcomes. This book will help you to improve your ability to apply Scrum.” –From the Foreword by Ken Schwaber, co-author of Scrum Mastering Professional Scrum is for anyone who wants to deliver increased value by using Scrum more effectively. Leading Scrum practitioners Stephanie Ockerman and Simon Reindl draw on years of Scrum training and coaching to help you return to first principles and apply Scrum with the professionalism required to achieve its transformative potential. The authors aim to help you focus on proven Scrum approaches for improving quality, getting and using fast feedback, and becoming more adaptable, instead of “going through the motions” and settling for only modest improvements. Whether you’re a Scrum Master, Development Team member, or Product Owner, you’ll find practical advice for facing challenges with transparency and courage, overcoming a wide array of common challenges, and continually improving your Scrum practice. Realistically assess your current Scrum practice, and identify areas for improvement Recognize what a great Scrum Team looks like and get there Focus on “Done”–not “sort-of-Done” or “almost-Done” Measure and optimize the value delivered by every Product Increment Improve the way you plan, develop, and grow Clear away wider organizational impediments to agility and professionalism Overcome common misconceptions that stand in the way of progress Register your book for convenient access to downloads, updates, and/or corrections as they become available. See inside book for details.

How do I start a business on a budget? How do I find my first 100 customers and make my first £100k? How do I build a network and get my business noticed?

How inclusive methods can build elegant design solutions that work for all.Sometimes designed objects reject their users: a computer mouse that doesn't work for left-handed people, for example, or a touchscreen payment system that only works for people who read English phrases, have 20/20 vision, and use a credit card. Something as simple as color choices can render a product unusable for millions. These mismatches are the building blocks of exclusion. In Mismatch, Kat Holmes describes how design can lead to exclusion, and how design can also remedy exclusion. Inclusive design methods—designing objects with rather than for excluded users—can create elegant solutions that work well and benefit all.Holmes tells stories of pioneers of inclusive design, many of whom were drawn to work on inclusion because of their own experiences of exclusion. A gamer and designer who depends on voice recognition shows Holmes his “Wall of Exclusion,” which displays dozens of game controllers that require two hands to operate; an architect shares her firsthand knowledge of how design can fail communities, gleaned from growing up in Detroit's housing projects; an astronomer who began to lose her eyesight adapts a technique called “sonification” so she can “listen” to the stars.Designing for inclusion is not a feel-good sideline. Holmes shows how inclusion can be a source of innovation and growth, especially for digital technologies. It can be a catalyst for creativity and a boost for the bottom line as a customer base expands. And each time we remedy a mismatched interaction, we create an opportunity for more people to contribute to society in meaningful ways.

Improve and Accelerate Software Delivery for Large, Distributed, Complex Projects The Nexus Framework is the simplest, most effective approach to applying Scrum at scale across multiple teams, sites, and time zones. Created by Scrum.org--the pioneering Scrum training and certification organization founded by Scrum co-creator Ken Schwaber--Nexus draws on decades of experience to address the unique challenges teams face in coming together, sharing work, and managing and minimizing dependencies. The NexusTM Framework for Scaling Scrum is a concise book that shows how Nexus helps teams to deliver a complex, multi-platform, software-based product in short, frequent cycles, without sacrificing consistency or quality, and without adding unnecessary complexity or straying from Scrum's core principles. Using an extended case study, the authors illustrate how Nexus helps teams solve common scaling challenges like reducing cross-team dependencies, preserving team self-organization and transparency, and ensuring accountability. Understand the challenges of delivering working, integrated product increments with multiple teams, and how Nexus addresses them Form a Nexus around a new or existing product and learn how that Nexus sets goals and plans its work Run Sprints within a Nexus, provide transparency into progress, conduct effective Nexus Sprint reviews, and use Nexus Sprint Retrospectives to continuously improve Overcome the distributed team collaboration challenges Register your product at informit.com/register for convenient access to downloads, updates, and/or corrections as they become available.

Since Don’t Make Me Think was first published in 2000, hundreds of thousands of Web designers and developers have relied on usability guru Steve Krug’s guide to help them understand the principles of intuitive navigation and information design. Witty, commonsensical, and eminently practical, it’s one of the best-loved and most recommended books on the subject. Now Steve returns with fresh perspective to reexamine the principles that made Don’t Make Me Think a classic–with updated examples and a new chapter on mobile usability. And it’s still short, profusely illustrated…and best of all–fun to read. If you’ve read it before, you’ll rediscover what made Don’t Make Me Think so essential to Web designers and developers around the world. If you’ve never read it, you’ll see why so many people have said it should be required reading for anyone working on Web sites. “After reading it over a couple of hours and putting its ideas to work for the past five years, I can say it has done more to improve my abilities as a Web designer than any other book.” –Jeffrey Zeldman, author of Designing with Web Standards  

When it comes to making your business more profitable and successful, don't look to re-engineering for answers. A better way is to apply the concept of kaizen, which mean making simple, common-sense improvements and refinements to critical business processes.The result: greater productivity, quality, and profits achieved with minimal cost, time, and effort invested. In this book, you discover how to maximize the results of kaizen by applying it to gemba--business processes involved in the manufacture of products and the rendering of services--the areas of your business where, as the author puts it, the "real action" takes place.

Building upon the success of best-sellers The Clean Coder and Clean Code, legendary software craftsman Robert C. "Uncle Bob" Martin shows how to bring greater professionalism and discipline to application architecture and design.   As with his other books, Martin's Clean Architecture doesn't merely present multiple choices and options, and say "use your best judgment": it tells you what choices to make, and why those choices are critical to your success. Martin offers direct, no-nonsense answers to key architecture and design questions like: What are the best high level structures for different kinds of applications, including web, database, thick-client, console, and embedded apps? What are the core principles of software architecture? What is the role of the architect, and what is he/she really trying to achieve? What are the core principles of software design? How do designs and architectures go wrong, and what can you do about it? What are the disciplines and practices of professional architects and designers? Clean Architecture is essential reading for every software architect, systems analyst, system designer, and software manager -- and for any programmer who aspires to these roles or is impacted by their work.

Software development projects can be fun, productive, and even daring. Yet they can consistently deliver value to a business and remain under control. Extreme Programming (XP) was conceived and developed to address the specific needs of software development conducted by small teams in the face of vague and changing requirements. This new lightweight methodology challenges many conventional tenets, including the long-held assumption that the cost of changing a piece of software necessarily rises dramatically over the course of time. XP recognizes that projects have to work to achieve this reduction in cost and exploit the savings once they have been earned. Fundamentals of XP include: Distinguishing between the decisions to be made by business interests and those to be made by project stakeholders. Writing unit tests before programming and keeping all of the tests running at all times. Integrating and testing the whole system--several times a day. Producing all software in pairs, two programmers at one screen. Starting projects with a simple design that constantly evolves to add needed flexibility and remove unneeded complexity. Putting a minimal system into production quickly and growing it in whatever directions prove most valuable. Why is XP so controversial? Some sacred cows don't make the cut in XP: Don't force team members to specialize and become analysts, architects, programmers, testers, and integrators--every XP programmer participates in all of these critical activities every day. Don't conduct complete up-front analysis and design--an XP project starts with a quick analysis of the entire system, and XPprogrammers continue to make analysis and design decisions throughout development. Develop infrastructure and frameworks as you develop your application, not up-front--delivering business value is the heartbeat that drives XP projects. Don't write and maintain implementation documentation--communication in XP projects occurs face-to-face, or through efficient tests and carefully written code. You may love XP, or you may hate it, but "Extreme Programming Explained" will force you to take a fresh look at how you develop software. 0201616416B04062001

Protecting information, identifying undercover agents, and operating clandestinely—efforts known as counterintelligence—are the primary objectives of terrorist groups evading detection by intelligence and law enforcement officials. Some strategies work well, some fail, and those tasked with tracking these groups are deeply invested in the difference. Discussing the challenges terrorist groups face as they multiply and plot international attacks, while at the same time providing a framework for decoding the strengths and weaknesses of their counterintelligence, Blake W. Mobley provides an indispensable text for the intelligence, military, homeland security, and law enforcement fields. He outlines concrete steps for improving the monitoring, disruption, and elimination of terrorist cells, primarily by exploiting their mistakes in counterintelligence. A key component of Mobley's approach is to identify and keep close watch on areas that often exhibit weakness. While some counterintelligence pathologies occur more frequently among certain terrorist groups, destructive bureaucratic tendencies, such as mistrust and paranoia, pervade all organizations. Through detailed case studies, Mobley shows how to recognize and capitalize on these shortcomings within a group's organizational structure, popular support, and controlled territory, and he describes the tradeoffs terrorist leaders make to maintain cohesion and power. He ultimately shows that no group can achieve perfect secrecy while functioning effectively and that every adaptation or new advantage supposedly attained by these groups also produces new vulnerabilities.