This groundbreaking new book sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers, and operations, delivery teams can get changes released in a matter of hours-- sometimes even minutes-no matter what the size of a project or the complexity of its code base. Jez Humble and David Farley begin by presenting the foundations of a rapid, reliable, low-risk delivery process. Next, they introduce the "deployment pipeline," an automated process for managing all changes, from check-in to release. Finally, they discuss the "ecosystem" needed to support continuous delivery, from infrastructure, data and configuration management to governance. The authors introduce state-of-the-art techniques, including automated infrastructure management and data migration, and the use of virtualization. For each, they review key issues, identify best practices, and demonstrate how to mitigate risks. Coverage includes - Automating all facets of building, integrating, testing, and deploying software - Implementing deployment pipelines at team and organizational levels - Improving collaboration between developers, testers, and operations - Developing features incrementally on large and distributed teams - Implementing an effective configuration management strategy - Automating acceptance testing, from analysis to implementation - Testing capacity and other non-functional requirements - Implementing continuous deployment and zero-downtime releases - Managing infrastructure, data, components and dependencies - Navigating risk management, compliance, and auditing Whether you're a developer, systems administrator, tester, or manager, this book will help your organization move from idea to release faster than ever--so you can deliver value to your business rapidly and reliably.

    Based on SAP ERP 6.0, this new edition of the best-selling book is a comprehensive reference to the ins and outs of Materials Management in SAP, with new real-world, practical examples to help you grasp the information quickly and efficiently. You’ll learn everything you need to know, from goods receipt and invoice verification to balance sheet valuation and the material ledger. Materials Management Processes and Concepts Discover the various concepts of materials management and how they can be used to help your business run smoothly. Materials Management Configuration Learn specific configuration details to help you optimize your MM implementation. Comprehensive Coverage of Key Concepts Master the various elements of SAP ERP, including material master data, vendor master data, purchase requisitions, request for quotations, inventory management, and much more. Real-World Scenarios and Examples Use the expert advice and examples throughout to help you with your own MM processes. Third Edition, Updated and Expanded This book is updated to include new content on the release strategy for purchasing, special procurement keys, split valuation, pricing conditions in purchasing, taxes in MM, as well as screenshots for the latest GUI and new appendices.Highlights• Material Master Data • Vendor Master Data • Purchasing Information Data • Release Strategy for Purchasing • Split Valuation • Material Master Records • Purchase Requisitions • Requests for Quotations • External Services Management • Inventory Management • Goods Issue • Taxes in MM

    He describes a broad range of agile product management practices, including making agile product discovery work, taking advantage of emergent requirements, creating the minimal marketable product, leveraging early customer feedback, and working closely with the development team. Benefitting from Pichler's extensive experience, you'll learn how Scrum product ownership differs from traditional product management and how to avoid and overcome the common challenges that Scrum product owners face. Coverage includesUnderstanding the product owner's role: what product owners do, how they do it, and the surprising implicationsEnvisioning the product: creating a compelling product vision to galvanize and guide the team and stakeholdersGrooming the product backlog: managing the product backlog effectively even for the most complex productsPlanning the release: bringing clarity to scheduling, budgeting, and functionality decisionsCollaborating in sprint meetings: understanding the product owner's role in sprint meetings, including the dos and don'tsTransitioning into product ownership: succeeding as a product owner and establishing the role in the enterprise This book is an indispensable resource for anyone who works as a product owner, or expects to do so, as well as executives and coaches interested in establishing agile product management.

    The vision behind Clojure is of a radically simple language framework holding together a sophisticated collection of programming features. Learning Clojure involves much more than just learning the mechanics of the language. To really get Clojure you need to understand the ideas underlying this structure of framework and features. You need this book: an accessible introduction to Clojure that focuses on the ideas behind the language as well as the practical details of writing code.

    is one of the most successful—and influential—companies of our time, the transformational innovator that made computers not just personal but beautiful everyday objects. Technology met design, and our culture was altered forever.And yet very little is known about life inside Apple. The company is pathologically secretive—even with its own designers—about how it comes up with its groundbreaking products: iMac, iPod, iPhone, iPad, and the next “insanely great” thing on the horizon. Here, for the first time, the men and women who worked for and alongside Steve Jobs share their remarkable, nearly forty-year-old story. How Apple survived nearly catastrophic failure early on. How Jobs and his team came to understand and execute design like no one else. And how their philosophy ultimately changed the world.This Fast Company/Byliner Original is unlike any other book about Apple. Author Max Chafkin led a team of “Fast Company” reporters that spent months interviewing more than fifty former Apple execs and insiders, many of whom had never spoken publicly about their work. The result is a compelling and deeply revealing oral history of how design evolved at the most creative enterprise of our time, the company that one entrepreneur says “taught the world taste.”In these interviews, former colleagues describe Jobs at his most brilliant and bombastic—hurling unsatisfactory products across the lab and insulting employees, yet also singling out and celebrating craftsmanship and original work. Without a doubt, Jobs is the single most important figure in the company’s history. But overlooked in Apple’s carefully cultivated mythology are the other ingenious men and women who’ve left an indelible mark on Apple, some of whom think they deserve much more of the credit. At Apple, the stakes were big, and so were the egos.“Design Crazy” takes us behind the mystique and reveals Apple to be a deeply misunderstood company. And the greatest business story of the past two decades is far from over. Two years after the death of Steve Jobs, with many of his former colleagues now at startups like Tesla, Evernote, and Nest Labs, some think the end of Apple’s dominance is only a matter of time. The company has risen to the challenge before, but still the question lingers: Can Apple be Apple without Jobs?ABOUT THE AUTHORMax Chafkin is a contributing writer with “Fast Company.” His work has also been published in “Inc.”, “Vanity Fair,” “The New York Times Magazine,” and “The Best Business Writing 2012.” He lives in Brooklyn.

    "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."

    This book isn't about that - it's about everything else. As such, there's very little code inside, meaning everyone from PHP hackers to hardcore embedded C programmers will get a lot out of it.This book covers 10 topics crucial to being an amazing developer:Focus on Delivering ResultsFix Bugs Efficiently and CleanlyAdd Features with EaseDeal With Technical Debt and SlopPlay Well With OthersMake Technical DecisionsBootstrap a Greenfield SystemLearn to WriteInterview Potential Co-WorkersLead a Team

    In the late 1990s, it provided an optimistic model for public

    Dormann—founder, chairman, and editor-in-chief of LEADERS magazine, whose circulation is limited to such leading figures. Here, he brings together the first-ever exclusive collection of wisdom and inspiration addressed to young people from the world’s most influential people—advice on leadership, goal achievement, public service, and life journeys. Letters from Leaders is a beautifully designed book comprising nearly eighty letters from those who have done so much to shape our world today—from Muhammad Ali to four U.S. Presidents, Mikhail Gorbachev, King Bhumibol Adulyadej of Thailand and King Abdullah II of Jordan, and the Dalai Lama; from Cathie Black to T. Boone Pickens, Muriel Siebert, and Donald Trump. The letters, some as facsimile reproductions of handwritten originals, are each introduced with a biographical note by Dormann. As put so aptly by Dormann in his introduction, “All kings and queens, presidents, Nobel Laureates, chairmen and chairwomen, CEOs, and world leaders have one thing in common: They want what they have achieved to be useful and to be handed over to a younger generation. . . . The leaders in these pages have ‘lived’ and now offer their experiences as a treasure to ambitious and open minds—those who want to be something in life.”

    Martin ("Uncle Bob") reintroduces agile values and principles for a new generation of software developers. In this eagerly-awaited book, the best-selling author of The Clean Coder shows how to bring unprecedented levels of professionalism and discipline to agile development -- and thereby write far more effective, successful software. As with his other books, Martin's Clean Agile: Back to Basics 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. Writing in the agile context, Martin offers direct, no-nonsense answers to crucial questions like:How and why did Agile begin? What are the costs and benefits of Agile? What are the most effective practices of Agile Development? How should an Agile team be organized? What roles do programmers, testers, and managers play in an Agile team? What is the role of the Agile Coach? What about Agile for large projects? What kinds of projects benefit from Agile? Clean Agile: Back to Basics is essential reading for programmers, managers, testers, project managers and every software professional called upon to lead or participate in an agile project.

    Drawing on Lopp's management experiences at Apple, Netscape, Symantec, and Borland, this book is full of stories based on companies in the Silicon Valley where people have been known to yell at each other. It is a place full of dysfunctional bright people who are in an incredible hurry to find the next big thing so they can strike it rich and then do it all over again. Among these people are managers, a strange breed of people who through a mystical organizational ritual have been given power over your future and your bank account.Whether you're an aspiring manager, a current manager, or just wondering what the heck a manager does all day, there is a story in this book that will speak to you.

    They go far beyond generic implementation guidelines, demonstrating exactly how to make lean work in real projects, environments, and companies.The Poppendiecks organize this book around the crucial concept of frames, the unspoken mental constructs that shape our perspectives and control our behavior in ways we rarely notice. For software leaders and team members, some frames lead to long-term failure, while others offer a strong foundation for success. Drawing on decades of experience, the authors present twenty-four frames that offer a coherent, complete framework for leading lean software development. You'll discover powerful new ways to act as competency leader, product champion, improvement mentor, front-line leader, and even visionary.Systems thinking: focusing on customers, bringing predictability to demand, and revamping policies that cause inefficiency Technical excellence: implementing low-dependency architectures, TDD, and evolutionary development processes, and promoting deeper developer expertise Reliable delivery: managing your biggest risks more effectively, and optimizing both workflow and schedules Relentless improvement: seeing problems, solving problems, sharing the knowledge Great people: finding and growing professionals with purpose, passion, persistence, and pride Aligned leaders: getting your entire leadership team on the same page From the world's number one experts in Lean software development, Leading Lean Software Development will be indispensable to everyone who wants to transform the promise of lean into reality--in enterprise IT and software companies alike.

    He presents convincing arguments that when leaders emulate these qualities, they will inspire and empower the people they have been called to lead. Reflection and discussion questions and assessment questions make this ideal for group use. Conversational in tone and seasoned with real-life stories from his own successes and failures as a leader, Robinson helps Christian leaders wrestle with four questions that emerge from John’s introduction of Jesus, “and the word became flesh and dwelt among us….” • Jesus dwelt with those he led, how can I be closer to those I lead? • Jesus disciples beheld him, how can I be more transparent with those I lead? • The glory of Jesus was a reflection of his father, am I seeking my own glory? • Jesus led with grace and truth, how can I lead with grace and truth? The Incarnate Leader is indispensable reading for anyone in a position of leadership – whether in a church setting, corporation, school board, or home. The book is packaged as a short one-evening read, similar to other popular business books.

    The tools and recipes in this book will help you uncover and solve hidden (and not-so-hidden) problems with your technology, your methodology, and those difficult "people" issues on your team.Project retrospectives help teams examine what went right and what went wrong on a project. But traditionally, retrospectives (also known as "post-mortems") are only helpful at the end of the project--too late to help. You need agile retrospectives that are iterative and incremental. You need to accurately find and fix problems to help the team today.Now, Derby and Larsen show you the tools, tricks, and tips you need to fix the problems you face on a software development project on an on-going basis. You'll see how to architect retrospectives in general, how to design them specifically for your team and organization, how to run them effectively, how to make the needed changes, and how to scale these techniques up. You'll learn how to deal with problems, and implement solutions effectively throughout the project--not just at the end.With regular tune-ups, your team will hum like a precise, world-class orchestra.ContentsForwardPrefaceIntroduction1. Helping your team inspect and adapt2. A retrospective custom-fit for your team3. Leading retrospectives4. Activities to set the stage5. Activities to gather data6. Activities to gather insights7. Activities to decide what to do8. Activities to close the retrospective9. Releases and project retrospectives10. Make it soA1. Facilitation suppliesA2. Debriefing activitiesA3. Activities quick reference matrixA4. Resources for learning facilitation skillsA5. Bibliography

    Cooper details many of these meta functions to explain his central thesis: programmers need to seriously re-evaluate the many user-hostile concepts deeply embedded within the software development process. Rather than provide users with a straightforward set of options, programmers often pile on the bells and whistles and ignore or de-prioritise lingering bugs. For the average user, increased functionality is a great burden, adding to the recurrent chorus that plays: "computers are hard, mysterious, unwieldy things." (An average user, Cooper asserts, who doesn't think that way or who has memorised all the esoteric commands and now lords it over others, has simply been desensitised by too many years of badly designed software.) Cooper's writing style is often overblown, with a pantheon of cutesy terminology (i.e. "dancing bearware") and insider back-patting. (When presenting software to Bill Gates, he reports that Gates replied: "How did you do that?" to which he writes: "I love stumping Bill!") More seriously, he is also unable to see beyond software development's importance--a sin he accuses programmers of throughout the book. Even with that in mind, the central questions Cooper asks are too important to ignore: Are we making users happier? Are we improving the process by which they get work done? Are we making their work hours more effective? Cooper looks to programmers, business managers and what he calls "interaction designers" to question current assumptions and mindsets. Plainly, he asserts that the goal of computer usage should be "not to make anyone feel stupid." Our distance from that goal reinforces the need to rethink entrenched priorities in software planning. -- Jennifer Buckendorff, Amazon.com