{"id":24190,"date":"2026-10-04T19:55:17","date_gmt":"2026-10-04T14:25:17","guid":{"rendered":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/?post_type=article&p=24190"},"modified":"2026-10-07T10:32:52","modified_gmt":"2026-10-07T05:02:52","slug":"program-status","status":"publish","type":"article","link":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/article\/program-status\/","title":{"rendered":"How to Monitor Program Progress"},"content":{"rendered":"
\n

Skip Ahead to:<\/p>\n

<\/div>\n\n\n\n\n\n\n\n\n
1<\/span>Overview<\/a><\/td>\n<\/tr>\n
2<\/span>Navigation<\/a><\/td>\n<\/tr>\n
3<\/span>Understand the Release & Sprint Status Views<\/a><\/td>\n<\/tr>\n
4<\/span>Monitor Work Using the Parent-Child Tab<\/a><\/td>\n<\/tr>\n
5<\/span>Monitor Work Using the Releases & Sprints Tab<\/a><\/td>\n<\/tr>\n
6<\/span>Parent-Child vs. Releases & Sprints<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n

Overview<\/h2>\n

Once work is planned across a program, the next question is how it is going. Release & Sprint Status<\/strong> answers that in one screen.<\/p>\n

It reads the whole program at once. Every child project, every release, every sprint and every card sits in one grid, with a progress figure on each row. You do not have to open each project and add the numbers up by hand.<\/p>\n

In fact, the screen holds the same information twice, in two views. One arranges it by parent and child card. The other arranges it by project and release. Which you use depends on the question you are asking.<\/p>\n

\n

!<\/span>This Screen Reports, It Does Not Plan<\/p>\n

\n

Release & Sprint Status reads work that is already planned. To change which release or sprint a card sits in, use Release Planning at the Program Level<\/a> or Sprint Planning at the Program Level<\/a>.<\/p>\n<\/div><\/div>\n

Program Projects and Ordinary Projects<\/h3>\n

Release & Sprint Status is available on every project. The screen and its two tabs are the same in both cases. However, what changes is how much it covers.<\/p>\n

On an ordinary project it reports that project’s own cards. On a Program<\/strong> project it reports the program and every child project linked to it, which makes it cross-project monitoring. Because of that, the Project<\/strong> column on the Parent-Child tab tells you which project each card belongs to, and parent cards can gather children from several projects at once.<\/p>\n

\nThe same screen on an ordinary project<\/summary>\n
\n

On a child project the grid is a flat list of that project’s cards. There are no cross-project parent rows, and the Project column has nothing to distinguish:<\/p>\n

\"Release<\/a> <\/div>\n<\/div>\n<\/details>\n

To set the category, see How to Set Up a Program Project<\/a>.<\/p>\n

Navigation<\/h2>\n

Navigate to the breadcrumb at the top, hover over the program name, expand the Agile Planning<\/strong> module, then select Release & Sprint Status<\/strong>.<\/p>\n

Understand the Release & Sprint Status Views<\/h2>\n

The screen opens with two tabs. However, they show the same cards, arranged differently.<\/p>\n

\"The<\/a> <\/div>\n

Parent-Child<\/h3>\n

Arranges the grid by card relationship. Each parent card is a group row, and the cards that roll up to it sit beneath. So use it to follow a piece of work from the epic downwards.<\/p>\n

Releases & Sprints<\/h3>\n

Arranges the grid by delivery window. Rows group by project, then by release, then by sprint. Use it to follow a release or a sprint across the program.<\/p>\n

How the Two Views Complement Each Other<\/h3>\n

A card belongs to a parent, and it belongs to a release and a sprint. Each view surfaces one of those two and reports the other in a column.<\/p>\n

So Parent-Child answers “is this epic on track, and who is delivering it?” while Releases & Sprints answers “is this release on track, project by project?”<\/p>\n

The Parent Card<\/strong> column is what carries you between them. Spot a card holding a release back, note its parent, then switch to Parent-Child and expand that parent. You will see whether the problem is one card or the whole epic.<\/p>\n

Monitor Work Using the Parent-Child Tab<\/h2>\n
\"The<\/a> <\/div>\n

The Parent-Child View<\/h3>\n

A hierarchical list of the program’s work. Parent cards form the group rows. Expanding one reveals every card that rolls up to it, no matter which project that card lives in.<\/p>\n

Columns on This Tab<\/h3>\n

Every row on the Parent-Child tab carries the same set of columns. Group rows roll the figures up.<\/p>\n

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Column<\/th>\nWhat It Shows<\/th>\n<\/tr>\n<\/thead>\n
ID<\/td>\nThe card ID. Select it to open the card.<\/td>\n<\/tr>\n
Name<\/td>\nThe card name. On a group row, the parent card’s name.<\/td>\n<\/tr>\n
Project<\/td>\nWhich project the card lives in. Parent-Child only.<\/td>\n<\/tr>\n
Percent Complete<\/td>\nProgress, as a colour-coded bar.<\/td>\n<\/tr>\n
Assigned to<\/td>\nWho owns the card.<\/td>\n<\/tr>\n
Release \/ Sprint<\/td>\nWhere the card is scheduled. A dash means it is not scheduled yet. Parent-Child only.<\/td>\n<\/tr>\n
Estimated Points<\/td>\nStory points estimated against the card.<\/td>\n<\/tr>\n
Due Date<\/td>\nWhen the card is due.<\/td>\n<\/tr>\n
Overall Status<\/td>\nThe card’s current status.<\/td>\n<\/tr>\n
Estimated, Actual and Remaining Hours<\/td>\nEffort, taken from the card’s To-dos tab.<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n

Select Filter<\/strong>, at the top right, to narrow the grid by project or by card type<\/a>. Learn more about it here<\/a>.<\/p>\n

You can also perform common operations such as rearranging column fields<\/a> and sorting<\/a>.<\/p>\n

Understand the Workitem Hierarchy<\/h3>\n

Above all, this is the view’s real value on a program. For example, an epic owned by the program can have children sitting in several different child projects. The Project<\/strong> column names the project for each child, so you can see at a glance how many teams a single epic depends on.<\/p>\n

\"One<\/a> <\/div>\n

Select the chevron beside a parent card to expand or collapse it. Select a card ID to open that card.<\/p>\n

Track Workitem Progress<\/h3>\n

Percent Complete<\/strong> shows how far along each card is, as a colour-coded bar.<\/p>\n

On a group row, the figure is the average of its immediate child cards<\/strong>. So an epic at 16% is not 16% of its own work — it is the average across the cards directly beneath it.<\/p>\n

\"Percent<\/a> <\/div>\n

Track Ownership and Assignments<\/h3>\n

Assigned to<\/strong> names the person who owns each card. Scanning this column down an expanded epic tells you who is carrying it, and whether the work sits with one person or is spread across teams.<\/p>\n

Track Releases and Sprints<\/h3>\n

On this tab the Release<\/strong> and Sprint<\/strong> columns report where each card is scheduled. A dash means the card is not yet assigned to one. That is the quickest way to spot work that belongs to an epic but has not been planned into a delivery window.<\/p>\n

Track Effort and Estimates<\/h3>\n

Four columns cover effort: Estimated Points<\/strong>, Estimated Hours<\/strong>, Actual Hours<\/strong> and Remaining Hours<\/strong>.<\/p>\n

\n

i<\/span>Where the Hours Come From<\/p>\n

\n

The hour columns are populated from the To-dos<\/strong> tab of a card. Until to-dos carry values, these columns stay empty.<\/p>\n<\/div><\/div>\n

When to Use the Parent-Child View<\/h3>\n