Pulse Cycle planning: the quarter, planned together

Watch

You will be able to

• Set how cycles run in your organisation
• Plan a cycle: future sprints, the run-up, the event and the planning whiteboards
• Read the plan at portfolio, product and team level, and fix dependencies early
• Set objectives with business value and hold the confidence vote

Step by step

1. Turn it on, when you are ready Work › Pulse Cycle planning
   It is optional and off until an administrator turns it on. Nothing else depends on it.
2. Set how cycles run Work › Pulse Cycle planning › How cycles run here
   Sprints in a cycle (six by default), their length, whether the last is for planning and improvement, the event length (two days by default) and the weeks of run-up. An administrator sets these.
3. Plan a cycle Work › Pulse Cycle planning › Plan a Pulse Cycle
   Choose the organisation or portfolio and the first sprint’s start. DelPulse creates every team’s future sprints, schedules the run-up and the event for the right roles, and opens a planning whiteboard for each product.
4. Review the forecast Cycle › Run-up and event › Prepared for you
   DelPulse has already placed carry-over, work in progress, roadmap dates, project handovers, network roadmap items and the top of the Product Kanban, each with a reason and a confidence. Accept, move or dismiss each; a refresh never overrides your decision.
5. Work through the run-up Cycle › Run-up and event
   Priorities, feature readiness, capacity, early dependency mapping, then the readiness review. The checks show what is still missing.
6. Plan features into sprints Cycle › Product
   Each product’s breakout: its teams by sprint. Plan features into a sprint and team; red cells mean more is planned than the team usually finishes.
7. Read the plan at every level Cycle › Portfolio and Teams
   Portfolio: every product’s features by sprint and the epics they serve. Teams: load against usual pace and the people allocated.
8. Fix dependencies before they bite Cycle › Dependencies
   The map, the register, and order problems: work planned before the work it waits on.
9. Run the event from the planning deck Cycle › Planning deck
   Prepared from your template and filled live: agenda, people, last cycle’s results, product one-pagers, the forecast, capacity and dependencies. Replace the prompts, present it full screen, and update the day 2 slides on the day. It is kept with the record when the plan is committed.
10. Objectives and the vote Cycle › Objectives and vote
    Teams write objectives; the Product Manager sets business value; everyone votes 1 to 5. Commit the plan when confidence averages 3 or more.

Try it yourself

Practise as Hannah Lee in the demo.
View as Hannah Lee. Open Pulse Cycle 5. Which predictions came from projects and the network roadmap, which would you accept or dismiss, and which readiness checks are still open?

Open the demo as Hannah Lee Password pulse-demo-2026. The demo resets every night.

The examples use a made-up healthcare organisation. DelPulse is not only for healthcare: it can be set up for any industry, with your own names for every portfolio, programme, product and team.

Part of

Delivery team members · Product Managers and Product Owners · SROs and Executive Sponsors · PMO and assurance