liveBook · Manning

Agile software development

Also called Agile methodology, Agile approach, agile development, Agile methods, Agile process

Agile software development is an iterative approach to developing software through incremental delivery, collaboration, feedback, and adaptation to change.

How 5 Manning books explain it

Lead Developer Career Guide

A software development practice based on iterative delivery, continuous feedback, and adaptation to change.

How it is used
Organizes software project work around incremental delivery, collaboration, customer feedback, and adaptation to changing requirements.
How deep it goes
Defines agile, outlines Scrum roles and activities and Kanban flow, and compares waterfall; stops short of a detailed implementation procedure.
Examples
Uses omitted Scrum reviews and retrospectives, a difficult waterfall-to-agile transition, and client budget decisions as workplace examples.
What you can do after
Practice/perform it by preserving feedback activities and proposing specific process improvements when a team’s agile routines fall short.

Read how Lead Developer Career Guide explains agile software development →

Delivering Machine Learning Projects: From design to deployment

Agile development is an iterative software development approach emphasizing early delivery, customer collaboration, and responsiveness to change.

How it is used
Organizes machine learning delivery into adaptive sprints and backlogs, from project setup through production.
How deep it goes
Defines agile principles and outlines sprint checklists and working agreements, while recognizing that teams use different practices.
Examples
Illustrates project practices with a bike shop case study and unplanned performance experiments for novel hardware.
What you can do after
Practice organizing adaptive project work with sprints, backlogs, checklists, and explicit working agreements.

Read how Delivering Machine Learning Projects: From design to deployment explains agile software development →

Think Like a CTO

An iterative development and project-management approach that delivers work in small increments and adapts plans based on feedback and changing requirements.

How it is used
Organizes a defined development outcome into smaller tasks to help manage uncertain project timelines.
How deep it goes
Explains the project-planning trade-off with waterfall and notes smaller components, without specifying an agile framework or iteration procedure.
Examples
Uses a customer-intake modernization project to distinguish its stated outcome from the tasks needed to reach it.
What you can do after
Practice/perform project breakdown by defining an outcome, dividing work into smaller components, and tracking task status.

Read how Think Like a CTO explains agile software development →

Collaborative Software Design: How to facilitate domain modeling decisions

Agile software development is an iterative approach to software development that emphasizes collaboration, feedback, adaptability, and incremental delivery.

How it is used
Uses incremental delivery and user feedback to guide software development while exposing the organizational conditions needed for genuine agility.
How deep it goes
Explains incremental delivery, collaboration, and Agile theater through consequences, but stops short of prescribing a specific framework or workflow.
Examples
Uses BigScreen’s refactoring conflict, neglected architecture, interconnected codebase, and delivery-process comparison as teaching examples.
What you can do after
Evaluate whether Agile adoption changes organizational decision-making or merely accelerates development within a waterfall structure.

Read how Collaborative Software Design: How to facilitate domain modeling decisions explains agile software development →

Build Financial Software with Generative AI (From Scratch)

Agile is an iterative software-development approach that emphasizes incremental delivery, collaboration, and adaptation to changing requirements.

How it is used
Uses short development cycles to organize an ACH project within a large FinTech delivery process.
How deep it goes
Defines program increments, sprints, epics, and user stories, but does not detail Agile ceremonies or engineering practices.
Examples
Uses an ACH project that progresses from file processing to APIs and a user interface.
What you can do after
Apply it via SAFe planning to divide FinTech work into timeboxed increments, sprints, epics, and user stories.

Read how Build Financial Software with Generative AI (From Scratch) explains agile software development →

Also covered in

What to know first

Related concepts

Questions about agile software development

What is agile software development?

Agile software development is an iterative approach to developing software through incremental delivery, collaboration, feedback, and adaptation to change.

Which Manning books explain agile software development?

Lead Developer Career Guide, Delivering Machine Learning Projects: From design to deployment, Think Like a CTO, Collaborative Software Design: How to facilitate domain modeling decisions and Build Financial Software with Generative AI (From Scratch).

What should I know before learning agile software development?

Manning books that teach agile software development usually introduce waterfall model, communication, feedback and Scrum first.

What is the difference between agile software development and waterfall model?

Agile software development is an iterative approach to developing software through incremental delivery, collaboration, feedback, and adaptation to change. The waterfall model is a development and project-management approach that organizes work into largely sequential phases, with limited iteration between them.

What kinds of agile software development are there?

Kinds of agile software development include Scrum, Kanban and behavior-driven development.

What is agile software development a kind of?

Agile software development is a kind of software development life cycle. The software development life cycle is the organized sequence of activities for planning, creating, testing, delivering, operating, and maintaining software.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.