Traditional software development methods struggle to keep pace with the accelerated pace and rapid change of Internet-era development. Several "agile methodologies" have been developed in response -- and these approaches to software development are showing exceptional promise. In this book, Jim Highsmith covers them all -- showing what they have in common, where they differ, and how to choose and customize the best agile approach for your needs.KEY TOPICS:Highsmith begins by introducing the values and principles shared by virtually all agile software development methods. He presents detailed case studies from organizations that have used them, as well as interviews with each method's principal authors or leading practitioners. Next, he takes a closer look at the key features and techniques associated with each major Agile approach: Extreme Programming (XP), Crystal Methods, Scrum, Dynamic Systems Development Method (DSDM), Lean Development, Adaptive Software Development (ASD), and Feature-Driven Development (FDD). In Part III, Highsmith offers practical advice on customizing the optimal agile discipline for your own organization.MARKET:For all software developers, project managers, and other IT professionals seeking more flexible, effective approaches to developing software.
Scrum, das am weitesten verbreitete Vorgehen der Agilen Softwareentwicklung, ist in den IT-Projekten längst angekommen. Weil Scrum zu verwendende Methoden und ihre Anwendungen bewusst nicht festlegt, brauchen Entwicklerteams hier oft Unterstützung. Sehr häufig wird in Scrum-Projekten die Methode angewendet, Anforderungen an das zu entwickelnde Produkt in Form von „User Stories“ (Benutzergeschichten) zu erfassen, damit die Arbeit zu planen und zu priorisieren. User Stories werden in Alltagssprache formuliert und bewusst kurz gehalten (in der Regel nicht länger als zwei Sätze). Dieses Buch zeigt, wie Scrum mit Hilfe von User Stories hinsichtlich eines kundenorientierten Anforderungsmanagements optimiert werden kann und gibt den Entwicklern konkrete Empfehlungen, wie sie User Stories erfolgreich einsetzen können. Die 3. Auflage erweitert das Themenspektrum um das Thema User Story Mapping und Verticals - [email protected] Das Otto-Kapitel beschreibt, wie Scrum im Großen und mit unabhängig agierenden Teams funktionieren kann.
Best practices for managing projects in agile environments—now updated with new techniques for larger projects Today, the pace of project management moves faster. Project management needs to become more flexible and far more responsive to customers. Using Agile Project Management (APM), project managers can achieve all these goals without compromising value, quality, or business discipline. In Agile Project Management, Second Edition, renowned agile pioneer Jim Highsmith thoroughly updates his classic guide to APM, extending and refining it to support even the largest projects and organizations. Writing for project leaders, managers, and executives at all levels, Highsmith integrates the best project management, product management, and software development practices into an overall framework designed to support unprecedented speed and mobility. The many topics added in this new edition include incorporating agile values, scaling agile projects, release planning, portfolio governance, and enhancing organizational agility. Project and business leaders will especially appreciate Highsmith’s new coverage of promoting agility through performance measurements based on value, quality, and constraints. This edition’s coverage includes: Understanding the agile revolution’s impact on product development Recognizing when agile methods will work in project management, and when they won’t Setting realistic business objectives for Agile Project Management Promoting agile values and principles across the organization Utilizing a proven Agile Enterprise Framework that encompasses governance, project and iteration management, and technical practices Optimizing all five stages of the agile project: Envision, Speculate, Explore, Adapt, and Close Organizational and product-related processes for scaling agile to the largest projects and teams Agile project governance solutions for executives and management The “Agile Triangle”: measuring performance in ways that encourage agility instead of discouraging it The changing role of the agile project leader
The XP conference series established in 2000 was the first conference dedicated to agile processes in software engineering. The idea of the conference is to offer a unique setting for advancing the state of the art in the research and practice of agile processes. This year’s conference was the ninth consecutive edition of this international event. The conference has grown to be the largest conference on agile software development outside North America. The XP conference enjoys being one of those conferences that truly brings practitioners and academics together. About 70% of XP participants come from industry and the number of academics has grown steadily over the years. XP is more of an experience rather than a regular conference. It offers several different ways to interact and strives to create a truly collaborative environment where new ideas and exciting findings can be presented and shared. For example, this year’s open space session, which was “a conference within a conference”, was larger than ever before. Agile software development is a unique phenomenon from several perspectives.
Agile is a relatively recent methodology used in the development process of a project. Therefore, it is important to share new emerging knowledge with researchers and professionals interested in adopting an agile mindset. Emerging Innovations in Agile Software Development focuses on the use of agile methodologies to manage, design, develop, test and maintain software projects. Emphasizing research-based solutions for contemporary software development, this publication is designed for use by software developers, researchers, and graduate-level students in software engineering and project management programs.
This is the digital version of the printed book (Copyright © 2000). Winner of the 2001 Software Development Jolt Product Excellence Award This innovative text offers a practical, realistic approach to managing high-speed, high-change software development projects. Consultant James A. Highsmith shows readers how to increase collaboration and adapt to uncertainty. Many organizations start high-speed, high-change projects without knowing how to do them–and even worse, without knowing they don’t know. Successful completion of these projects is often at the expense of the project team. Adaptive Software Development emphasizes an adaptive, collaborative approach to software development. The concepts allow developers to “scale-up” rapid application development and extreme programming approaches for use on larger, more complex projects. The four goals of the book are to support an adaptive culture or mindset, in which change and uncertainty are assumed to be the natural state–not a false expectation of order introduce frameworks to guide the iterative process of managing change institute collaboration, the interaction of people on three levels: interpersonal, cultural, and structural add rigor and discipline to the RAD approach, making it scalable to the uncertainty and complexity of real-life undertakings
Heute werden viele Softwareprojekte unter Zuhilfenahme von Outsourcing, Offshoring oder einer sonstigen Form von Verteilung durchgeführt. Dies ist stets mit einer Distanz zwischen den Projektmitarbeitern verbunden, die sich auf Raum, Zeit, Kultur, Sprache oder Politik beziehen kann. Ein weiterer Trend wird immer deutlicher: der Aufschwung der agilen Softwareentwicklung. Dieses Buch zeigt, wie auch bei verteilten Projekten erfolgreich agil gearbeitet werden kann. Es richtet sich an Entwickler und Manager, die auch in einer verteilten Umgebung die Vorteile agiler Entwicklung nutzen möchten.
Challenges in unpredictable markets, changing customer requirements, and advancing information technologies have lead to progression towards service oriented engineering and agile and lean software development. These prevailing approaches to software systems provide solutions to challenges in demanding business environments. Agile and Lean Service-Oriented Development: Foundations, Theory and Practice explores the groundwork of service-oriented and agile and lean development and the conceptual basis and experimental evidences for the combination of the two approaches. Highlighting the best tools and guidelines for these developments in practice, this book is essential for researchers and practitioners in the software development and service computing fields.
This is the digital version of the printed book (Copyright © 2010). All software projects face the challenges of diverse distances -- temporal, geographical, cultural, lingual, political, historical, and more. Many forms of distance even affect developers in the same room. The goal of this book is to reconcile two mainstays of modern agility: the close collaboration agility relies on, and project teams distributed across different cities, countries, and continents. In Agile Software Development with Distributed Teams, Jutta Eckstein asserts that, in fact, agile methods and the constant communication they require are uniquely capable of solving the challenges of distributed projects. Agility is responsiveness to change -- in other words, agile practitioners maintain flexibility to accommodate changing circumstances and results. Iterative development serves the learning curve that global project teams must scale. This book is not about how to outsource and forget your problems. Rather, Eckstein details how to carefully select development partners and integrate efforts and processes to form a better product than any single contributor could deliver on his or her own. The author de-emphasizes templates and charts and favors topical discussion and exploration. Practitioners share experiences in their own words in short stories throughout the book. Eckstein trains readers to be change agents, to creatively apply the concepts in this book to form a customized distributed project plan for success. Topics include: Understanding Distributed Development The Productivity Myth Ensuring Conceptual Integrity Trust and Mutual Respect Iterations and Releases Using Features to Steer the Development Effort Team Velocity Virtual Retrospectives Dispersed Synchronization Introducing Agility to Global Projects and much more
Inhaltsangabe:Einleitung: Vorgehensmodelle zur Softwareentwicklung zielen darauf ab, dass mit ihrer Hilfe Softwareprodukte mit den gewünschten Funktionalitäten zu den geplanten Kosten und innerhalb der erwarteten Zeit erstellt werden. Projekte scheitern insbesondere wegen unklarer Projektziele und unklarer Formulierung der Anforderungen sowie unmethodischem Vorgehen. Die Risiken eines Projektscheiterns werden durch den Einsatz eines Vorgehensmodells reduziert. Im Laufe der Zeit haben sich verschiedene Modelle etabliert, wobei seit 2000 vermehrt so genannte agile Modelle angewendet werden. Frühere Modelle basieren auf einem Vorgehen, bei welchem das Hauptaugenmerk auf umfassender Planung liegt und die Softwareentwicklung als ein an die Produktion angelehnter Fertigungsprozess betrachtet wird. Agile Modelle vertreten die Auffassung, dass ein adaptives Vorgehen zielführender ist. In agilen Modellen wird dementsprechend eine schrittweise Umsetzung in kurzen Zyklen bevorzugt, wodurch ein schnelles Reagieren auf sich ändernde Anforderungen möglich wird. Das Ergebnis im Sinne von lauffähiger Software wird als oberstes Ziel definiert. Die Planungsphase wird als weniger wichtig angesehen und es erfolgt hingegen eine besondere Berücksichtigung der menschlichen Komponente. Softwareentwicklung wird in Anlehnung an die Produktentwicklung als innovativer und kreativer Prozess gesehen, was sich auch auf den Aufbau der Modelle und der verwendeten Steuerungsmechanismen auswirkt. Diese Arbeit beschreibt die relevanten Vorgehensmodelle, welche im Anschluss verglichen werden, um die Unterschiede zwischen den Modellen festzustellen. Nachfolgend werden die Anforderungen an ein Vorgehensmodell für die Softwareentwicklung bei der Hypo Tirol Bank erhoben. Aufgrund dieser Erhebung wird ein bestimmtes Modell ausgewählt und ein Weg aufgezeigt, wie die Einführung des Modells erfolgt. Bei der Einführung des Modells gilt es darauf zu achten, dass die Rahmenbedingungen und die Ausgangssituation berücksichtigt werden. Es wird ein Leitfaden dargestellt, der das Vorgehen für eine erfolgreiche Modell-Einführung für die Softwareentwicklung beschreibt. Damit wird die Basis geschaffen, um durch das Anwenden des richtigen Vorgehensmodells den Erfolg von Softwareentwicklungsprojekten zu [...]
- Helps managers combat the manufacturing mindset that dominates business thinking, and shows why this mindset is harmful to software development - Introduces predictability to the historically unpredictable world of software development - Allows organizations to improve job satisfaction by fostering an environment of creativity among developers
Widely considered one of the best practical guides to programming, Steve McConnell’s original CODE COMPLETE has been helping developers write better software for more than a decade. Now this classic book has been fully updated and revised with leading-edge practices—and hundreds of new code samples—illustrating the art and science of software construction. Capturing the body of knowledge available from research, academia, and everyday commercial practice, McConnell synthesizes the most effective techniques and must-know principles into clear, pragmatic guidance. No matter what your experience level, development environment, or project size, this book will inform and stimulate your thinking—and help you build the highest quality code. Discover the timeless techniques and strategies that help you: Design for minimum complexity and maximum creativity Reap the benefits of collaborative development Apply defensive programming techniques to reduce and flush out errors Exploit opportunities to refactor—or evolve—code, and do it safely Use construction practices that are right-weight for your project Debug problems quickly and effectively Resolve critical construction issues early and correctly Build quality into the beginning, middle, and end of your project
In OBJECT THINKING, esteemed object technologist David West contends that the mindset makes the programmer—not the tools and techniques. Delving into the history, philosophy, and even politics of object-oriented programming, West reveals how the best programmers rely on analysis and conceptualization—on thinking—rather than formal process and methods. Both provocative and pragmatic, this book gives form to what’s primarily been an oral tradition among the field’s revolutionary thinkers—and it illustrates specific object-behavior practices that you can adopt for true object design and superior results. Gain an in-depth understanding of: Prerequisites and principles of object thinking. Object knowledge implicit in eXtreme Programming (XP) and Agile software development. Object conceptualization and modeling. Metaphors, vocabulary, and design for object development. Learn viable techniques for: Decomposing complex domains in terms of objects. Identifying object relationships, interactions, and constraints. Relating object behavior to internal structure and implementation design. Incorporating object thinking into XP and Agile practice.
A top-level security guru for both eBay and PayPal and a best-selling information systems security author show how to design and develop secure Web commerce systems. Whether it's online banking or ordering merchandise using your cell phone, the world of online commerce requires a high degree of security to protect you during transactions. This book not only explores all critical security issues associated with both e-commerce and mobile commerce (m-commerce), it is also a technical manual for how to create a secure system. Covering all the technical bases, this book provides the detail that developers, system architects, and system integrators need to design and implement secure, user-friendly, online commerce systems. Co-authored by Hadi Nahari, one of the world’s most renowned experts in Web commerce security; he is currently the Principal Security, Mobile and DevicesArchitect at eBay, focusing on the architecture and implementation of eBay and PayPal mobile Co-authored by Dr. Ronald Krutz; information system security lecturer and co-author of the best-selling Wiley CISSP Prep Guide Series Shows how to architect and implement user-friendly security for e-commerce and especially, mobile commerce Covers the fundamentals of designing infrastructures with high availability, large transactional capacity, and scalability Includes topics such as understanding payment technologies and how to identify weak security, and how to augment it. Get the essential information you need on Web commerce security—as well as actual design techniques—in this expert guide.
-- Contains the best papers from the world's two leading Extreme Programming conferences: XP 2001 and XP Universe. -- Helps organizations fully understand, transition to, and overcome the common challenges of Extreme Programming. For some, Extreme Programming represents a new set of rules, for others it is a humanistic set of values, and to still others it is a very dangerous over simplification of software development. Anyway you slice it, Extreme Programming is thought-provoking and controversial. Extreme Programming Perspectives collects the best papers from the world's two leading XP conferences, and presents this information in a handy, easily-digestible format that allows reader to determine whether XP is a prudent undertaking for their organization, and how their organization can optimize their XP initiatives. The book contains contributions from the most renowned names in the XP field, including Kent Beck, Martin Fowler, Ward Cunningham, and Ron Jeffries. Despite the growing acceptance of XP, readers need information to understand and optimize this agile method. They need to place XP in perspective. This book provides what they need.
Alastair Cockburn offers advice on bringing difficult software development projects to a successful conclusion with a minimum of stress. The volume is based on over 10 years of interviewing software project teams.

Best Books