Patterns of Software Construction: How to Predictably Build Results

ISBN-13: 9781484279359 / Angielski / Miękka / 2022 / 156 str.

Stephen Rylander

Spis treści

Chapter 1: Not a Process

o 1.1 System

o 1.2 The Problem

o 1.3 Reality

o 1.4 The Solution

o 1.5.The Evolutions

Chapter 2 LIFT System Evolutions

Chapter 3 Plan

o 3.1 Plan

o 3.1 Target

o 3.1 Map it out

o 3.1 Development Strategy

Chapter 4 Build

o 4.1 Anatomy of a Sprint

o 4.2 Most Software Looks like this.

o 4.3 Non-functional Requirements Pay the Bills

o 4.4 …

Chapter 5 Test

Chapter 6 Release

Chapter 7 Operate

Chapter 8 Manage

Chapter 9 The Long Game

Chapter 10 - Summary

O autorze

Stephen Rylander is currently SVP, Global Head of Engineering Company at Donnelley Financial Solutions. He is a software engineer turned technical executive who has seen a variety of industries from music, to ecommerce, to finance and more. He is invested in improving the practice of software delivery, operational platforms and all the people involved in making this happen. He has worked on platforms handling millions of daily transactions and developed digital transformation programs driving financial platforms. He has also had the opportunity to construct platforms with digital investing advice engines and has a history of dealing with scale and delivering results leading local and distributed teams. 

For fun he used to also run the API Craft Chicago Meetup, help organize Morningstar Tech Talks and has been a member mentor at 1871 - Chicago's Technology & Entrepreneurship Center.

Blurb

Master how to implement a repeatable software construction system. This book closely examines how a system is designed to tie a series of activities together that are needed when building software-intensive systems. 

Software construction and operations don't get enough attention as a repeatable system. The world is stuck in agile backlog grooming sessions, and quality is not increasing. Companies' budgets are shrinking, and teams need a way to get more done with less, consistently. This topic is very relevant to our current economic conditions and continuing globalization trends. A reason we constantly need more hands-on-the-keyboards is because of all the waste created in development cycles. We need more literature on how to "do software" not just write software.  

These goals are accomplished using the concept of evolutions, much like the Navy SEALS train their team members.  For LIFT, the evolutions are: Plan, Build, Test, Release, Operate and Manage.  The entire purpose of the book is instructing professionals how to use these distinct evolutions while remaining agile. And then, inside of each evolution, to explicitly break down the inputs to the evolution, outputs and series of activities taking place. Patterns of Software Construction clearly outlines how together this becomes the system.

You will:

• Optimize each evolution of a software delivery cycle
• Review best practices of planning, highest return in the build cycle, and ignored practices in test, release, and operate 
• Apply the highest return techniques during the software build evolution