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

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 and limits ability to take responsibility for quality of work.ii. Enable controls such as pair programming, continuous inspection, automated testing to achieve outcomes intended with controls. e. ENSURE

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 include: poor/improper coding, changing requirements, issues found during testing, inconsistent programming, lack of process rigor, hastiness to demonstrate progress, and poor enterprise architectures. Agile in DoD by William Broadus, Defense AT&L Magazine Agile Methods  Scrum  Extreme Programming (XP)  Kanban  Feature Driven Development (FDD)  Dynamic Systems Development Method

TESTS BEFORE WE WRITE THE CODE (“TEST DRIVEN DEVELOPMENT”) i. TDD – Kent Beck as part of Extreme Programming 1. Ensure the tests fail – “Write a test for the next bit of functionality you want to add”