interviews, demonstrations, etc.)?  Does the program have clear, agreed-upon expectations for the depth and breadth of documentation?  How much planning occurs in early phases and documents vice continually of FPIF contracts under Better Buying Power. This also requires the government to have a more in-depth understanding of the requirements, development work required, and estimated costs to effectively

software systems • The system should first be made to run, even though it does nothing useful • Bit-by-bit it is fleshed out • The morale effects are startling • Enthusiasm jumps when there is a running problem? • Or am I just shaving a yak?Brook’s Advice • The system should first be made to run • Bit-by-bit it is fleshed out • One always has, at every stage in the process, a working system • Enthusiasm

were delivered as a single “product” at the end of a project, a “product” that then only required a bit of maintenance now and then, the economics of IT delivery often favored buying a product off the shelf post is: https://www.facebook.com/groups/AgileForDefense/permalink/2557027747901552/ or https://bit.ly/39IOrGw The group is private so the first time you visit you likely have to wait for an admin to

Changing the Laws of Engineering with GitHub Pull Requests by Ralph Bodenner (New Relic) https://bit.ly/pull-request-your-culture  How you change your process matters  Terms: culture, metaprocess

– 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” 2. Ensure the tests pass – “Write the functional code until the