New formatting toolbar button
New Try the inline toolbar, (opens new window). Unpin it. Select text to edit. Feedback
/
Workshop for Android Reg Client

This space is created to document the Android Reg Client Workshop.


Itinerary:


Day #

Things to discuss

Action Items

Day #1:

(12:00-4:00; Monday-4th September)

  1. Present the entire feature list- 20min

  2. Discuss the feature flow (any deviation from existing Reg Client?)- 20min

    1. New Registration

    2. Update

    3. Lost

    4. Operator onboarding

  1. New feature ideas:- 60 min

    1. From resident’s perspective- 20min

    2. From Operator/Supervisor perspective- 20min

    3. From country’s perspective?- 20min

  2. Strategy for documentation (docs/sub domain of docs)

  1. Mind map

  2. Make a flow chart diagram for each feature

Day #2:

(12:00-4:00; Wednesday-11th October)



  1. Status update for P1

    1. Feature-18th August

    2. Release was postponed based on workshop on 4th September to include a few basic features

  2. Align on approach (scope for P1 release)

    1. features to be included for P1 release

    2. With and without the new features-come up with estimates + bug

    3. QA tested vs QA certified?


  4. Discuss feature list from last workshop + enhancements to the feature list (P2, P3,….)- (sticky notes)

  1. Relook at P2, P3,… and the timelines for phases - any specific month/quarter?

Another session

  1. Create stories: Present the list the old + new features - 10min

  2. Timelines/estimates for the above stories

    1. Divide features in Phases (Phase I, Phase II…etc. )-30min

    2. Prioritise the features within each phase-30min

    3. Community contribution features-15min

  1. Technical evaluation -60min

    1. Technical feasibility check

    2. Technical Design discussion

    3. Technical NFRs

      1. Local DB hardening

      2. Logs

      3. Audit

      4. Metrics/ Telemetry

      5. Packet safety on tablet

  2. Community engagement: 20min

    1. Announcement on demos

    2. Announcement on progress

    3. How to contribute- guideline?

    4. Pitch to contribute: Pre-requisites for the same:

      1. Have google form ready

      2. How to make APK readily available

      3. Have a team ready to answer questions

  1. Make list of the old + new features + responses from the Google form

  2. Make a plan for community engagement

  3. Present the current architecture (HLD) and potential change if new features are considered - ​@Hitesh Champalal​

Day #3:

(12:00-1:00; Friday-8th September)

Conclusion

  1. Conclude on the items discussed on day #1 and day #2 of workshop.

  2. Make a list of action items- MSL + Roadmap

  3. Send MoM and document it on confluence