Sept 6, 2021 - Session 1

Defining “what” we want/should be working on?

Comments from @Jojo Mehra to note:

Core

We will huddle in groups and populate our collective items on this confluence document.

  • Platform – @P. Sankar @Satish N

    • Data – @Vidya @Harishikesh Anand

    • Privacy and Security

    • Performance

    • Others

  • Design – @Antriksh Kumar @Jojo Mehra @Chandra Kiran (Unlicensed) @Andrew Jones

  • Process – @P. Sankar @Jojo Mehra @Hena Shah @Harishikesh Anand@Vibhor Dubey @Anjoo Narayan

    • Meetings and Reporting

    • Cross-functional collaboration

    • Enablement and Evangelization

  • Others

Anyone can join in any of the breakout sessions to listen in and learn

 

Product Team Items (WIP)

Linked OKR

Link to PR

Item

Description

Priority

Effort

Linked OKR

Link to PR

Item

Description

Priority

Effort

 

 

Design Adoption for new UX

Implementations are on different versions so we do not have a clear view on who will be the taker for new UX

 

 

 

 

Design Retrospective for PT, PGR new UX

  • Comparison of features (Old UX vs New UX)

    • What is picked up/left out ?

      • Why feature was left out ?

      • Step/Plan (To bring missing components in the new UI)?

 

 

 

 

Design Product Completeness of new UI/UX as compared to old DIGIT UI

(TL, PGR timeline feature, PT Assessment Features etc)

 

 

 

 

Design New UI Documentation

Module-wise availability screens, features and functionalities

 

 

 

 

Design Best practices / process of upgrading from old UI to new UI

 

 

 

 

 

Design Guidelines on customising in new UI - benefits over old UI

 

 

 

 

 

PRocess Transparency about customization on implementation side

 

 

 

 

 

PRocess Upgrading the version (in case of implementation partner)

Change management; We do not know which instance to change the feature when States request for a change

 

 

 

 

PRocess Version control management

 

 

 

 

 

PRocessJoint planning; More robust planning and time management

 

 

 

 

 

PRocess Product <> Implementation

More visibility of ground feedback and changes

 

 

 

 

PRocess Product <> Program

More visibility to what’s happening for delivery

 

 

 

Program Team Items

Linked OKR

Item

Description (Why? What?)

Current Status and Details (PM Input)

Linked OKR

Item

Description (Why? What?)

Current Status and Details (PM Input)

 

Product Specific Improvements in Reporting framework performance specific to PT / W&S

 

PT

W&S

 

Core Ability to customise reports easily (e.g. MDMS based solution)

We need more details for this from Program team

 

 

Core Process document on implementing Telemetry

What is expectation from the telemetry process documentation ?

Need to check with engineering team on whether the approach document exists for this line item as telemetry is not yet productized.

 

Core Exemplar of telemetry on any of our internal QA / Staging environments to showcase

 

 

 

Core Embedding Telemetry as part of a product release

 

 

 

Core Product Completeness of new UI/UX as compared to old DIGIT UI

(TL, PGR timeline feature, PT Assessment Features etc)

 

 

Core New UI Documentation

Module-wise availability screens, features and functionalities

 

 

Core Best practices / process of upgrading from old UI to new UI

 

 

 

Core Guidelines on customising in new UI - benefits over old UI

 

 

 

? Feedback mechanism

Rating service delivery (e.g. WhatsApp. PGR, PT)

More details from the ground on which products/usecases need rating

 

 

 

 

 

Product Specific

Please make a separate confluence page for your product-specific items. At the end of all our sessions, we will attempt to turn that page into a Jira roadmap page

Please use the below format on your product-specific page.

Linked OKR

eGov Theme

Item

Description

Priority

Effort Estimate

Linked OKR

eGov Theme

Item

Description

Priority

Effort Estimate