Faster delivery, fewer defects, lower cost.

Time is money.  Parallel Agile gets you to market faster.

In software development, faster-to-market wins.

Parallel Agile is a major breakthrough in software engineering that lets large teams of developers work together in parallel, drastically reducing time to market on your software project.  Instead of stretching out the schedule for bigger projects with a never-ending series of 2-week sprints, a backlog the size of Mount Everest and a steaming pile of technical debt, you can add more developers and get to market much faster and with higher quality code  than on typical agile/scrum projects.

Parallel Agile shortens schedules by applying parallel processing strategies to software engineering

Doug Rosenberg presented Parallel Agile to USC CS577 in September 2018.  Watch the lecture video here.

Parallel Agile is the result of a multi-year collaboration between Professor Barry Boehm (author of Balancing Agility and Discipline, Software Engineering Economics and the Incremental Commitment Spiral Model) and Doug Rosenberg (author of Use Case Driven Object Modeling with UML, Design Driven Testing, and Agile Development with ICONIX Process).

Parallel Agile projects scale by adding developers, not stretching the schedule.

Parallel Agile projects proceed in three phases: Proof of Concept where we get to code early by doing extensive prototyping, Minimum Viable Product, which follows a use case and Model-View-Controller (MVC) paradigm and Initial Release, which focuses on acceptance testing.  Each phase is roughly a month long.  So even large systems can be brought to market in around 3 months if enough developers are available.

Parallel Agile's 3-phase approach results in feedback driven, carefully planned, thoroughly tested systems


Just enough planning is more cost-effective than underplanning or overplanning.

Most agile projects operate on the "underplanned" side of the cost curve.  Typically this happens because the Agile Manifesto values "Responding to change over following a plan".  With this manifesto as the founding document of the agile movement, the agile mindset often doesn't recognize that underplanning is just as expensive as overplanning on a software project.  The result is often "hotfix driven development".

Parallel Agile restores a balance between feedback and planning but retains an agile project management approach.  It's agile on the management side and model-driven on the technical side.

Parallel Agile restores the balance between feedback and planning, operating at the cost minimum