No Silver Bullet – Essence and Accident in Software Engineering Mike Ballou“There is no single development, in either technology or management technique, which by itself promises even one order-of- published The Mythical Man-Month: Essays on Software Engineering • In 1987, authored No Silver Bullet – Essence and Accident in Software Engineering“We hear desperate cries for a silver bullet – something

approach, program managers need to work with stakeholders representing the requirements, systems engineering, contracting, cost estimating, and testing communities to design processes around short releases It presents options for structuring a program, developing a contract strategy, shaping systems engineering processes, managing requirements, and developing cost estimates for programs with a dynamic scope ............................................................................. 20 9 Systems Engineering ..............................................................................................

at every levelSystems Engineering Role Program leaders must encourage systems engineers to engage developers, testers, users, and other stakeholders in their disciplined engineering processes. (No ivory ivory towers) While Agile systems engineering involves frequent informal technical and programmatic reviews, this less formal approach does not equate to less rigor. Instead, greater frequency allows key

environments (to include production, pre-production, and CD pipeline) iii. Ian Malpass, Etsy – “If Engineering at Etsy has a religion, it’s the Church of Graphs. If it moves, we track it. Sometimes we’ll draw gets visceral feedback on upstream decisions. (Pedro Canahuati, Facebook Director of Production Engineering) iii. Find the proper balance between fixing production issues and new features development –

make it easy for people who have been part of the problem to come along Changing the Laws of Engineering with GitHub Pull Requests by Ralph Bodenner (New Relic) https://bit.ly/pull-request-your-culture

ver=2019-09-26-115824-583 DevSecOps – Defined by DoD CIO DevSecOps is an organizational software engineering culture and practice that aims at unifying software development (Dev), security (Sec) and operations

Security in the same manner as QA and operations b. Compliance checking is the opposite of security engineering c. INTEGRATE SECURITY INTO DEVELOPMENT ITERATION DEMONSTRATIONS i. Bring Infosec left; incorporate