Sept 6, 2021 - Session 1
- Hena Shah
- Harishikesh Anand
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 |
|---|---|---|---|---|---|
Β | Β | 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 |
| Β | Β |
Β | Β | 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) |
|---|---|---|---|
Β | 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 |
|---|---|---|---|---|---|
Β | Β | Β | Β | Β | Β |