國立虎尾科技大學 |

The Agile Codex = Re-inventing Agile Through the Science of Invention and Assembly /

紀錄類型:	書目-語言資料,印刷品 : Monograph/item
正題名/作者:	The Agile Codex/ by Michael McCormick.
其他題名:	Re-inventing Agile Through the Science of Invention and Assembly /
作者:	McCormick, Michael.
面頁冊數:	VII, 159 p. 59 illus.online resource. :
Contained By:	Springer Nature eBook
標題:	Software engineering. -
電子資源:	https://doi.org/10.1007/978-1-4842-7280-0
ISBN:	9781484272800

The Agile Codex = Re-inventing Agile Through the Science of Invention and Assembly /
McCormick, Michael.

The Agile CodexRe-inventing Agile Through the Science of Invention and Assembly /[electronic resource] :by Michael McCormick. - 1st ed. 2021. - VII, 159 p. 59 illus.online resource.

Chapter 1: Clear Ownership -- Chapter 2: Small Independent Units of Work -- Chapter 3: Sized- Chapter 4: Sequenced -- Part 2: Agile Codex Practices -- Chapter 5: Inputs Transition Criteria Outputs -- Chapter 6: Stakeholder Approval -- Chapter 7: The Problem -- Chapter 8: The Codex -- Chapter 9: The Agile -- Chapter 10: Benefits -- Chapter 11: From Invention to Assembly Line -- Chapter 12: Team Functions -- Chapter 13: Software Development Lifecyle -- Chapter 14: Risk Management -- Chapter 15: Building Blocks -- Chapter 16: Workflow -- Chapter 17: Metrics -- Chapter 18: Teaching the Teams -- Chapter 19: What's Next? -- Chapter 20: Conclusion. .

Apply the industrial engineering science of invention and assembly to how software is described, planned, and built, allowing you to be free to flex your practices according to your needs, putting principle over habit and rules. Reading about Agile practices is like reading diet advice. Everything sounds unique and good; everything starts with good intentions. Then reality sets in. Organizations adapt their practices, but lose sight of grounding principles. A bias toward ceremonies, metrics, and recipes comes at the expense of efficiently getting the real work done. Managers and developers are incentivized to game the system. Organizational metrics become detached from the reality of what is being delivered and how. The Agile Codex shows you how to describe a software project as an acyclic dependency tree of sized work items, scoped to be operated on by one software engineer each and completed within a week. It provides Open Source tooling to help you visualize, sequence and assign these work items to account for risk and increase predictability in your delivery times. You’ll see the value of doing this as it applies to efficiently planning and adjusting software projects in the face of learning and change. Finally, the book covers the collaborative agile principles required to bring this skill set and practice to a software team. Throughout the book you’ll be reminded that software engineering is not a rote task - it is primarily a skilled, creative act. As such, you’ll see that we need to account for the space needed to research, plan, create, and adjust. The Agile practices serving the codex deal with this intersection between the engineering problem of software delivery flow, and the human reality of how work is described, owned, executed, and transitioned from one state to another. Everything an agile team does must serve the codex. The creation and the care and feeding of this structured tree of work sets the frame in which all other team actions take place and against which all successes or failures can be evaluated.

ISBN: 9781484272800

Standard No.: 10.1007/978-1-4842-7280-0doiSubjects--Topical Terms:

562952
Software engineering.

LC Class. No.: QA76.758

Dewey Class. No.: 005.1

The Agile Codex = Re-inventing Agile Through the Science of Invention and Assembly /
LDR:04061nam a22003975i 4500 001 1048891
003 DE-He213
005 20210907103224.0
007 cr nn 008mamaa
008 220103s2021 xxu| s |||| 0|eng d
020 $a 9781484272800 $9 978-1-4842-7280-0
024 7 $a 10.1007/978-1-4842-7280-0 $2 doi
035 $a 978-1-4842-7280-0
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 McCormick, Michael. $e author. $4 aut $4 http://id.loc.gov/vocabulary/relators/aut $3 1352890
245 1 4 $a The Agile Codex $h [electronic resource] : $b Re-inventing Agile Through the Science of Invention and Assembly / $c by Michael McCormick.
250 $a 1st ed. 2021.
264 1 $a Berkeley, CA : $b Apress : $b Imprint: Apress, $c 2021.
300 $a VII, 159 p. 59 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 Chapter 1: Clear Ownership -- Chapter 2: Small Independent Units of Work -- Chapter 3: Sized- Chapter 4: Sequenced -- Part 2: Agile Codex Practices -- Chapter 5: Inputs Transition Criteria Outputs -- Chapter 6: Stakeholder Approval -- Chapter 7: The Problem -- Chapter 8: The Codex -- Chapter 9: The Agile -- Chapter 10: Benefits -- Chapter 11: From Invention to Assembly Line -- Chapter 12: Team Functions -- Chapter 13: Software Development Lifecyle -- Chapter 14: Risk Management -- Chapter 15: Building Blocks -- Chapter 16: Workflow -- Chapter 17: Metrics -- Chapter 18: Teaching the Teams -- Chapter 19: What's Next? -- Chapter 20: Conclusion. .
520 $a Apply the industrial engineering science of invention and assembly to how software is described, planned, and built, allowing you to be free to flex your practices according to your needs, putting principle over habit and rules. Reading about Agile practices is like reading diet advice. Everything sounds unique and good; everything starts with good intentions. Then reality sets in. Organizations adapt their practices, but lose sight of grounding principles. A bias toward ceremonies, metrics, and recipes comes at the expense of efficiently getting the real work done. Managers and developers are incentivized to game the system. Organizational metrics become detached from the reality of what is being delivered and how. The Agile Codex shows you how to describe a software project as an acyclic dependency tree of sized work items, scoped to be operated on by one software engineer each and completed within a week. It provides Open Source tooling to help you visualize, sequence and assign these work items to account for risk and increase predictability in your delivery times. You’ll see the value of doing this as it applies to efficiently planning and adjusting software projects in the face of learning and change. Finally, the book covers the collaborative agile principles required to bring this skill set and practice to a software team. Throughout the book you’ll be reminded that software engineering is not a rote task - it is primarily a skilled, creative act. As such, you’ll see that we need to account for the space needed to research, plan, create, and adjust. The Agile practices serving the codex deal with this intersection between the engineering problem of software delivery flow, and the human reality of how work is described, owned, executed, and transitioned from one state to another. Everything an agile team does must serve the codex. The creation and the care and feeding of this structured tree of work sets the frame in which all other team actions take place and against which all successes or failures can be evaluated.
650 0 $a Software engineering. $3 562952
650 0 $a Project management. $3 558297
650 0 $a Leadership. $3 562584
650 0 $a Organization. $3 568089
650 0 $a Planning. $3 660157
650 0 $a Management. $3 558618
650 0 $a Business. $3 558617
650 0 $a Management science. $3 719678
650 1 4 $a Software Engineering/Programming and Operating Systems. $3 669780
650 2 4 $a Project Management. $3 787187
650 2 4 $a Business Strategy/Leadership. $3 796119
650 2 4 $a Business and Management, general. $3 1069500
710 2 $a SpringerLink (Online service) $3 593884
773 0 $t Springer Nature eBook
776 0 8 $i Printed edition: $z 9781484272794
776 0 8 $i Printed edition: $z 9781484272817
856 4 0 $u https://doi.org/10.1007/978-1-4842-7280-0
912 $a ZDB-2-CWD
912 $a ZDB-2-SXPC
950 $a Professional and Applied Computing (SpringerNature-12059)
950 $a Professional and Applied Computing (R0) (SpringerNature-43716)