SSW.Rewards: Sprint 21 Forecast

Open
#769 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
10/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

This issue is a historical sprint forecast and does not identify a source file, test, implementation entry point, or code change. Review the linked project and sprint-forecast rule only if maintaining project records; no completion criteria for a first-time code contribution are provided.

Written by the indexing model from the issue text.

Description

scrum

To: Adam, Seth
Cc: Matt G., Zach, Anton

(Checked by Matt)

Hi Adam,

We tried to call you, but you weren't available.

Sprint Goals (in priority order):

  • 🐛 Killing the Auth bug
  • ⭐️ DDD Melbourne
  • 💄 Complete Rewards UI 2024

Please see below for a more detailed breakdown of the upcoming Sprint:

Note: Team capacity is drastically reduced this Sprint as Matt and Tylah will be on Client work. Anton will be looking after Rewards :)

Sprint Duration: | 2 Weeks
Project: | SSW.Rewards
Project Portal: | https://ssw.visualstudio.com/SSW.Rewards
Product Owner: | Adam Cogan (Seth Daily)
Sprint Review Meeting: | Wed 27th March

As per our Sprint Planning Meeting, and as the Product Owner, you have agreed to the following Product Backlog Items (PBIs) being included in the current sprint backlog.

The Team will do its best to deliver this set of features (Scope), to a defined quality standard (Definition of Done) by the end of the sprint. Ideally the team will deliver what they forecast, or even a bit more, but this can't be guaranteed.

image

<This is as per rule: https://www.ssw.com.au/rules/sprint-forecast />

Dominant language
C#
Stars
37
Forks
11
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SSWConsulting/SSW.Rewards.Mobile

All issues in SSWConsulting/SSW.Rewards.Mobile

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.