The Plus Delta retrospective is one of the simplest and most effective formats for continuous improvement. With just two columns—what worked well (+) and what to change (Δ)—teams can quickly identify wins and improvements without getting bogged down in complex frameworks.

In this guide, you’ll learn how to run a Plus Delta retrospective, when to use it, and how to get the most from this streamlined format.

What Is the Plus Delta Retrospective?

The Plus Delta format uses two simple categories:

• Plus (+): Things that went well and should continue
• Delta (Δ): Things to change or improve

The name comes from mathematics: plus (+) for positive additions, and delta (Δ) for change. It’s a forward-looking format—instead of dwelling on negatives, the delta column focuses on what to do differently.

Why Delta Instead of Minus?

The deliberate choice of “Delta” (change) over “Minus” (negative) shapes the conversation:

Minus Framing	Delta Framing
”What went wrong?"	"What should we change?”
Focuses on past failures	Focuses on future improvement
Can feel like blame	Feels constructive
Lists problems	Lists actions

This subtle linguistic shift makes Plus Delta one of the most psychologically safe retrospective formats. Teams that run regular retrospectives are 24% more productive (State of Agile Report), and a psychologically safe format like Plus Delta helps ensure those retrospectives actually happen.

The Two Categories

Plus (+): What Worked Well

This column captures:

• Successful processes or practices
• Team wins and achievements
• Things that should continue
• Behaviors to reinforce
• Tools or techniques that helped

Example items:

• “Daily standups kept everyone aligned”
• “Code reviews caught bugs early”
• “Great collaboration on the API design”
• “Clear sprint goal helped prioritization”

Delta (Δ): What to Change

This column captures:

• Things to do differently
• Process improvements to try
• New experiments to run
• Behaviors to adjust
• Problems reframed as changes

Example items:

• “Start testing earlier in the sprint”
• “Reduce meeting time on Wednesdays”
• “Add acceptance criteria before sprint starts”
• “Try pair programming for complex features”

💡 Pro tip: Encourage deltas to be phrased as actions, not complaints. “Communication was bad” becomes “Hold brief daily syncs.”

When to Use Plus Delta

Plus Delta works best for:

Quick Reviews

When you’ve limited time (20-30 minutes), Plus Delta’s simplicity keeps the session focused.

Frequent Retrospectives

For weekly or bi-weekly retros, a lightweight format prevents retrospective fatigue.

New Teams

The straightforward structure is easy for retrospective newcomers to understand.

After Meetings or Workshops

Beyond sprints, use Plus Delta for post-meeting feedback—“What worked about this meeting? What should we change?”

Continuous Improvement Culture

Teams practicing continuous improvement benefit from regular, low-ceremony reflection. Companies practicing continuous improvement see 37% lower employee turnover (State of Agile Report), and Plus Delta’s lightweight structure makes it easy to maintain that habit.

When NOT to Use Plus Delta

• After significant failures (need more depth)
• When emotional processing is needed (try Mad Sad Glad)
• For complex issues requiring multiple dimensions
• When the team needs variety after using Plus Delta repeatedly

How to Run a Plus Delta Retrospective

Before the Meeting

1. Schedule 25-40 minutes - Plus Delta is fast
2. Create the board with two columns labeled + and Δ
3. Share the format if team members are new to it
4. Gather context - Sprint goals, metrics, notable events

Step-by-Step Facilitation

Step 1: Set the Stage (3 minutes)

Welcome the team and explain the format:

“Today we’re using Plus Delta. We’ve two columns: Plus for what worked well, and Delta for what we should change. Let’s focus on actions, not blame.”

Read the Prime Directive for psychological safety.

Step 2: Silent Brainstorming (5-7 minutes)

Everyone writes items on sticky notes or cards:

• Encourage multiple items per person
• One idea per card
• Both + and Δ items

Step 3: Share Plus Items (5-8 minutes)

Go around the room (or virtual meeting):

• Each person shares their + items
• Place on the board
• Group similar items
• Brief clarifying questions only

Step 4: Share Delta Items (5-8 minutes)

Same process for delta items:

• Share and place on board
• Group similar items
• Rephrase complaints as changes if needed

Step 5: Discuss and Vote (8-10 minutes)

• Identify patterns or themes
• Vote on most important items (dot voting)
• Discuss top 2-3 items

Step 6: Create Action Items (5 minutes)

For each top delta:

• Define a specific action
• Assign an owner
• Set a deadline or checkpoint

Plus Delta Template

Use this visual template:

┌─────────────────────────┬─────────────────────────┐
│         + (Plus)        │       Δ (Delta)         │
│      What worked?       │    What to change?      │
├─────────────────────────┼─────────────────────────┤
│                         │                         │
│  • Daily standups       │  • Start testing early  │
│                         │                         │
│  • Clear sprint goal    │  • Fewer meetings Wed   │
│                         │                         │
│  • Pair programming     │  • Define acceptance    │
│    on feature X         │    criteria upfront     │
│                         │                         │
│  • Quick bug fixes      │  • Update documentation │
│                         │                         │
│                         │                         │
└─────────────────────────┴─────────────────────────┘

Sample Questions for Plus Delta

Plus (+) Questions

• What went well this sprint?
• What should we keep doing?
• What helped us succeed?
• What are we proud of?
• What processes worked smoothly?
• What should we celebrate?

