So, why does conventional wisdom insist that software engineers focus primarily on the design and development of large-scale computing systems?In this collection of essays and articles, key members of Google's Site Reliability Team explain how and why their commitment to the entire lifecycle has enabled the company to successfully build, deploy, monitor, and maintain some of the largest software systems in the world. You'll learn the principles and practices that enable Google engineers to make systems more scalable, reliable, and efficient--lessons directly applicable to your organization.This book is divided into four sections: Introduction--Learn what site reliability engineering is and why it differs from conventional IT industry practicesPrinciples--Examine the patterns, behaviors, and areas of concern that influence the work of a site reliability engineer (SRE)Practices--Understand the theory and practice of an SRE's day-to-day work: building and operating large distributed computing systemsManagement--Explore Google's best practices for training, communication, and meetings that your organization can use

    Based on numerous interviews, this book reveals exclusive new information about how Apple innovates, deals with its suppliers, and is handling the transition into the post Jobs era.

    Find out how the Swedish police combined XP, Scrum, and Kanban in a 60-person project. From start to finish, you'll see how to deliver a successful product using Lean principles. We start with an organization in desperate need of a new way of doing things and finish with a group of sixty, all working in sync to develop a scalable, complex system. You'll walk through the project step by step, from customer engagement, to the daily "cocktail party," version control, bug tracking, and release. In this honest look at what works--and what doesn't--you'll find out how to: Make quality everyone's business, not just the testers. Keep everyone moving in the same direction without micromanagement. Use simple and powerful metrics to aid in planning and process improvement. Balance between low-level feature focus and high-level system focus. You'll be ready to jump into the trenches and streamline your own development process.ContentsForewordPrefacePART I: HOW WE WORK1. About the Project1.1 Timeline 51.2 How We Sliced the Elephant 61.3 How We Involved the Customer 72. Structuring the Teams3. Attending the Daily Cocktail Party3.1 First Tier: Feature Team Daily Stand-up3.2 Second Tier: Sync Meetings per Specialty3.3 Third Tier: Project Sync Meeting4. The Project Board4.1 Our Cadences4.2 How We Handle Urgent Issues and Impediments5. Scaling the Kanban Boards6. Tracking the High-Level Goal7. Defining Ready and Done7.1 Ready for Development7.2 Ready for System Test7.3 How This Improved Collaboration 8. Handling Tech Stories8.1 Example 1: System Test Bottleneck8.2 Example 2: Day Before the Release8.3 Example 3: The 7-Meter Class9. Handling Bugs9.1 Continuous System Test9.2 Fix the Bugs Immediately9.3 Why We Limit the Number of Bugs in the Bug Tracker9.4 Visualizing Bugs9.5 Preventing Recurring Bugs10. Continuously Improving the Process10.1 Team Retrospectives10.2 Process Improvement Workshops10.3 Managing the Rate of Change11. Managing Work in Progress11.1 Using WIP Limits11.2 Why WIP Limits Apply Only to Features12. Capturing and Using Process Metrics12.1 Velocity (Features per Week)12.2 Why We Don’t Use Story Points12.3 Cycle Time (Weeks per Feature)12.4 Cumulative Flow12.5 Process Cycle Efficiency13. Planning the Sprint and Release13.1 Backlog Grooming13.2 Selecting the Top Ten Features13.3 Why We Moved Backlog Grooming Out of the Sprint Planning Meeting13.4 Planning the Release14. How We Do Version Control14.1 No Junk on the Trunk14.2 Team Branches14.3 System Test Branch15. Why We Use Only Physical Kanban Boards16. What We Learned16.1 Know Your Goal16.2 Experiment16.3 Embrace Failure16.4 Solve Real Problems16.5 Have Dedicated Change Agents16.6 Involve PeoplePART II: A CLOSER LOOK AT THE TECHNIQUES 17. Agile and Lean in a Nutshell17.1 Agile in a Nutshell17.2 Lean in a Nutshell17.3 Scrum in a Nutshell17.4 XP in a Nutshell17.5 Kanban in a Nutshell18. Reducing the Test Automation Backlog18.1 What to Do About It18.2 How to Improve Test Coverage a Little Bit Each Iteration18.3 Step 1: List Your Test Cases18.4 Step 2: Classify Each Test18.5 Step 3: Sort the List in Priority Order18.6 Step 4: Automate a Few Tests Each Iteration18.7 Does This Solve the Problem?19. Sizing the Backlog with Planning Poker19.1 Estimating Without Planning Poker19.2 Estimating with Planning Poker19.3 Special Cards20. Cause-Effect Diagrams20.1 Solve Problems, Not Symptoms20.2 The Lean Problem-Solving Approach: A3 Thinking20.3 How to Use Cause-Effect Diagrams20.4 Example 1: Long Release Cycle20.5 Example 2: Defects Released to Production20.6 Example 3: Lack of Pair Programming20.7 Example 4: Lots of Problems20.8 Practical Issues: How to Create and Maintain the Diagrams20.9 Pitfalls20.10 Why Use Cause-Effect Diagrams?21. Final WordsA1. Glossary: How We Avoid Buzzword BingoIndex

    The widespread adoption of agile methods has brought the need for effective testing into the limelight, and agile projects have transformed the role of testers. Much of a tester's function, however, remains largely misunderstood. What is the true role of a tester? Do agile teams actually need members with QA backgrounds? What does it really mean to be an "agile tester?"Two of the industry's most experienced agile testing practitioners and consultants, Lisa Crispin and Janet Gregory, have teamed up to bring you the definitive answers to these questions and many others. In Agile Testing, Crispin and Gregory define agile testing and illustrate the tester's role with examples from real agile teams. They teach you how to use the agile testing quadrants to identify what testing is needed, who should do it, and what tools might help. The book chronicles an agile software development iteration from the viewpoint of a tester and explains the seven key success factors of agile testing.Readers will come away from this book understanding- How to get testers engaged in agile development- Where testers and QA managers fit on an agile team- What to look for when hiring an agile tester- How to transition from a traditional cycle to agile development- How to complete testing activities in short iterations- How to use tests to successfully guide development- How to overcome barriers to test automationThis book is a must for agile testers, agile teams, their managers, and their customers.

    It's not the star.It's not money. It's not a strategy.It's something else entirely.Several years ago, Sam Walker set out to answer one of the most hotly debated questions in sports: What are the greatest teams of all time? He devised a formula, then applied it to thousands of teams from leagues all over the world, from the NBA to the English Premier League to Olympic field hockey. When he was done, he had a list of the sixteen most dominant teams in history. At that point, he became obsessed with another, more complicated question: What did these freak teams have in common?As Walker dug into their stories, a pattern emerged: Each team had the same type of captain--a singular leader with an unconventional skill set who drove it to achieve sustained, historic greatness.Fueled by a lifetime of sports spectating, twenty years of reporting, and a decade of painstaking research, The Captain Class tells the surprising story of what makes teams exceptional. Drawing on original interviews with athletes from two dozen countries, as well as general managers, coaches, executives, and others skilled at building teams, Walker identifies the seven core qualities of this Captain Class--from extreme doggedness and emotional control to a knack for nonverbal communication to tactical aggression and the courage to stand apart.Told through riveting accounts of some of the most pressure-soaked moments in sports history--from Bill Russell's legendary "Coleman Play" in the 1957 NBA Finals to Barcelona's "Figo Game" against Real Madrid in 2000--The Captain Class doesn't just bring these events to life; it presents a fresh, counterintuitive take on leadership that can be applied to a wide spectrum of competitive disciplines.The men and women who make up the Captain Class were never the most skilled athletes, nor were they gifted orators or paragons of sportsmanship. They were often role players who were allergic to the spotlight. In short, the seven attributes they shared challenge your assumptions of what inspired leadership looks like.

    The value chain. Five forces. Industry structure. Differentiation. Relative cost. If you want to understand how companies achieve and sustain competitive success, Michael Porter’s frameworks are the foundation. But while everyone in business may know Porter’s name, many managers misunderstand and misuse his concepts.Understanding Michael Porter sets the record straight, providing the first concise, accessible summary of Porter’s revolutionary thinking. Written with Porter’s full cooperation by Joan Magretta, his former editor at Harvard Business Review, this new book delivers fresh, clear examples to illustrate and update Porter’s ideas.Magretta uses her wide business experience to translate Porter’s powerful insights into practice and to correct the most common misconceptions about them—for instance, that competition is about being unique, not being the best; that it is a contest over profits, not a battle between rivals; that strategy is about choosing to make some customers unhappy, not being all things to all customers.An added feature is an original Q&A with Porter himself, which includes answers to managers’ FAQs.Eminently readable, this book will enable every manager in your organization to grasp Porter’s ideas—and swiftly deploy them to drive your company’s success.

    Great ideas often come from a simple spark: A soccer player on the New Zealand national team notices all the unused wool his country produces and figures out a way to turn them into shoes (Allbirds). A former Buddhist monk decides the very best way to spread his mindfulness teachings is by launching an app (Headspace). A sandwich cart vendor finds a way to reuse leftover pita bread and turns it into a multimillion-dollar business (Stacy’s Pita Chips).   Award-winning journalist and NPR host Guy Raz has interviewed more than 200 highly successful entrepreneurs to uncover amazing true stories like these. In How I Built This, he shares tips for every entrepreneur’s journey: from the early days of formulating your idea, to raising money and recruiting employees, to fending off competitors, to finally paying yourself a real salary. This is a must-read for anyone who has ever dreamed of starting their own business or wondered how trailblazing entrepreneurs made their own dreams a reality.

    The author incudes OOD, UML, Design Patterns, Agile and XP methods with a detailed description of a complete software design for reusable programs in C++ and Java. Using a practical, problem-solving approach, it shows how to develop an object-oriented application -- from the early stages of analysis, through the low-level design and into the implementation. Walks readers through the designer's thoughts -- showing the errors, blind alleys, and creative insights that occur throughout the software design process. KEY TOPICS: Covers: Statics and Dynamics; Principles of Class Design; Complexity Management; Principles of Package Design; Analysis and Design; Patterns and Paradigm Crossings. Explains the principles of OOD, one by one, and then demonstrates them with numerous examples, completely worked-through designs, and case studies. Covers traps, pitfalls, and work arounds in the application of C++ and OOD and then shows how Agile methods can be used. Discusses the methods for designing and developing big software in detail. Features a three-chapter, in-depth, single case study of a building security system. MARKET: For Software Engineers, Programmers, and Analysts who want to understand how to design object oriented software with state of the art methods.

    500 CEOs.An instant classic, this revised and updated edition of the phenomenal bestseller dispels the myths about starting your own business. Small business consultant and author Michael E. Gerber, with sharp insight gained from years of experience, points out how common assumptions, expectations, and even technical expertise can get in the way of running a successful business.Gerber walks you through the steps in the life of a business—from entrepreneurial infancy through adolescent growing pains to the mature entrepreneurial perspective: the guiding light of all businesses that succeed—and shows how to apply the lessons of franchising to any business, whether or not it is a franchise. Most importantly, Gerber draws the vital, often overlooked distinction between working on your business and working in your business.The E-Myth Revisited will help you grow your business in a productive, assured way.

    Christensen). We've combed through hundreds of Harvard Business Review articles to select the most important ones to help you maximize yourself.HBR's 10 Must Reads on Managing Yourself will inspire you to:Stay engaged throughout your 50+-year work lifeTap into your deepest valuesSolicit candid feedbackReplenish physical and mental energyBalance work, home, community, and selfSpread positive energy throughout your organizationRebound from tough timesDecrease distractibility and frenzyDelegate and develop employees' initiativeThis collection of best-selling articles includes: bonus article “How Will You Measure Your Life?” by Clayton M. Christensen, "Managing Oneself," "Management Time: Who's Got the Monkey?" "How Resilience Works," "Manage Your Energy, Not Your Time," "Overloaded Circuits: Why Smart People Underperform," "Be a Better Leader, Have a Richer Life," "Reclaim Your Job," "Moments of Greatness: Entering the Fundamental State of Leadership," "What to Ask the Person in the Mirror," and "Primal Leadership: The Hidden Driver of Great Performance."

    In this guide, Chris Vander Mey provides a simplified, no-BS approach to the entire software lifecycle, distilled from lessons he learned as a manager at Amazon and Google.In the first part of the book, you’ll learn a step-by-step shipping process used by many of the best teams at Google and Amazon. Part II shows you the techniques, best practices, and skills you need to face an array of challenges in product, program, project, and engineering management.Clearly define your product and develop your mission and strategyAssemble your team and understand enough about systems to communicate with themCreate a beautiful, intuitive, and simple user experienceTrack your team’s deliverables and closely manage the testing processCommunicate clearly to gracefully handle requests, senior-management interactions, and feedback from various sourcesBuild metrics to track progress, spot problems, and celebrate successStick to your launch checklist and plan for marketing and PR

    Two leaders in the requirements community have teamed up to deliver a contemporary set of practices covering the full range of requirements development and management activities on software projects. Describes practical, effective, field-tested techniques for managing the requirements engineering process from end to end. Provides examples demonstrating how requirements "good practices" can lead to fewer change requests, higher customer satisfaction, and lower development costs. Fully updated with contemporary examples and many new practices and techniques. Describes how to apply effective requirements practices to agile projects and numerous other special project situations. Targeted to business analysts, developers, project managers, and other software project stakeholders who have a general understanding of the software development process. Shares the insights gleaned from the authors' extensive experience delivering hundreds of software-requirements training courses, presentations, and webinars.New chapters are included on specifying data requirements, writing high-quality functional requirements, and requirements reuse. Considerable depth has been added on business requirements, elicitation techniques, and nonfunctional requirements. In addition, new chapters recommend effective requirements practices for various special project situations, including enhancement and replacement, packaged solutions, outsourced, business process automation, analytics and reporting, and embedded and other real-time systems projects.

    One of the best ways is to understand users' reasons for doing things. Mental Models gives you the tools to help you grasp, and design for, those reasons. Adaptive Path co-founder Indi Young has written a roll-up-your-sleeves book for designers, managers, and anyone else interested in making design strategic, and successful.

    With step-by-step guidance, Validating Product Ideas shows you how to tackle the research to build the best possible product.

    You'll understand how to discover and interpret customer pain, and learn how to use this research to guide your team through each step of product creation.Written for designers, product managers, and others who want to communicate better with designers, this book is essential reading for anyone who contributes to the product creation process.Understand exactly who your customers are, what they want, and how to build products that make them happyLearn frameworks and principles that successful product designers useIncorporate five states into every screen of your interface to improve conversions and reduce perceived loading timesDiscover meeting techniques that Apple, Amazon, and LinkedIn use to help teams solve the right problems and make decisions fasterDesign effective interfaces across different form factors by understanding how people hold devices and complete tasksLearn how successful designers create working prototypes that capture essential customer feedbackCreate habit-forming and emotionally engaging experiences, using the latest psychological research