Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Rule “sprint-forecast/rule” #9473

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions rules/sprint-forecast/rule.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
seoDescription: Do you create a Sprint Forecast? (aka The functionality that will be developed during the Sprint) - Confirming the relationship between the Product Owner and Development Team in Agile Project Management.
type: rule
title: Do you create a Sprint Forecast? (aka The functionality that will be developed during the Sprint)
title: Do you create a Sprint Forecast? (aka The functionality to be developed in the Sprint)
seoDescription: The functionality that will be developed during the Sprint confirms the relationship between the Product Owner and Development Team in Agile Project Management.
uri: sprint-forecast
authors:
- title: Adam Cogan
Expand Down Expand Up @@ -30,13 +30,13 @@ Each Sprint in a Scrum project can be considered a mini-project that has **time*

::: email-template

| | |
| -------- | --- |
| To: | {{Product Owner}} |
| Subject: | {{Client Name}}: Sprint XXX Forecast |
| | |
| -------- | -------------------------------------- |
| To: | {{ PRODUCT OWNER }} |
| Subject: | {{ CLIENT NAME }}: Sprint XXX Forecast |
::: email-content

### Hi {{Product Owner}}
### Hi {{ PRODUCT OWNER }}

Sprint Goals (in priority order):

Expand Down
Loading