Nailing Q3 Together - Process Document
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
Core - This includes common items on the platform, design, implementation, and process level
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.
Please find the OKRs here for reference.
Urban Mission
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”?
@Jojo Mehra will share more details on this
(3) How much can we work on?
Estimating Efforts Required
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 | Open Questions/ Comments | Participants |
---|---|---|---|---|
Sep 6, 2021 | 1 | (1) Defining “what” we want/should be working on? Group Session Huddle quick and breakout into groups to identify core items Independent Product-specific items in Confluence pages PT W&S TL mCollect Fire NOC HRMS WhatsApp mGramSeva Output - Confluence Document |
| Product |
Sep 7, 2021 | 2 | Group Session Resolve open questions, agree on core and product specific items Output - Confluence Document |
| Product |
Sep 7, 2021 | 3 | Group Session Product <> Program Output - Confluence Document |
| Product <> Program |
Sep 8, 2021 | 4 | Group SessionProduct <> Engineering Output - Confluence Document |
| Product <> Engineering and Platform |
Sep 8, 2021 | 5 | How do we prioritize to cut down and focus on the most important “whats”? How much can we work on? Group Session Prioritization Huddle Independent Bandwidth estimation and nailing “what” Output - Confluence Document |
| Product |
Sep 9, 2021 | 6 | Jira Alignment Product team moves all work items, engg and non-engg, on JIRA Output - Jira Backlog |
| Product |
Sep 14, 2021 | 7 | Jira Progress Roadmaps and Dashboards Output - Jira Roadmap and Product Page |
| Product |
Sep 16, 2021 | 8 | We’re in alignment on what to do, how to do it, how to present progress and blockers |
| Product <> Platform/ Engineering <> Program |