國立虎尾科技大學 |

Parallel Agile – faster delivery, fewer defects, lower cost

Record Type:	Language materials, printed : Monograph/item
Title/Author:	Parallel Agile – faster delivery, fewer defects, lower cost/ by Doug Rosenberg, Barry Boehm, Matt Stephens, Charles Suscheck, Shobha Rani Dhalipathi, Bo Wang.
Author:	Rosenberg, Doug.
other author:	Boehm, Barry.
Description:	XIX, 221 p. 120 illus.online resource. :
Contained By:	Springer Nature eBook
Subject:	Software engineering. -
Online resource:	https://doi.org/10.1007/978-3-030-30701-1
ISBN:	9783030307011

Parallel Agile – faster delivery, fewer defects, lower cost
Rosenberg, Doug.

Parallel Agile – faster delivery, fewer defects, lower cost[electronic resource] /by Doug Rosenberg, Barry Boehm, Matt Stephens, Charles Suscheck, Shobha Rani Dhalipathi, Bo Wang. - 1st ed. 2020. - XIX, 221 p. 120 illus.online resource.

1. Parallel Agile Concepts -- 2. Inside Parallel Agile -- 3. CodeBots: From Domain Model to Executable Architecture -- 4. Parallel Agile by Example: CarmaCam -- 5. Taking the Scream Out of Scrum -- 6. Test Early, Test Often -- 7. Managing Parallelism: Faster Delivery, Fewer Defects, Lower Cost -- 8. Large-Scale Parallel Development -- 9. Parallel Agile for Machine Learning -- Appendix A. The Scream Guide -- Appendix B. Architecture Blueprints.

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.

ISBN: 9783030307011

Standard No.: 10.1007/978-3-030-30701-1doiSubjects--Topical Terms:

562952
Software engineering.

LC Class. No.: QA76.758

Dewey Class. No.: 005.1

Parallel Agile – faster delivery, fewer defects, lower cost
LDR:04172nam a22004095i 4500 001 1021860
003 DE-He213
005 20200702115059.0
007 cr nn 008mamaa
008 210318s2020 gw | s |||| 0|eng d
020 $a 9783030307011 $9 978-3-030-30701-1
024 7 $a 10.1007/978-3-030-30701-1 $2 doi
035 $a 978-3-030-30701-1
050 4 $a QA76.758
072 7 $a UMZ $2 bicssc
072 7 $a COM051230 $2 bisacsh
072 7 $a UMZ $2 thema
072 7 $a UL $2 thema
082 0 4 $a 005.1 $2 23
100 1 $a Rosenberg, Doug. $4 aut $4 http://id.loc.gov/vocabulary/relators/aut $3 673295
245 1 0 $a Parallel Agile – faster delivery, fewer defects, lower cost $h [electronic resource] / $c by Doug Rosenberg, Barry Boehm, Matt Stephens, Charles Suscheck, Shobha Rani Dhalipathi, Bo Wang.
250 $a 1st ed. 2020.
264 1 $a Cham : $b Springer International Publishing : $b Imprint: Springer, $c 2020.
300 $a XIX, 221 p. 120 illus. $b online resource.
336 $a text $b txt $2 rdacontent
337 $a computer $b c $2 rdamedia
338 $a online resource $b cr $2 rdacarrier
347 $a text file $b PDF $2 rda
505 0 $a 1. Parallel Agile Concepts -- 2. Inside Parallel Agile -- 3. CodeBots: From Domain Model to Executable Architecture -- 4. Parallel Agile by Example: CarmaCam -- 5. Taking the Scream Out of Scrum -- 6. Test Early, Test Often -- 7. Managing Parallelism: Faster Delivery, Fewer Defects, Lower Cost -- 8. Large-Scale Parallel Development -- 9. Parallel Agile for Machine Learning -- Appendix A. The Scream Guide -- Appendix B. Architecture Blueprints.
520 $a 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.
650 0 $a Software engineering. $3 562952
650 0 $a Management information systems. $3 561123
650 0 $a Computer science. $3 573171
650 1 4 $a Software Engineering/Programming and Operating Systems. $3 669780
650 2 4 $a Management of Computing and Information Systems. $3 593928
700 1 $a Boehm, Barry. $e editor. $4 aut $4 http://id.loc.gov/vocabulary/relators/aut $3 1284757
700 1 $a Stephens, Matt. $4 aut $4 http://id.loc.gov/vocabulary/relators/aut $3 673296
700 1 $a Suscheck, Charles. $e author. $4 aut $4 http://id.loc.gov/vocabulary/relators/aut $3 1317556
700 1 $a Dhalipathi, Shobha Rani. $e author. $4 aut $4 http://id.loc.gov/vocabulary/relators/aut $3 1317557
700 1 $a Wang, Bo. $4 aut $4 http://id.loc.gov/vocabulary/relators/aut $3 1204810
710 2 $a SpringerLink (Online service) $3 593884
773 0 $t Springer Nature eBook
776 0 8 $i Printed edition: $z 9783030307004
776 0 8 $i Printed edition: $z 9783030307028
776 0 8 $i Printed edition: $z 9783030307035
856 4 0 $u https://doi.org/10.1007/978-3-030-30701-1
912 $a ZDB-2-SCS
912 $a ZDB-2-SXCS
950 $a Computer Science (SpringerNature-11645)
950 $a Computer Science (R0) (SpringerNature-43710)