Barry Boehm

Jo Ann Lane

Supannika Koolmanojwong

Richard N. Turner

“The title makes a huge promise: a way to divide commitment into increments that are both meetable (good news for developers) and meaningful (good news for managers and stakeholders). And the book makes good on that promise.” –Tom DeMarco, Principal, The Atlantic Systems Guild, author of Peopleware, Deadline, and Slack “I am seriously impressed with this ICSM book. Besides being conceptually sound, I was amazed by the sheer number of clear and concise characterizations of issues, relationships, and solutions. I wanted to take a yellow highlighter to it until I realized I’d be highlighting most of the book.” –Curt Hibbs, Chief Agile Evangelist, Boeing Use the ICSM to Generate and Evolve Your Life-Cycle Process Assets to Best Fit Your Organization’s Diverse and Changing Needs Many systems development practitioners find traditional “one-size-fits-all” processes inadequate for the growing complexity, diversity, dynamism, and assurance needs of their products and services. The Incremental Commitment Spiral Model (ICSM) responds with a principle- and risk-based framework for defining and evolving your project and corporate process assets, avoiding pitfalls and disruption, and leveraging opportunities to increase value. This book explains ICSM’s framework of decision criteria and principles, and shows how to apply them through relevant examples. It demonstrates ICSM’s potential for reducing rework and technical debt, improving maintainability, handling emergent requirements, and raising assurance levels. Its coverage includes What makes a system development successful ICSM’s goals, principles, and usage as a process-generation framework Creating and evolving processes to match your risks and opportunities Integrating your current practices and adopting ICSM concepts incrementally, focusing on your greatest needs and opportunities About the Website: Download the evolving ICSM guidelines, subprocesses, templates, tools, white papers, and academic support resources at csse.usc.edu/ICSM.

Principles and Practices for Successful Systems and Software

The Incremental Commitment Spiral Model

IEEE, Press Staff

21st International Conference

