liveBook · Manning

Program increment

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

A program increment is a fixed SAFe planning and delivery period typically lasting eight to twelve weeks.

A program increment (PI) is a fixed SAFe planning and delivery period lasting 8–12 weeks. It gives teams a shared timebox for organizing work across several development cycles. section 1.3

A PI typically connects planning decisions to implementation through:

  • Four iterations, often called sprints; each sprint commonly lasts two weeks, although teams may choose a different length. section 1.3
  • A product roadmap showing business commitments, expected regulatory changes, and company initiatives. section 1.3
  • Work decomposed from larger epics or initiatives into smaller user stories and tasks. section 1.3

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

How deep it goes
Defines the timebox and relates it to planning inputs and work breakdown, but stops short of detailing the planning session’s execution.
Examples
Uses an ACH project, a yearly product roadmap, and decomposed release or project epics as planning examples.
What it assumes
Assumes only basic familiarity with Agile terminology while defining PIs, sprints, epics, and user stories.
What you can do after
Apply it via SAFe planning by organizing roadmap commitments into epics, user stories, and sprint-sized work.
How it connects
Connects SAFe Agile with sprints, product roadmaps, epics, user stories, and regulatory planning.

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.