SSWConsulting / SSWConsulting/SSW.Rewards.Mobile

SSW.Rewards: Sprint 22 Forecast

Open
#803 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: @sethdaily
Cc: @zacharykeeping, @AntPolkanov, @adamcogan

(Checked by Zach, Anton)

Hi Seth,

We tried to call you, but couldn't get in touch.

Sprint Goals (in priority order):

  • 🐛 Bug Squashing (Auth, tech debt etc.)
  • 💄 Activity 2024 Page

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

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

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

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

The issue is a Sprint 22 forecast and points to the SSW.Rewards project board and sprint-forecast rule; it names no repository files, tests, or code entry points. Start by reviewing the linked project board and rule, but the issue does not define a concrete change or a verifiable done condition.

Written by the indexing model from the issue text.

Assessment

Domain
content, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
10/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.