From best-selling author and noted teacher and speaker Yehuda Berg comes a thought-provoking call to action on our current global crisis. Positing that our collective abdication of responsibility — in every facet of our lives, including business and the economy, the environment, government and politics, healthcare, education, and religion — has contributed to the problems and challenges we face, Berg asserts that taking responsibility for our actions (or lack thereof) and their consequences is the key to achieving change for the better. Berg urges readers to access the power within each of us, using the principles of Kabbalah, in order to create the consciousness shift required for lasting positive change.

This guide will help readers learn how to employ the significant power of use cases to their software development efforts. It provides a practical methodology, presenting key use case concepts.

Thoroughly reviewed and eagerly anticipated by the agile community, User Stories Applied offers a requirements process that saves time, eliminates rework, and leads directly to better software. The best way to build software that meets users' needs is to begin with "user stories": simple, clear, brief descriptions of functionality that will be valuable to real users. In User Stories Applied, Mike Cohn provides you with a front-to-back blueprint for writing these user stories and weaving them into your development lifecycle. You'll learn what makes a great user story, and what makes a bad one. You'll discover practical ways to gather user stories, even when you can't speak with your users. Then, once you've compiled your user stories, Cohn shows how to organize them, prioritize them, and use them for planning, management, and testing. User role modeling: understanding what users have in common, and where they differ Gathering stories: user interviewing, questionnaires, observation, and workshops Working with managers, trainers, salespeople and other "proxies" Writing user stories for acceptance testing Using stories to prioritize, set schedules, and estimate release costs Includes end-of-chapter practice questions and exercises User Stories Applied will be invaluable to every software developer, tester, analyst, and manager working with any agile method: XP, Scrum... or even your own home-grown approach.

Proven, 100% Practical Guidance for Making Scrum and Agile Work in Any Organization This is the definitive, realistic, actionable guide to starting fast with Scrum and agile-and then succeeding over the long haul. Leading agile consultant and practitioner Mike Cohn presents detailed recommendations, powerful tips, and real-world case studies drawn from his unparalleled experience helping hundreds of software organizations make Scrum and agile work. Succeeding with Agile is for pragmatic software professionals who want real answers to the most difficult challenges they face in implementing Scrum. Cohn covers every facet of the transition: getting started, helping individuals transition to new roles, structuring teams, scaling up, working with a distributed team, and finally, implementing effective metrics and continuous improvement. Throughout, Cohn presents "Things to Try Now" sections based on his most successful advice. Complementary "Objection" sections reproduce typical conversations with those resisting change and offer practical guidance for addressing their concerns. Coverage includes Practical ways to get started immediately-and "get good" fast Overcoming individual resistance to the changes Scrum requires Staffing Scrum projects and building effective teams Establishing "improvement communities" of people who are passionate about driving change Choosing which agile technical practices to use or experiment with Leading self-organizing teams Making the most of Scrum sprints, planning, and quality techniques Scaling Scrum to distributed, multiteam projects Using Scrum on projects with complex sequential processes or challenging compliance and governance requirements Understanding Scrum's impact on HR, facilities, and project management Whether you've completed a few sprints or multiple agile projects and whatever your role-manager, developer, coach, ScrumMaster, product owner, analyst, team lead, or project lead-this book will help you succeed with your very next project. Then, it will help you go much further: It will help you transform your entire development organization.

Summary Specification by Example is an emerging practice for creating software based on realistic examples, bridging the communication gap between business stakeholders and the dev teams building the software. In this book, author Gojko Adzic distills interviews with successful teams worldwide, sharing how they specify, develop, and deliver software, without defects, in short iterative delivery cycles. About the Technology Specification by Example is a collaborative method for specifying requirements and tests. Seven patterns, fully explored in this book, are key to making the method effective. The method has four main benefits: it produces living, reliable documentation; it defines expectations clearly and makes validation efficient; it reduces rework; and, above all, it assures delivery teams and business stakeholders that the software that's built is right for its purpose. About the Book This book distills from the experience of leading teams worldwide effective ways to specify, test, and deliver software in short, iterative delivery cycles. Case studies in this book range from small web startups to large financial institutions, working in many processes including XP, Scrum, and Kanban. This book is written for developers, testers, analysts, and business people working together to build great software. Purchase of the print book comes with an offer of a free PDF, ePub, and Kindle eBook from Manning. Also available is all code from the book. What's Inside Common process patterns How to avoid bad practices Fitting SBE in your process 50+ case studies =============================================== Table of Contents Part 1 Getting started Part 2 Key process patterns Part 3 Case studies Key benefits Key process patterns Living documentation Initiating the changes Deriving scope from goals Specifying collaboratively Illustrating using examples Refining the specification Automating validation without changing specifications Validating frequently Evolving a documentation system uSwitch RainStor Iowa Student Loan Sabre Airline Solutions ePlan Services Songkick Concluding thoughts

