Incremental Commitment Spiral Model, Expedited Engineering,

and Kanban

Jo Ann Lane and Alexey Tregubov USC CSSE

Rich TurnerStevens University

CSSE ARR 2013 2

Outline

• Incremental Commitment Spiral Model (ICSM) Overview

• ICSM and lean engineering• Kanban processes for large, complex

development organizations

3/13/13

CSSE ARR 2013

What is the ICSM?

• Risk-driven framework for determining and evolving best-fit system life-cycle process

• Integrates the strengths of phased and risk-driven spiral process models

• Synthesizes together principles critical to successful system development– Stakeholder value-based system definition and evolution– Incremental commitment and accountability– Concurrent hardware, human factors, and software system

definition and development– Evidence-based and risk-based decision-making

Principles trump diagrams…

Principles used by 60-80% of CrossTalk Top-5 projects, 2002-200533/13/13

CSSE ARR 2013

Risk-Driven Scalable Spiral Model: Increment View

Agile Rebaselining for

Future Increments

Short, StabilizedDevelopment

of Increment N

Verification and Validation (V&V)of Increment N

Deferrals

Artifacts Concerns

Rapid Change

HighAssurance

Future Increment Baselines

Increment N Transition/

Operations and Maintenance

Future V&V

Resources

Increment N Baseline

Current V&V

Resources

Unforeseeable Change (Adapt)

ShortDevelopmentIncrements

ForeseeableChange

(Plan)

Stable DevelopmentIncrements

Continuous V&V43/13/13

CSSE ARR 2013

Small Custom Software Systems

3/13/13 5

Case ID Name Description

1 AgileSoftware developed using pure agile methods with short-duration sprints

2 Architected agile

Initial sprint focuses on foundations/architecture issues, then transitions to pure agile process for development of software capabilities

3 Formal methods

Critical software system or subsystem, often containing security- or safety-relevant software or critical/high-precision algorithms that must be rigorously developed, tested, and often certified

CSSE ARR 2013

COTS-Based

3/13/13 6

Case ID Name Description

4 COTS-Based System

Systems range from single COTS products to multiple integrated COTS products.

Larger, More Complex Hardware/Software Systems

3/13/13 CSSE ARR 2013 7

Case ID Name Description

5 Software-intensive device

Hardware-software user-interactive device not part of a product line

6 Large software-intensive system

Large software-intensive system with varying component types/complexity. Differs from system of systems in that components are typically always integrated and not reconfigured for specific system missions.

7 Platform-based systemLarge-scale platform with embedded software systems. Development is driven by hardware platform and software supports platform capabilities.

8 System of systems/ enterprise-wide systems

Set of independent (constituent) systems that can be integrated together in a manner that allows them to interoperate and perform cross-cutting mission-specific capabilities.

9 Family of systems/product lines

Set of systems that can interoperate with each other or are related to each other (e.g., have common components) as part of a product line.

10 Brownfield modernization

Incremental legacy phase-out.

CSSE ARR 2013 8

Basis for Spin and Increment Planning

MC 1 MC 2 MC 3

Req 1 Req 2 Req 3 Req 4 Req 5 Req 6 Req 7 Req 8

Product 1 Product 2 Product 3 Product 4

Product 1: Req 1 Req 2 Req 3 Req 6

Product 2: Req 1 Req 3 Req 4 Req 6

Product 3: Req 1 Req 2 Req 5 Req 7

Product 4: Req 1 Req 2 Req 3 Req 4 Req 5 Req 7 Req 8

Interface ReqsComputation ReqsPerformance Reqs

3/13/13

CSSE ARR 2013 9

Kanban Scheduling System (KSS) Network

3/13/13

CSSE ARR 2013 10

Classes of Service

• Critical Expedite• Important• Date Certain• Standard • Background

3/13/13

CSSE ARR 2013 11

Health Care Example

• New capability to interface to a new health insurance company

• New capability to integrate and analyze information from multiple patient telemetry systems to improve diagnostic capabilities

• User response improvement• Periodic upgrade of pharmacy formulary

information• Patient safety issue due to interoperability problem3/13/13

CSSE ARR 2013 12

Kanban Flow for Healthcare Examples

3/13/13

CSSE ARR 2013 13

Future Work

• Continue work on – “Value” strategies– Priority strategies

• Identify organizations to pilot• Work with Kanban tool vendors

More details on this in next presentation…

3/13/13

CSSE ARR 2013 14

Questions?

3/13/13