Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Objective 🎯

Taking control of what we focus on, how we deliver, and bringing overall transparency to the organization

What needs to be done❓

(1) Defining “what” we want/should be working on? 🧱

We’re looking at 2 broad categories of items

  1. Core - This includes common items on the platform, design, implementation, and process level

  2. Product Specific

In this step, we focus on identifying, refining, aligning each other on the specifics. Ideally, all these items would map to our Mission OKRs.

Info

Please find the OKRs here for reference.

Urban Mission

  1. Punjab Account

  2. Uttarakhand Account

  3. e-Chhawani Account

  4. Odisha Account

Public Finance Management Mission?

Sanitation Mission

Please

...

also see
- The respective Product Completion roadmaps that you all created
- Items for your products in the Product Roadmap

Note: We will also look at streamlining Engineering <> Product <> Implementation/Partnership so that we can keep the firebox items in check (items coming up all of a sudden because of a critical issue in a particular account) and we can ensure what we’re building is going to be used #Adoption

(2) How do we prioritize to cut down and focus on the most important “whats”? 🔪

Note

Jojo Mehra will share more details on this

(3) How much can we work on? 👨‍💻👩‍💻

Estimating Efforts Required

Info
  • Small (S): 1-2 weeks

    • Doable within one product (and/or one engineering sprint) 1-2 weeks

  • Medium (M): 2-3 weeks

  • Large (L): 1 month

Estimating Bandwidth

  • How much can we individually take per month?

This will require us to have a rough idea about where our time is consumed on a regular basis.

(4) How can we share our focus and progress with others? 📊

Once we have alignment on what we will be working on, we will start tracking it on JIRA.

All the reporting will happen through Jira dashboards. This is going to be a tough road, but we need this for ourselves more than anyone else! #JIRATheHellOut 😈

Next Steps

Date

Sr.

Agenda and Outputs

Session and Participants

Open Questions/ Comments

Participants

1

(1) Defining “what” we want/should be working on?🧱

  •  
    Status
    colourBlue
    titleGroup Session
    Huddle quick and breakout into groups to identify core items
  •  
    Status
    colourYellow
    titleIndependent
List and scope our product
  • Product-specific items in Confluence pages
    •  PT
    •  W&S
    •  TL
    •  mCollect
    •  Fire NOC
    •  HRMS
    •  WhatsApp
    •  mGramSeva

Output - Confluence Document

Product

- Breakout Session

2

  •  
    Status
    colourBlue
    titleGroup Session
    Resolve open questions, agree on core and product specific items

Output - Confluence Document

Product

3

  •  
    Status
    colourBlue
    titleGroup Session
    Product <> Program

Output - Confluence Document

Product <> Program

4

  •  
    Status
    colourBlue
    titleGroup Session
    Product <> Engineering

Output - Confluence Document

Product <> Engineering and Platform

5

How do we prioritize to cut down and focus on the most important “whats”? 🔪

How much can we work on? 👨‍💻👩‍💻

  •  
    Status
    colourBlue
    titleGroup Session
    Prioritization Huddle
  •  
    Status
    colourYellow
    titleIndependent
    Bandwidth estimation and nailing “what”

Output - Confluence Document

Product

6

Jira Alignment

  •  Jira Guidelines and Huddle

Product

Team starts getting

team moves all work items, engg and non-engg, on JIRA

Output - Jira Backlog

Product

7

Jira Progress Roadmaps and Dashboards

  •  Jira Guidelines and Huddle

Output - Jira Roadmap and Product Page

Product

8

We’re in alignment on what to do, how to do it, how to present progress and blockers

Product <> Platform/ Engineering <> Program