Filled with advice distilled from the authors' experience in the creation and use of object-oriented technology, Succeeding with Objects is an invaluable guide to the decision processes inherent in successful software development using object-oriented technology. The focus of the book is on you - the developer, project manager, or IS executive.

Much of the innovative programming that powers the Internet, creates operating systems, and produces software is the result of "open source" code, that is, code that is freely distributed--as opposed to being kept secret--by those who write it. Leaving source code open has generated some of the most sophisticated developments in computer technology, including, most notably, Linux and Apache, which pose a significant challenge to Microsoft in the marketplace. As Steven Weber discusses, open source's success in a highly competitive industry has subverted many assumptions about how businesses are run, and how intellectual products are created and protected. Traditionally, intellectual property law has allowed companies to control knowledge and has guarded the rights of the innovator, at the expense of industry-wide cooperation. In turn, engineers of new software code are richly rewarded; but, as Weber shows, in spite of the conventional wisdom that innovation is driven by the promise of individual and corporate wealth, ensuring the free distribution of code among computer programmers can empower a more effective process for building intellectual products. In the case of Open Source, independent programmers--sometimes hundreds or thousands of them--make unpaid contributions to software that develops organically, through trial and error. Weber argues that the success of open source is not a freakish exception to economic principles. The open source community is guided by standards, rules, decisionmaking procedures, and sanctioning mechanisms. Weber explains the political and economic dynamics of this mysterious but important market development. Table of Contents: Preface 1. Property and the Problem of Software 2. The Early History of Open Source 3. What Is Open Source and How Does It Work? 4. A Maturing Model of Production 5. Explaining Open Source: Microfoundations 6. Explaining Open Source: Macro-Organization 7. Business Models and the Law 8. The Code That Changed the World? Notes Index Reviews of this book: In the world of open-source software, true believers can be a fervent bunch. Linux, for example, may act as a credo as well as an operating system. But there is much substance beyond zealotry, says Steven Weber, the author of The Success of Open Source...An open-source operating system offers its source code up to be played with, extended, debugged, and otherwise tweaked in an orgy of user collaboration. The author traces the roots of that ethos and process in the early years of computers...He also analyzes the interface between open source and the worlds of business and law, as well as wider issues in the clash between hierarchical structures and networks, a subject with relevance beyond the software industry to the war on terrorism. --Nina C. Ayoub, Chronicle of Higher Education Reviews of this book: A valuable new account of the [open-source software] movement. --Edward Rothstein, New York Times We can blindly continue to develop, reward, protect, and organize around knowledge assets on the comfortable assumption that their traditional property rights remain inviolate. Or we can listen to Steven Weber and begin to make our peace with the uncomfortable fact that the very foundations of our familiar "knowledge as property" world have irrevocably shifted. --Alan Kantrow, Chief Knowledge Officer, Monitor Group Ever since the invention of agriculture, human beings have had only three social-engineering tools for organizing any large-scale division of labor: markets (and the carrots of material benefits they offer), hierarchies (and the sticks of punishment they impose), and charisma (and the promises of rapture they offer). Now there is the possibility of a fourth mode of effective social organization--one that we perhaps see in embryo in the creation and maintenance of open-source software. My Berkeley colleague Steven Weber's book is a brilliant exploration of this fascinating topic. --J. Bradford DeLong, Department of Economics, University of California at Berkeley Steven Weber has produced a significant, insightful book that is both smart and important. The most impressive achievement of this volume is that Weber has spent the time to learn and think about the technological, sociological, business, and legal perspectives related to open source. The Success of Open Source is timely and more thought provoking than almost anything I've come across in the past several years. It deserves careful reading by a wide audience. --Jonathan Aronson, Annenberg School for Communication, University of Southern California