Software Engineering (ICSE '99)

Richard Turner

Barry W. Boehm

"Being a certified bibliophile and a professional geek, I have more shelf space devoted to books on software methods than any reasonable human should possess. Balancing Agility and Discipline has a prominent place in that section of my library, because it has helped me sort through the noise and smoke of the current method wars." --From the Foreword by Grady Booch "This is an outstanding book on an emotionally complicated topic. I applaud the authors for the care with which they have handled the subject." --From the Foreword by Alistair Cockburn "The authors have done a commendable job of identifying five critical factors--personnel, criticality, size, culture, and dynamism--for creating the right balance of flexibility and structure. Their thoughtful analysis will help developers who must sort through the agile-disciplined debate, giving them guidance to create the right mix for their projects." --From the Foreword by Arthur Pyster Agility and discipline: These apparently opposite attributes are, in fact, complementary values in software development. Plan-driven developers must also be agile; nimble developers must also be disciplined. The key to success is finding the right balance between the two, which will vary from project to project according to the circumstances and risks involved. Developers, pulled toward opposite ends by impassioned arguments, ultimately must learn how to give each value its due in their particular situations. Balancing Agility and Discipline sweeps aside the rhetoric, drills down to the operational core concepts, and presents a constructive approach to defining a balanced software development strategy. The authors expose the bureaucracy and stagnation that mark discipline without agility, and liken agility without discipline to unbridled and fruitless enthusiasm. Using a day in the life of two development teams and ground-breaking case studies, they illustrate the differences and similarities between agile and plan-driven methods, and show that the best development strategies have ways to combine both attributes. Their analysis is both objective and grounded, leading finally to clear and practical guidance for all software professionals--showing how to locate the sweet spot on the agility-discipline continuum for any given project. 0321186125B10212003

A Guide for the Perplexed

Balancing Agility and Discipline

Azad M. Madni

Daniel Erwin

Mahta Moghaddam

Michael Sievers

Marilee Wheaton

This volume comprises papers from the 18th Conference on Systems Engineering Research (CSER). The theme of this volume, “Recent Trends and Advances in Model-Based Systems Engineering,” reflects the fact that systems engineering is undergoing a transformation motivated by mission and system complexity and enabled by technological advances such as model-based systems engineering, digital engineering, and the convergence of systems engineering with other disciplines. This conference is focused on exploring recent trends and advances in model-based systems engineering (MBSE) and the synergy of MBSE with simulation technology and digital engineering. Contributors have submitted papers on MBSE methods, modeling approaches, integration of digital engineering with MBSE, standards, modeling languages, ontologies and metamodels, and economics analysis of MBSE to respond to the challenges posed by 21st century systems. What distinguishes this volume are the latest advances in MBSE research, the convergence of MBSE with digital engineering, and recent advances in applied research in MBSE, including growing convergence with systems science and decision science. This volume is appropriate as a reference text in graduate engineering courses in Model-Based Systems Engineering.

Recent Trends and Advances in Model Based Systems Engineering

Roger G. Ghanem

Marilee J. Wheaton

The theme of this volume on systems engineering research is disciplinary convergence: bringing together concepts, thinking, approaches, and technologies from diverse disciplines to solve complex problems. Papers presented at the Conference on Systems Engineering Research (CSER), March 23-25, 2017 at Redondo Beach, CA, are included in this volume. This collection provides researchers in academia, industry, and government forward-looking research from across the globe, written by renowned academic, industry and government researchers.

Disciplinary Convergence in Systems Engineering Research

Matt Stephens

Shobha Rani Dhalipathi

Doug Rosenberg

Bo Wang

Charles Suscheck

From the beginning of software time, people have wondered why it isn’t possible to accelerate software projects by simply adding staff. This is sometimes known as the “nine women can’t make a baby in one month” problem. The most famous treatise declaring this to be impossible is Fred Brooks’ 1975 book The Mythical Man-Month, in which he declares that “adding more programmers to a late software project makes it later,” and indeed this has proven largely true over the decades. Aided by a domain-driven code generator that quickly creates database and API code, Parallel Agile (PA) achieves significant schedule compression using parallelism: as many developers as necessary can independently and concurrently develop the scenarios from initial prototype through production code. Projects can scale by elastic staffing, rather than by stretching schedules for larger development efforts. Schedule compression with a large team of developers working in parallel is analogous to hardware acceleration of compute problems using parallel CPUs. PA has some similarities with and differences from other Agile approaches. Like most Agile methods, PA "gets to code early" and uses feedback from executable software to drive requirements and design. PA uses technical prototyping as a risk-mitigation strategy, to help sanity-check requirements for feasibility, and to evaluate different technical architectures and technologies. Unlike many Agile methods, PA does not support "design by refactoring," and it doesn't drive designs from unit tests. Instead, PA uses a minimalist UML-based design approach (Agile/ICONIX) that starts out with a domain model to facilitate communication across the development team, and partitions the system along use case boundaries, which enables parallel development. Parallel Agile is fully compatible with the Incremental Commitment Spiral Model (ICSM), which involves concurrent effort of a systems engineering team, a development team, and a test team working alongside the developers. The authors have been researching and refining the PA process for several years on multiple test projects that have involved over 200 developers. The book’s example project details the design of one of these test projects, a crowdsourced traffic safety system.

Parallel Agile – faster delivery, fewer defects, lower cost

Leon J. Osterweil

Mingshu Li

This book constitutes the thoroughly refereed post-proceedings of the International Software Process Workshop, SPW 2005, help in Beijing, China in May 2005. The 30 papers presented here, together with 11 keynote addresses are organized in topical sections on process content, process tools and metrics, process management, process representation and analysis, as well as experience reports.

International Software Process Workshop, SPW 2005, Beijing, China, May 25-27, 2005 Revised Selected Papers

Unifying the Software Process Spectrum

Paul Grünbacher

Stefan Biffl

Hakan Erdogmus

Aybuke Aurum

Ross Jeffery When, as a result of pressure from the CEO, the Chief Information Officer poses the question “Just what is this information system worth to the organization?” the IT staff members are typically at a loss. “That’s a difficult question,” they might say; or “well it really depends” is another answer. Clearly, neither of these is very satisfactory and yet both are correct. The IT community has struggled with qu- tions concerning the value of an organization’s investment in software and ha- ware ever since it became a significant item in organizational budgets. And like all questions concerning value, the first step is the precise determination of the object being assessed and the second step is the identification of the entity to which the value is beneficial. In software engineering both of these can be difficult. The p- cise determination of the object can be complex. If it is an entire information s- tem in an organizational context that is the object of interest, then boundary defi- tion becomes an issue. Is the hardware and middleware to be included? Can the application exist without any other applications? If however the object of interest is, say, a software engineering activity such as testing within a particular project, then the boundary definition becomes a little easier. But the measure of benefit may become a little harder.

Value-Based Software Engineering

Barry Boehm

About

Books

Join the club