Delta (Δ) Questions

• What would we do differently next time?
• What experiment should we try?
• What process could we improve?
• What’s one thing we could change?
• What adjustment would make work easier?
• How could we be more effective?

For discussion prompts that pair well with this format, see our retrospective questions guide.

Tips for Facilitating Plus Delta

1. Balance the Columns

If you see many deltas and few plusses (or vice versa), prompt the team:

“I notice we have lots of deltas but few plusses. What went well that we might be overlooking?“

2. Convert Complaints to Actions

When someone adds a complaint as a delta, help rephrase:

• ❌ “Communication was terrible”
• ✅ “Try a brief morning sync for better communication”

3. Celebrate the Plusses

Don’t rush through positive items. Acknowledging wins builds team morale and reinforces good practices.

4. Limit Action Items

Plus Delta is simple—keep actions simple too. 1-3 action items is plenty. Teams with action item follow-through are 31% more likely to report retro satisfaction (Scrum.org survey), so fewer well-executed actions beat a long list that goes ignored.

5. Track Over Time

Keep a record of plusses and deltas across retrospectives. Patterns emerge:

• Recurring plusses = team strengths
• Recurring deltas = systemic issues needing attention

Common Mistakes to Avoid

Skipping the Plus Column

Some teams jump straight to problems. The plus column:

• Builds positive momentum
• Identifies practices to maintain
• Provides psychological safety

Vague Deltas

“Improve communication” isn’t actionable. Push for specifics:

• What kind of communication?
• Between whom?
• What change would help?

Too Many Action Items

Don’t create 10 action items from a simple format. Pick 1-3 high-impact changes.

Using Plus Delta Every Time

Even simple formats get stale. Rotate with other formats like 4Ls or Sailboat.

Plus Delta Variations

Plus Delta Star

Add a third column:

• Plus (+): What worked
• Delta (Δ): What to change
• Star (⭐): What was exceptional

Plus Delta Question

Add reflection questions:

• Plus (+): What worked
• Delta (Δ): What to change
• Question (?): What are we unsure about

Numbered Plus Delta

Prioritize during collection:

• Rate each + item 1-5 for importance
• Rate each Δ item 1-5 for impact
• Discuss highest-rated items first

Plus Delta vs Similar Formats

Plus Delta vs What Went Well

Aspect	Plus Delta	What Went Well
Columns	2 (+, Δ)	2 (WWW, Improve)
Framing	Change-focused	Improvement-focused
Action orientation	High	Medium
Use case	Quick reviews	General retrospectives

Very similar formats—choose based on preference.

Plus Delta vs Start Stop Continue

Aspect	Plus Delta	Start Stop Continue
Columns	2	3
Focus	Change	Actions
Depth	Shallow	Medium
Time	20-30 min	30-45 min

Plus Delta is faster; Start Stop Continue provides more nuance.

Related Retrospective Formats

If you like Plus Delta, try these:

• Start Stop Continue - Three columns for more nuance
• What Went Well - Similar simplicity, different framing
• 4Ls Retrospective - Four dimensions for deeper reflection
• DAKI Retrospective - Four action-oriented categories

See our complete sprint retrospective formats guide for 30+ options.

Frequently Asked Questions

What is the Plus Delta retrospective format?

Plus Delta is a two-column retrospective format where Plus (+) captures what worked well and should continue, and Delta (triangle symbol) captures what the team should change. The name comes from mathematics, and the deliberate use of “delta” (change) instead of “minus” (negative) keeps the conversation constructive and forward-looking rather than blame-oriented.

How long does a Plus Delta retrospective take?

A Plus Delta retrospective typically takes 25 to 40 minutes, making it one of the fastest retrospective formats available. The simple two-column structure eliminates the overhead of complex frameworks while still producing meaningful insights and action items. This makes it ideal for weekly reviews, frequent retrospectives, and time-constrained sessions.

When should you use Plus Delta instead of Start Stop Continue?

Use Plus Delta when you want a faster, simpler session with just two categories instead of three. Plus Delta works best for quick reviews under 30 minutes, frequent weekly or bi-weekly retrospectives, and teams new to retrospectives. Start Stop Continue provides more nuance by separating new actions (Start) from ongoing improvements, making it better for sessions where you have 30 to 45 minutes and want more structured action categories.

How do you write good delta items that are actionable?

Frame delta items as specific changes rather than complaints. Instead of writing “Communication was terrible,” write “Try a brief morning sync to improve communication.” Each delta should describe what to do differently, not just what went wrong. Tools like RetroFlow make it easy to collect and vote on delta items with built-in anonymous brainstorming and dot voting.

Can you track Plus Delta results over time?

Yes, tracking results across retrospectives reveals valuable patterns. Recurring plusses indicate team strengths that should be protected and reinforced, while recurring deltas signal systemic issues that need deeper attention. Keep a simple log of plusses and deltas from each session and review it quarterly to identify long-term trends and measure whether changes are taking hold.

Run This Format Online — Free

RetroFlow includes a Plus Delta template with everything you need:

• Anonymous brainstorming so people speak freely
• Dot voting to find what matters most
• Action item tracking with owners

No signup required. No cost. Ever.

Launch your retro →