Elfenbaum , CIO, Schafer Corp. Each of the many existing Agile methods (e.g., Scrum, Extreme Programming (XP), Kanban, Test Driven Development) has its own unique processes, terms, techniques, and timelines amount of work the team estimates it can deliver in a sprint Development teams, aided by cross-functional representatives, analyze each user story and use measures known as story points to estimate the decisions to be made at that level. Development can be effectively managed by a small cross-functional government team. Team Size Many government stakeholders will be involved in the software

specification and represent working examples of API use e. DESIGN FOR OPERATIONS THROUGH CODIFIED NON-FUNCTIONAL REQUIREMENTS i. Designing for fast flow, deployability, and operations will derive NFRs. Codify Dynamic Analysis – tests executed while a program is in operation. Monitor items such as memory, functional behavior, and other elements. Testing from the outside-in 3. Dependency Scanning – inventory servers and ensure they can be reproduced in automated manner 2. Review all changes through pair programming or code review 3. Instrument the repository to detect suspicious code (API calls from certain

Beck as part of Extreme Programming 1. Ensure the tests fail – “Write a test for the next bit of functionality you want to add” 2. Ensure the tests pass – “Write the functional code until the test passes”3 itself iv. Log performance results and evaluate compared to previous results l. INTEGRATE NON-FUNCTIONAL REQUIREMENTS TESTING INTO OUR TEST SUITE i. Incorporate automate tests to validate the “-ilities”

generate measurable improvement or actionable data within weeks f. RESERVE 20% OF CYCLES FOR NON-FUNCTIONAL REQUIREMENTS AND REDUCING TECHNICAL DEBT i. Don’t just make the interest payments, pay down the b. ORGANIZATIONAL ARCHETYPES i. Functional-oriented 1. Optimized for expertise, division of labor, or reducing cost ii. Matrixed-oriented 1. Combines functional and market orientation 2. Often results Often flat, cross-disciplined 3. Most aligned with DevOps c. PROBLEMS OFTEN CAUSED BY OVERLY FUNCTIONAL ORIENTATION (“OPTIMIZING FOR COST”) i. Leads to limited outward visibility ii. Encourages long

shifted to the left through automated unit, functional, integration, and security testing - this is a key DevSecOps differentiator since security and functional capabilities are tested and built simultaneously favor small, incremental, frequent updates over larger, more sporadic releases.  Apply the cross-functional skill sets of Development, Cybersecurity, and Operations throughout the software lifecycle, embracing

steward the asset that is the total of all of the enterprise’s IT capabilities—an asset that has functional capabilities (how it is used today) but also latent capabilities (how it will support future agility is the point at which we are finished investing and just need to “maintain.” But unless we want functional and technical debt, a lumpy EA, and a need to do an expensive and risky transformation effort demonstrate understanding—witnessing employees’ contributions and removing impediments.  Cross-functional and team-based: It used to be natural for ops specialists to do ops, developers to do development

have time to change their minds" - Mary PoppendieckTeam -> Program -> Portfolio Team  Cross functional  Scrum  Release cadence  HIP Program  Built on Scrum, except scaled up  self-organizing

abstract software entity, and accidental tasks, the representation of the abstract entities in programming languages and the mapping of these onto machine languages within space and speed constraints have made the accidental tasks inordinately hard, such as severe hardware constraints, awkward programming languages, lack of machine time. How much of what software engineers now do is still devoted • Preserves immediacy, and hence enables us to maintain an overview of complexity • Unified programming environment • They attack the accidental difficulties of using tools togetherHopes for the Silver“Now

into daily work – enable flow, more automated testing h. ENABLE PAIR PROGRAMMING TO IMPROVE ALL OUR CHANGES i. Pair Programming – two engineers working together at the same workstation. Popularized increased from 70% to 85%. Since testing and debugging are often many times more costly than initial programming, this is an impressive result. Pairs typically consider more design alternatives than programmers