liveBook · Manning

Sprint

As explained in Build Financial Software with Generative AI (From Scratch)

A sprint is a short, fixed development iteration in which a team works on a selected set of software objectives.

A sprint is a short, fixed development iteration in which a team completes selected software objectives. It typically lasts two weeks, though teams may choose a different duration. section 1.3

Sprints organize larger business commitments into manageable development cycles:

  • PI planning schedules work across a Program Increment, typically 8–12 weeks and commonly divided into four sprints. section 1.3
  • Roadmap commitments, regulatory changes, and company initiatives are broken into epics, then into user stories for sprint planning. section 1.3
  • Teams use short cycles to keep large FinTech development efforts manageable, even when terminology differs between organizations. section 1.3

How Build Financial Software with Generative AI (From Scratch) covers it

How deep it goes
Defines sprint timing and relationships to Program Increments, epics, and user stories without detailing ceremonies or execution practices.
Examples
Uses a FinTech ACH project, roadmap commitments, regulatory changes, and company initiatives as surrounding planning examples.
What you can do after
Apply it via short development cycles that divide larger software initiatives into manageable work.
How it connects
Connects sprints to SAFe Agile, Scrum, Program Increments, PI planning, product roadmaps, epics, and user stories.

Also explained in

Compare how 3 books explain sprint →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build Financial Software with Generative AI (From Scratch). The section links point to the parts of the book it draws on.