Max Geurnsey III and Luniel de Beer, co-authors of the book Ready: Why Most Software Projects Fail and How to Fix It, discuss the concept of readiness in software engineering with host Brijesh Ammanath. Although Agile workflows and technical practices help delivery, many software efforts still struggle to achieve desired outcomes. Rework, shifting requirements, delays, defects, and mounting technical debt can plague software delivery and impede or altogether halt progress toward goals. The problem is often that implementation begins prematurely, before the team is properly set up for success. A strict system of explicit readiness work and gating, called Requirements Maturation Flow (RMF), has the potential to solve this problem in an SDLC-independent way. Teams that adopt RMF can dramatically improve progress toward real goals while reducing stress on engineering teams. In this episode, Max and Luniel deep dive into RMF and explain its foundational pillars.
Key Objectives:
- Understand why most software projects fail, what causes rework, under-delivery and delays.
- What is Requirements Maturation Flow and its 3 foundational practices?
- Understanding the value of having Readiness as a explicit work item
- Understanding Definition of Done
- Understanding Definition of Ready
Brought to you by IEEE Computer Society and IEEE Software magazine.
Show Notes
Related Episodes
- SE Radio 420: Ryan Ripley on Making Scrum Work
- SE Radio 543: Jon Smart on Patterns and Anti-Patterns for Successful Software Delivery in Enterprises
- SE Radio 389: Ryan Singer on Basecamp’s Software Development Process
Related Links
- Book:
- Requirements Maturation Flow: The Requirements Maturation Flow Series – Producore
- BDD: What is Behavior-Driven Development? | Luniel’s Portfolio
- Cargo Cult Programming: In John They Trust
