Learn the basics of do-it-yourself ZFS storage on Linux. This book delivers explanations of key features and provides best practices for planning, creating and sharing your storage. ZFS as a file system simplifies many aspects of the storage administrator´s day-to-day job and solves a lot of problems that administrators face, but it can be confusing. Introducing ZFS on Linux addresses some of these issues and shows you how to resolve them. This book explains the technical side of ZFS, through planning the hardware list to planning the physical and logical layout of the storage. What You´ll Learn Understand the gains ZFS gives system and storage administrators and utilize its features Install and configure ZFS software Create and maintain ZFS pool Administer ZFS storage, including sharing Who This Book is For This book is ideal for those who already have experience working with Linux systems but want to understand the bare basics of ZFS before moving further.
Gain industry best practices from planning to implementing Microsoft Teams and learn how to enable, configure, and integrate user provisioning, management, and monitoring. This book also covers troubleshooting Teams with step-by-step instructions and examples. Introducing Microsoft Teams gives you the comprehensive coverage you need to creatively utilize Microsoft Teams services. The author starts by giving an introduction to Microsoft Teams and its architecture followed by optimizing the Teams experience where he describes how organizations can prepare for Teams and enhance existing services. He further shows you how to manage and control the Microsoft Teams experience along with its capabilities and enhancements. You´ll learn how to migrate from Skype for Business to Microsoft Teams with a step-by-step tutorial. Finally, you´ll get to grips with Teams troubleshooting and best practices. This book has detailed coverage that helps you exploit every capability Microsoft Teams has to offer. It provides the answers you need and the insight that will make your journey from Skype for Business to Teams easier. What You Will Learn Enable guest access in Teams Provision and manage users in Teams Administrate Teams and channels Optimize the Teams experience Enable and configure Microsoft Teams Prepare your network for Microsoft Teams and Office 365 services Migrate from Skype for Business to Microsoft Teams Who This Book Is For Unified communication administrators and IT support engineers who are currently supporting an existing unified communication platform such as Skype for Business (Lync). It would also help support engineers, new administrators, and consultant to start their journey with Teams.
The book, while introducing readers to the auction mechanism for resource provisioning in cloud computing, also endeavors to provide structured literature on the subject. Since various models have been proposed, it will help readers to formulate the cloud resource provisioning problem using the auction approach. The book also discusses challenges for resource provisioning in detail, helping to shape future research. The target audience for this book includes computer scientists, economists, industry professionals, research scholars, and postgraduate students. Computer science readers of this book will come to see that economics-based method are quite helpful in computer science, especially for resource provisioning. Readers with a cloud computing background will come to recognize the importance of dynamic pricing, the specific benefits of auctions, and how to formulate auctions for cloud computing. Lastly, readers from the economics community will come to understand their role in cloud computing, as well as where and how they can contribute.
Pragmatic Insights for Successfully Managing Your Unique Agile Team or Organization In many organizations, management is the biggest obstacle to successful Agile development. 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; that you can´t simply let them run themselves; 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 and trainer, Appelo identifies the most valuable elements of Agile management, and helps you improve each of them. Coverage includes Getting beyond ´´Management 1.0´´ command hierarchies, and ´´Management 2.0´´ fads Understanding how complexity and non-linearity affect your organization-and why the best-laid plans so often fail Giving teams the care and feeding they need to grow on their own Defining boundaries and constraints, so teams can succeed in alignment with company goals Anticipating issues teams won´t or can´t resolve by themselves Sowing the seeds for a culture of software craftsmanship Keeping your people active, creative, motivated, and energized Helping teams develop crucial missing skills and disciplines Crafting organizational networks and communication flows that promote success Making change desirable-and making stagnation painful Implementing continuous improvement that actually works Thoroughly pragmatic-and never trendy-Jurgen Appelo´s Management 3.0 will help you bring greater agility to any software organization, team, or project. Product Description In many organizations, management is the biggest obstacle to successful Agile development. 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. Backcover In many organizations, management is the biggest obstacle to successful Agile development. 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
An airline is supposed to make the experience of booking a flight easy, trouble free, and reliable. But when scheduling software breaks down and flights get canceled, customers will walk, and heads will roll. That´s what Leigh Freemark faces the day she and her team launch a software upgrade that fails spectacularly and hits the media immediately. As Senior Director of Quality Assurance, her job is to make sure that code is market ready. And she´s the one who must face the music when it doesn´t. Tasked by senior management to find and fix the source of the failure, Leigh discovers just how essential it has become to radically improve the process of software development by introducing a concept called continuous testing. She must quickly learn what it means, how it works, and how to build it into her company´s legacy system. But she soon discovers that managing change is much more difficult than it first appears. The airline business is changing fast, yet old traditions and loyalties still dominate. As she fights to convince her team to change or perish, she discovers that obstructions and opportunities come in surprising forms. In The Kitty Hawk Venture , the authors deliver a sound lesson in the importance of continuous testing while taking the reader inside the world of commercial aviation. Each chapter delivers distinct and vital learning opportunities wrapped inside a fast-moving narrative complete with interesting characters, intriguing situations, and even some humor. The book concludes with a ´´Flight Plan for Continuous Testing´´ that stands on its own as a valuable resource guide for digital leaders in their continuous testing journey. The story is immediately relatable to anyone who has worked in software development or for the companies that rely on it. Who This Book Is For C-level executives, VPs of apps and quality, VPs of DevOps, architecture and strategy managers, and SMB and enterprise professionals
This book seeks to promote the structured, standardized and accurate use of software measurement at all levels of modern software development companies. To do so, it focuses on seven main aspects: sound scientific foundations, cost-efficiency, standardization, value-maximization, flexibility, combining organizational and technical aspects, and seamless technology integration. Further, it supports companies in their journey from manual reporting to automated decision support by combining academic research and industrial practice. When scientists and engineers measure something, they tend to focus on two different things. Scientists focus on the ability of the measurement to quantify whatever is being measured; engineers, however, focus on finding the right qualities of measurement given the designed system (e.g. correctness), the system´s quality of use (e.g. ease of use), and the efficiency of the measurement process. In this book, the authors argue that both focuses are necessary, and that the two are complementary. Thus, the book is organized as a gradual progression from theories of measurement (yes, you need theories to be successful!) to practical, organizational aspects of maintaining measurement systems (yes, you need the practical side to understand how to be successful). The authors of this book come from academia and industry, where they worked together for the past twelve years. They have worked with both small and large software development organizations, as researchers and as measurement engineers, measurement program leaders and even teachers. They wrote this book to help readers define, implement, deploy and maintain company-wide measurement programs, which consist of a set of measures, indicators and roles that are built around the concept of measurement systems. Based on their experiences introducing over 40,000 measurement systems at over a dozen companies, they share essential tips and tricks on how to do it right and how to avoid common pitfalls.
Mike Burrows vermittelt in diesem Buch einen neuen Ansatz, Kanban zu verstehen und einzusetzen. Er beschreibt die Methode von innen heraus anhand von neun Werten, wodurch er den Prinzipien und Praktiken Kanbans ein starkes Gerüst verleiht. Die Werte bieten ein effizientes Instrument, um die Umsetzung der Kanban-Vorgehensweise zu beurteilen und so anhaltende Veränderungen zu erzielen. Die neun Werte der Kanban-Methode sind im ersten Teil des Buches mit vielen Praxisbeispielen beschrieben: Transparenz, Balance, Zusammenarbeit, Kundenfokus, Arbeitsfluss (Flow), Führung (Leadership), Verständnis, Einverständnis und Respekt. Abschließend werden zwei jüngere Konzepte vorgestellt: die drei Agenden und die Kanban-Linse. Teil II befasst sich mit verwandten Methoden, die dabei helfen, die Kanban-Methode noch effektiver einzusetzen: Systems Thinking, Lean Development, agile Vorgehensweisen und die Engpasstheorie. Der letzte Teil ist eine Schritt-für-Schritt-Anleitung zur Implementierung von Kanban mittels STATIK (Systems Thinking Approach to Introducing Kanban). Aufgezeigt werden praktische Wege, wie Sie Anforderungen und Bedürfnissen aus der Organisation, von Kollegen und Kunden noch besser gerecht werden können. Das Buch gibt einen umfassenden Einblick in den aktuellen Stand der Kanban-Methode. Einsteiger werden verstehen, warum und wie Kanban funktioniert, sodass sie es wirksam in ihre bestehenden Strukturen und Teams integrieren können. Erfahrene Anwender lernen neue Werkzeuge sowie Vorgehensweisen kennen und gewinnen einen neuen Blick auf Kanban. ´This book is now the recommended text book for the LeanKanban Foundation level training ´Getting Started with Kanban´. Mike´s Kanban from the Inside has by far the most extensive and up-todate coverage of Kanban used in creative and knowledge work businesses in the 21st Century than anything published to date. David J. Anderson zur englischen Ausgabe
Proven strategies for maintaining and optimizing legacy code to get the most out of your existing applications. Examples in C-sharp, C++, and Java, as well as strategies for better using the industry standard modeling language: UML 2.0 Addresses the very concrete problems that programmers face working in the context of large untested code bases Based on successful classes for Object Mentor, the author helps organizations maintain older systems rather than go to the cost of developing new ones This book provides programmers with the ability to cost effectively handle common legacy code problems without having to go through the hugely expensive task of rewriting all existing code. It describes a series of practical strategies that developers can employ to bring their existing software applications under control. The author provides useful guidance about how to use these strategies when refactoring or making functional changes to code bases. One of the book´s key points is that it teaches developers to write tests that can be used to make sure they are not unintentionally changing the application as they optimize it. Examples are provided in Java, C++, and Csharp, and the book assumes that the reader has some knowledge of UML notation. Strategies using UML and code in C++ and Java primarily while language independent advice will be delivered in side bars and appendices for language specific users. Product Description This book provides programmers with the ability to cost effectively handlecommon legacy code problems without having to go through the hugelyexpensive task of rewriting all existing code. It describes a series of practicalstrategies that developers can employ to bring their existing softwareapplications under control. The author provides useful guidance about how touse these strategies when refactoring or making functional changes to codebases. One of the book´s key points is that it teaches developers to write teststhat can be used to make sure they are not unintentionally changing theapplication as they optimize it. Examples are provided in Java, C++, and Csharp,and the book assumes that the reader has some knowledge of UMLnotation. Strategies using UML and code in C++ and Java primarily whilelanguage independent advice will be delivered in side bars and appendices forlanguage specific users. Backcover Get more out of your legacy systems: more performance, functionality, reliability, and manageability Is your code easy to change? Can you get nearly instantaneous feedback when you do change it? Do you understand it? If the answer to any of these questions is no, you have legacy code, and it is draining time and money away from your development efforts. In this book, Michael Feathers offers start-to-finish strategies for working more effectively with large, untested legacy code bases. 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 structure This book also includes a catalog of twenty-four dependency-breaking techniques that help you work with program elements in isolation and make safer changes. © Copyright Pearson Education. All rights reserved. Preface. Introduction. I. THE MECHANICS OF CHANGE. 1. Changing Software. 2. Working with Feedback. 3. Sensing and Separation. 4. The Seam Model. 5. Tools. II. CHANGING SOFTWARE. 6. I Don´t Have Much Time and I Have To Change It. 7. It Takes Forever To Make a Change. 8. How Do I Add a Feature? 9. I Can´t Get This Class into a Test Harness. 10. I Can´t Run This Method into a Test Harness. 11. I Need to Make a Change. What Methods Should I Test? 12. I Need to Make Many Changes In One Area Do I Have To Break. 13. I Need To Make a Change but I Don´t Know What Tests To Write. 14. Dependencies on Libraries Are Killing Me. 15. My Application Is All API Calls. 16. I Don´t Understand the Code