SSWConsulting / SSWConsulting/SSW.Rewards.Mobile

SSW.Rewards: Sprint 28 review

Open
#986 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: @adamcogan, @sethdaily
Cc: @matt-goldman, @zacharykeeping, @tkapa
(Checked by Seth and Tylah)

Hi Adam,

Here are the Sprint Goals and their status at a glance:
- ✅ Done - Get Google Forms integration working
- ✅ Done - Improve QR code scanning
- 🚧 In Progress - Improve speed of quizzes

Sprint in Review: 28
Sprint Duration: 2 weeks
Project: SSW.Rewards
Project Portal: https://github.com/orgs/SSWConsulting/projects/7/views/1
GitHub SSW.Rewards Portal: https://github.com/SSWConsulting/SSW.Rewards.Mobile/issues (All other PBIs + Source Code)
Product Owner: Adam Cogan (with Seth Daily)
Scrum Master: Zach Keeping

Attendees: Seth, Tylah, Zach, Gert

Sprint PBIs:

Image

https://github.com/orgs/SSWConsulting/projects/7/views/2

PBIs in Sprint: 15
Done PBIs: 12

Application Health Overview (for the entire Sprint)

Image

Figure: https://portal.azure.com/#@sswcom.onmicrosoft.com/resource/subscriptions/b8b18dcf-d83b-47e2-9886-00c2e983629e/resourceGroups/SSW.Rewards.Prod/providers/Microsoft.Insights/components/ai-sswrewards-prod/overview

Application Health - iOS

Image

Figure: App Center Diagnostics for iOS App https://appcenter.ms/orgs/SSW.MobileApps/apps/RewardsMAUI-3/crashes/errors

Application Health - Android

Image

Figure: App Center Diagnostics for Android App https://appcenter.ms/orgs/SSW.MobileApps/apps/RewardsMAUI-3/crashes/errors

Application Engagement - iOS

Image

Figure: App Center Analytics for iOS App https://appcenter.ms/orgs/SSW.MobileApps/apps/RewardsMAUI-3/analytics/overview

Application Engagement - Android

Image

Figure: App Center Analytics for Android App https://appcenter.ms/orgs/SSW.MobileApps/apps/RewardsMAUI-3/analytics/overview

Number of Deployments

  • Beta/TestFlight: 1
  • Promotions to Production: 0
  • Admin Portal: 0

R&D

Sprint Retrospective

As part of our commitment to inspect and adapt as a team we conduct a Sprint Retrospective at the end of every Sprint. Here are the results of our Sprint Retrospective:

✅ What went well?

  • Landon and Gert - Easy to use sheet to add forms
  • Landon and Gert - It's all come together quickly
  • Thankfully most already done by Goldie
  • Quick turnaround on templates from Betty
  • Lots of little bugfixes
  • The workload has been pretty easy
  • QR code scanning issues should be resolved

❌ What didn’t go so well?

  • Scrum - didn't do 1 week Sprints
  • Tylah unavailable for most of last week
  • Landon says marketing form needs to be split into smaller forms
  • Quizzes - Updating model to GPT-4o lead to issues

What improvements will be made for the next Sprint?

  • Will do proper Scrum

<This is as per the rule: https://rules.ssw.com.au/do-you-create-a-sprint-review-retro-email >

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

Start by reviewing the sprint PBIs and project portal linked in the issue, along with the recorded health, deployment, and retrospective sections. The issue does not identify a file, test, or concrete change; its purpose is to document Sprint 28 rather than define work for a contributor.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, azure, ios
Domain
documentation, mobile
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.