Cheat sheet

This page describes the main steps of a program increment planning and delivery.

Plan

Use the plan view in Ativo to facilitate the Program Increment planning.

Activity	Ativo Admin	Team Member	Scrum Master	Product Owner	Program Manager	Product Manager
Create sprints			X
Configure Period (Program Increment)	X
Create & prioritize features				X		X
Include features in scope				X		X
Define Milestones					X	X
Create & plan stories according to capacity		X	X	X
Review cross team dependencies, replan.		X	X	X
Raise and review risks & impediments		X	X	X	X	X
Define, review & score objectives		X	X	X	X	X

Progress & replan

Use the progress views in Ativo to facilitate the Art Sync and scrum of scrum meetings.

Activity	Ativo Admin	Team member	Scrum Master	Product Owner	Program Manager	Product Manager
Deliver work and close stories		X
Close sprints (team level), replan stories.		X	X	X
Close sprints (program level)	X
Update & review risks & impediments		X	X	X	X	X
Review cross team dependencies, re-plan		X	X	X
Decide and communicate on priorities				X	X	X
De-scope / add features				X	X	X
Score objectives : delivered value				X	X	X

Quick Tips

Show less stories on the board

• Use Filters > Team filter with Add linked Issues to only show the issues from your team, together with the links with other teams.

• Use View options > Issues > Cross-team dependencies to only show issues that have cross team dependencies

• Use Filters > Issue type to only see the planning of epics (features)

• Use Filters > RAG > Amber & Red (do not select ‘add linked issues’) to only see the issues that have red and amber indicators.

Use the View options > Cords to hide cords on the board.

Cord colors

• ⬤ Red cord color = needs to replan to respect dependency (negative ‘slack’).

• ⬤ Amber cord color = needs attention as prerequisite and the issue itself are planned in the same sprint (‘slack’ = 0, this is on a critical path)

• ⬤ Purple cord color = timing of dependency is OK (positive ‘slack’)

Handle delays & re-planning

Unfinished stories in a sprint should be re-planned in another sprint.

Unfinished epics (features) should not be replanned. Ativo will detect if underlying issues are planned in later sprints than the feature itself was originally planned, and show this in the progress view.

Epics (features) added or removed from the PI can be tagged with ‘added/removed’ commitment levels. Use Filters > Commitment level (select ‘Add linked issues’) to switch between original planning and planning with added/removed features.

Filter

Note: filters affect all sections of the board, including the risks & impediments and the burn-up chart.