Skip Ahead to: 1Overview 2Splitting the Program into Child Projects 3Dividing the Increment into Releases 4Tracing One Epic Across Teams 5What to Check Before You Commit Overview This article walks through one program end to end, so the ideas in How to Run PI Planning in NimbleWork have something concrete behind them. Member Health Platform […]

Skip Ahead to: 1Overview 2Understanding PI Planning 3PI Planning vs. Release Planning vs. Sprint Planning 4How to Run PI Planning in NimbleWork Overview PI Planning is how several teams agree what they will deliver together over the next increment, and how they surface the dependencies between them before the work starts. NimbleWork has no menu […]

Skip Ahead to: 1Overview 2Navigation 3How to Plan a Sprint Across the Program? 4Layout of the Program Sprint Planning Board 5Rules You Should Know Overview Sprint Planning brings the team together to decide what work a sprint will deliver. On a single project you plan one backlog into a row of sprint columns, as How […]

Skip Ahead to: 1Overview 2Navigation 3How to Plan a Release Across the Program? 4Layout of the Program Release Planning Board 5Rules You Should Know 6What Is Different at the Program Level Overview Release Planning at the program level works like the board you already use on a single project. The difference is its reach. One […]

Skip Ahead to: Overview Navigation How to Set Up a Program Project? Layout of the Child Projects Tab Rules You Should Know Overview When several teams work towards one goal, each team plans well on its own and the whole still drifts. Dependencies surface late, two teams discover they need the same backend service in […]