📋Project Management

Sprint Planning Templates

Agile sprint planning, retrospective, and standup templates.

11 snippets included|Free to download|Works with TypeFire for macOS
Download TypeFire for macOS
zpmsp1

Professional Communication

Hi {{cursor}},

I wanted to bring something important to your attention regarding professional communication.

Here are the key details:

- [Detail 1]: [Specific information]
- [Detail 2]: [Specific information]
- [Detail 3]: [Specific information]

Please review the above and let me know if you have any questions or need additional information.

Thank you for your time and attention. I will follow up if I do not hear back by [date].

Best regards
zpmsp2

Quick Reminder

Quick Reminder

Date: {{date}}
Prepared by: {{cursor}}

Summary:
[Brief overview of quick reminder]

Details:
1. [Key point or finding]
2. [Key point or finding]
3. [Key point or finding]

Action Items:
- [Action item 1] - Due: [Date]
- [Action item 2] - Due: [Date]
- [Action item 3] - Due: [Date]

Next Steps:
[Description of what happens next]

Notes:
[Additional context or considerations]
zpmsp3

Comprehensive Confirmation

Hi {{cursor}},

Quick update on comprehensive confirmation:

[Key information]

Let me know if you have any questions.

Best
zpmsp4

Customized Report

Customized Report

Date: {{date}}
Status: [Active/Pending/Complete]
Owner: {{cursor}}

Description:
[Detailed description of customized report]

Key Points:
- [Point 1]
- [Point 2]
- [Point 3]

Timeline:
- Start: [Date]
- Milestone 1: [Date]
- Completion: [Date]

Notes:
[Additional information]
zpmsp5

Template Guide

Hi {{cursor}},

I am writing to update you on template guide.

Here are the key details:

- [Detail 1]: [Specific information]
- [Detail 2]: [Specific information]
- [Detail 3]: [Specific information]

Please review the above and let me know if you have any questions or need additional information.

Thank you for your time and attention. I will follow up if I do not hear back by [date].

Best regards
zpmsp6

Basic Brief

Basic Brief

Date: {{date}}
Prepared by: {{cursor}}

Summary:
[Brief overview of basic brief]

Details:
1. [Key point or finding]
2. [Key point or finding]
3. [Key point or finding]

Action Items:
- [Action item 1] - Due: [Date]
- [Action item 2] - Due: [Date]
- [Action item 3] - Due: [Date]

Next Steps:
[Description of what happens next]

Notes:
[Additional context or considerations]
zpmsp7

Advanced Draft

Hi {{cursor}},

Quick update on advanced draft:

[Key information]

Let me know if you have any questions.

Best
zpmsp8

Urgent Format

Urgent Format

Date: {{date}}
Status: [Active/Pending/Complete]
Owner: {{cursor}}

Description:
[Detailed description of urgent format]

Key Points:
- [Point 1]
- [Point 2]
- [Point 3]

Timeline:
- Start: [Date]
- Milestone 1: [Date]
- Completion: [Date]

Notes:
[Additional information]
zpmsp9

Routine Notice

Hi {{cursor}},

Following up on our recent conversation about routine notice.

Here are the key details:

- [Detail 1]: [Specific information]
- [Detail 2]: [Specific information]
- [Detail 3]: [Specific information]

Please review the above and let me know if you have any questions or need additional information.

I look forward to hearing from you. Feel free to reply to this message or schedule a call.

Best regards
zpmsp10

Personalized Message

Personalized Message

Date: {{date}}
Prepared by: {{cursor}}

Summary:
[Brief overview of personalized message]

Details:
1. [Key point or finding]
2. [Key point or finding]
3. [Key point or finding]

Action Items:
- [Action item 1] - Due: [Date]
- [Action item 2] - Due: [Date]
- [Action item 3] - Due: [Date]

Next Steps:
[Description of what happens next]

Notes:
[Additional context or considerations]
zpmsp11

Friendly Request

Hi {{cursor}},

Quick update on friendly request:

[Key information]

Let me know if you have any questions.

Best

When to use this template

Customize for your workflow

Common questions

Should retros be in the standup template too?

Keep them separate. Standups are tactical (what's blocking today); retros are reflective (what should change). Mixing them dilutes both.

How do I keep retros from being whining sessions?

Lock retros to one structural change as the output. Without a 'what we'll try', the same complaints surface every sprint.

Related reading

More Project Management Templates

Use these snippets in TypeFire

Download the template pack, drop the .md files into your TypeFire snippets folder, and start expanding with abbreviations instantly.

Get TypeFire Free