Agile Engineering
summary
Argues that engineering replaces sticker-driven coding culture with quantified design: uses Impact Estimation Table spreadsheets to compute value/cost ratios across multiple stakeholder values; shows IBM Cleanroom-style delivery with 45 increments (≈2% each) to stay on time and budget; cites Intel rollout across ~20,000 engineers using Spec QC + Planguage to cut requirement defects from 312 in a 31‑page draft to 10 in a 435‑page spec (target 0.2 defects/600 words) yielding 100X defect‑prevention; cites Evo case of 16 developers (4×4 teams) winning markets.
AI-written summary · about
chapters (7)
- 0:00Start
- 7:27We Need 'Real Software Engineering, not just about coding Not 'CodeFlow' like some agile methods.
- 12:35Simultaneous Multi-Values and Multi-Cost Requirements; as Agile Efficiency Measure, "Agility for Efficiency".
- 13:51Multi-Value Flow Optimization, Multi-Constraint Consideration
- 31:5412. "Principles of Agile Engineering": Logical Common Sense.
- 38:59DYNAMIC DESIGN OPTIMIZATION
- 39:29AUTOMATE
related talks
42mAgile Engineering Fluency
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
45mBeyond Estimates
40mReal Quality Assurance from an Agile and Lean Viewpoint
31mEngineering Effectiveness: Achieving your goals with less
31mImproving engineering effectiveness: A journey for the entire organization
37mEngineering for Software
49mMaking Value Visible