“I can tell you I came up with that word (Agile) because I was familiar with the book Agile Competitors and Virtual Organisations. We had proposed Adaptive, Essential, Lean and Lightweight.
– We did not want to use Adaptive because Jim Highsmith had given this to one of his works.
– Essential sounded overly proud.
– Lean had already been taken.
– Nobody wanted to be a lightweight.
We did this late in the second day and it took only a few minutes to decide on this.” ~ Mike Beedle
- Scrum Theory and Principles
- The New New Product Development Game
- A Leader’s Framework for Decision Making
- The Leader’s Guide to Radical Management: Reinventing the Workplace for the 21st Century
- Agile Project Management with Scrum (Developer Best Practices)
- The Art of Agile Development: Pragmatic Guide to Agile Software Development
- The Pragmatic Programmer: From Journeyman to Master
- The Scrum Framework
- Cross-functional, Self-organizing Teams
- The Five Dysfunctions of a Team: A Leadership Fable
- Drive: The Surprising Truth About What Motivates Us
- Peopleware: Productive Projects and Teams
- Extreme Ownership: How U.S. Navy SEALs Lead and Win
- Scrum and XP from the Trenches (Enterprise Software Development)
- Practices of an Agile Developer: Working in the Real World
- Maximizing Value
- The Professional Product Owner: Leveraging Scrum as a Competitive Advantage
- Software in 30 Days: How Agile Managers Beat the Odds, Delight Their Customers, and Leave Competitors in the Dust
- The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses
- Product Backlog Management
- Analysis
- Emergent Architecture
- Programming
- Test First Development
- Standards
- Testing
- ALM – Application Lifecycle Management