SSWConsulting / SSWConsulting/SSW.Rewards.Mobile

SSW.Rewards: Sprint 39 Forecast

Open
#1,192 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

scrum
Dominant language
C#
Stars
37
Forks
11
PR merge metrics
No merged PRs in 30d

Description

To: Adam, Seth
Cc: Vlad, JK Zach, Anton

(Checked by Vlad and JK)

Hi Adam,

Sprint Goals (in priority order):

🐛 NDC - Login process causing friction

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

Next Sprint: 39
Sprint Duration: 1 week
Project: SSW.Rewards
Project Portal: https://github.com/orgs/SSWConsulting/projects/7/views/1
Product Owner: Seth Daily (was Adam Cogan
Sprint Review Meeting: 30 Jan 2205

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.

🐛 NDC - Login process causing friction
🛠️🔥Admin Portal - Deployments are broken
✨ Improve Prize Drawing Logic in Admin Portal
🐛 Fix QR Code Scanning Issue in ⭐ Rewards (Mobile app)
🐛 Mobile App - Incorrect Profile Pictures
🐛 GPT Quiz | Servers down

https://github.com/orgs/SSWConsulting/projects/7/views/15?filterQuery=sprint:@next

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

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.

Research direction

This issue records the Sprint 39 forecast and links the planned backlog items, but it does not identify an implementation task or a file to change. Review the linked issues and the sprint project view first; there is no clear completion condition for work on this issue itself.

Written by the indexing model from the issue text.

Assessment

Domain
release
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.