Learning Agile is a comprehensive guide to the most popular agile methods, written in a light and engaging style that makes it easy for you to learn.
Agile has revolutionized the way teams approach software development, but with dozens of agile methodologies to choose from, the decision to "go agile" can be tricky. This practical book helps you sort it out, first by grounding you in agile’s underlying principles, then by describing four specific—and well-used—agile methods: Scrum, extreme programming (XP), Lean, and Kanban.
Table of contents
- 1. Learning Agile
2. Understanding Agile Values
- A Team Lead, Architect, and Project Manager Walk into a Bar...
- No Silver Bullet
- Agile to the Rescue! (Right?)
- A Fractured Perspective
- The Agile Manifesto Helps Teams See the Purpose Behind Each Practice
- Understanding the Elephant
- Where to Start with a New Methodology
3. The Agile Principles
- The 12 Principles of Agile Software
- The Customer Is Always Right...Right?
Delivering the Project
- Principle #1: Our Highest Priority Is to Satisfy the Customer Through Early and Continuous Delivery of Valuable Software.
- Principle #2: Welcome Changing Requirements, Even Late In Development. Agile Processes Harness Change for the Customer’s Competitive Advantage.
- Principle #3: Deliver Working Software Frequently, from a Couple of Weeks to a Couple of Months, with a Preference to the Shorter Timescale.
- Better Project Delivery for the Ebook Reader Project
Communicating and Working Together
- Principle #4: The Most Efficient and Effective Method of Conveying Information To and Within a Development Team Is Face-To-Face Conversation.
- Principle #5: Businesspeople and Developers Must Work Together Daily Throughout the Project.
- Principle #6: Build Projects Around Motivated Individuals. Give Them the Environment and Support They Need, and Trust Them to Get the Job Done.
- Better Communication for the Ebook Reader Project
Project Execution—Moving the Project Along
- Principle #7: Working Software Is the Primary Measure of Progress.
- Principle #8: Agile Processes Promote Sustainable Development. The Sponsors, Developers, and Users Should Be Able to Maintain a Constant Pace Indefinitely.
- Principle #9: Continuous Attention to Technical Excellence and Good Design Enhances Agility.
- A Better Working Environment for the Ebook Reader Project Team
Constantly Improving the Project and the Team
- Principle #10: Simplicity—the Art of Maximizing the Amount of Work Not Done—Is Essential.
- Principle #11: The Best Architectures, Requirements, and Designs Emerge from Self-Organizing Teams.
- Principle #12: At Regular Intervals, the Team Reflects on How to Become More Effective, Then Tunes and Adjusts Its Behavior Accordingly.
- The Agile Project: Bringing All the Principles Together
4. Scrum and Self-Organizing Teams
- The Rules of Scrum
- Act I: I Can Haz Scrum?
- Everyone on a Scrum Team Owns the Project
- Act II: Status Updates Are for Social Networks!
- The Whole Team Uses the Daily Scrum
- Act III: Sprinting into a Wall
- Sprints, Planning, and Retrospectives
- Act IV: Dog Catches Car
5. Scrum Planning and Collective Commitment
- Act V: Not Quite Expecting the Unexpected
- User Stories, Velocity, and Generally Accepted Scrum Practices
- Act VI: Victory Lap
- Scrum Values Revisited
6. XP and Embracing Change
- Act I: Going into Overtime
- The Primary Practices of XP
- Act II: The Game Plan Changed, but We’re Still Losing
- The XP Values Help the Team Change Their Mindset
- An Effective Mindset Starts with the XP Values
- Act III: The Momentum Shifts
- Understanding the XP Principles Helps You Embrace Change
7. XP, Simplicity, and Incremental Design
- Act IV: Going into Overtime, Part 2: Second Overtime
- Code and Design
- Make Code and Design Decisions at the Last Responsible Moment
Incremental Design and the Holistic XP Practices
- Teams Work Best When They Feel Like They Have Time to Think
- Team Members Trust Each Other and Make Decisions Together
- The XP Design, Planning, Team, and Holistic Practices Form an Ecosystem That Spurs Innovation
- Incremental Design Versus Designing for Reuse
- When Units Interact in a Simple Way, the System Can Grow Incrementally
- Great Design Emerges from Simple Interactions
- Act V: Final Score
8. Lean, Eliminating Waste, and Seeing the Whole
- Lean Thinking
- Act I: Just One More Thing...
- Creating Heroes and Magical Thinking
- Eliminate Waste
- Gain a Deeper Understanding of the Product
- Deliver As Fast As Possible
9. Kanban, Flow, and Constantly Improving
- Act II: Playing Catch-Up
- The Principles of Kanban
- Improving Your Process with Kanban
- Measure and Manage Flow
- Emergent Behavior with Kanban
10. The Agile Coach
- Act III: Just One More Thing (Again?!)...
- Coaches Understand Why People Don’t Always Want to Change
- Coaches Understand How People Learn
- Coaches Understand What Makes a Methodology Work
- The Principles of Coaching
- Title: Learning Agile
- Release date: November 2014
- Publisher(s): O'Reilly Media, Inc.
- ISBN: 9781449331924
You might also like
Succeeding with Agile
Proven, 100% Practical Guidance for Making Scrum and Agile Work in Any Organization This is the …
Breaking Into Product Management
Product management (PM) has emerged as an exciting and highly desirable career path, offering opportunities to …
40 Algorithms Every Programmer Should Know
Learn algorithms for solving classic computer science problems with this concise guide covering everything from fundamental …
User Stories Applied: For Agile Software Development
Thoroughly reviewed and eagerly anticipated by the agile community, User Stories Applied offers a requirements process …