SSWConsulting / SSWConsulting/SSW.Rewards.Mobile

SSW.Rewards: Sprint 23 Forecast

Open
#833 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: Matt G., Zach, Anton

(Checked by Matt)

Hi Adam,

Sprint Goals (in priority order):
- ⌛️ Check-in with the Auth Bug
- 📣 Complete Push-Notifications feature

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

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

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

This issue is a sprint forecast rather than an implementation task. Review the linked SSW.Rewards project board and the sprint forecast rule first, then compare the listed sprint goals with the Sprint 23 backlog. It is complete when the forecast has served its planning purpose and the sprint scope is recorded in the project tracking system.

Written by the indexing model from the issue text.

Assessment

Domain
mobile-dev
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.