SSWConsulting / SSWConsulting/SSW.Rewards.Mobile

SSW.Rewards: Sprint 21 review

Open
#802 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, Seth)

Hi Seth,

Here are the Sprint Goals and their status at a glance:
- 🚧 In Progress - 🐛 Killing the Auth bug
- ✅ Done - ⭐️ DDD Melbourne
- ❌ Not Done - 💄 Complete Rewards UI 2024

Sprint in Review: 21
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: Tylah Kapa

Attendees: Adam, Seth, Tylah, Zach, Anton

Sprint PBIs:

image

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

PBIs in Sprint: 14
Done PBIs: 9

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

Note: Errors still primarily coming from Bots hitting /

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: 1
  • 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?

(+2/-0) DDD Melbourne went very well!

(+1/-0) App didn't fall apart for DDD

(+1/-0) Good feedback from users; people loved quizzes.

(+1/-0) Squashed some annoying bugs

(+0/-0) Dones - Lots of Dones this Sprint

What could be improved?

(+1/-0) We are quickly accumulating technical debt

(+0/-0) UX - Quizzes | Technical Questions in Quizzes can be annoying to Answer

(+0/-0) UX - Redeeming | Booth Team thought that users had to input Address. Team thought it was QR Codes.

(+0/-0) UX - Mobile Login | Unclear that OAuth could be used

(+0/-0) Difficult to test awarded points for Quizzes, Scanning, Prize Redemption

(+0/-0) Resourcing - Tylah's Last Sprint on Rewards

(+0/-0) We made progress with the Auth bug, but it's still there

(+0/-0) Anton was all alone :( (With Zach at the end)

(+0/-0) JetBrains Rider fails a lot after merging repos

A brilliant idea to share?

(+0/-0) Can we improve the avenue of Feedback from users?

<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

This issue records a Sprint 21 review rather than requesting a specific source or documentation change. Start with the linked project portal, Sprint PBIs, and the referenced health and engagement reports; no files or tests are identified, and completion criteria are not defined.

Written by the indexing model from the issue text.

Assessment

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