Open and Agile - JIRA Setup v1

Objective

Going from 1 Mission to 4, our work needs restructuring to manage priorities, capacity, timelines, and quality better. With this document, we attempt to put forth a view of organizing the work using JIRA.

Mission Projects

Each Mission becomes a JIRA project, one mission one backlog, with standardized components (Components in JIRA are used to filter the work in the backlog). This will also include non-engineering work that a Mission undertakes.

To start with, we will add non-engineering mission work that the product team is undertaking/participating in.

Core	Urban	Sanitation	iFix
Analytics Revamp Performance Benchmarking GIS Design System Privacy Testing Strategy Documentation (core.digit.org )	Single Instance PT PGR TL OBPAS Fire NOC W&S Documentation (urban.digit.org) National Dashboard	FSM SWM Documentation (dishha.digit.org)	mGramSeva iFix Adaptor iFix Core Documentation (ifix.digit.org)

Standardization

Epics, Stories, Tasks, Bugs

Item	Description
Epic	A large body of work taking more than smaller task to finish. These will include engineering as well as non-engineering large items that we undertake for a Mission.
Stories/ Task	Smaller tasks/requests/requirements/testing/etc required to complete an Epic

Reference

We’re keeping this estimation framework while adding Epics/Stories

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

Open Question: How do we want to roll up Epics to an Initiative level?

Issue Information

Every issue ticket (Epic/Story/Task/Sub-Task/Bug) will have the following details so that we can understand what our work is mapping towards:

Mission
- Core
- Urban
- Sanitation
- PFM
Theme
- Access
- Citizen Adoption
- Enablement
- Privacy and Security
- Quality
- Performance
- Innovation
- User Experience
- Pilot and Roll Out
- Completeness
- None
Type of Work
- Research
- Design
- Development
- Enablement
- GTM and Partnerships
Programs
- CDG
- Punjab
- eChhawani
- Uttarakhand
- Odisha
- None
Issue Description
- Background
- Solution
- Scope
- Actors
- Details
- Validations
- Design
- Notifications
- Acceptance Criteria
  - Functional
  - Non-Functional

Operations

Running operations between Product <> Engineering/Platform <> Programs:

TBD:

Looking to capture required Implementation related information in JIRA

Release feature implementation status
Reference application and platform bug reported during implementation
Feedback

Issue Workflow

Product/Design

Engineering

TBD based on updated Done process

Implementation

TBD

We can set up various workflows depending on the type of work. But for now, this should suffice

Reporting

We will the Dashboards feature of Jira and set up reports for stakeholders. Some Work-In-Progress Sample Reports:

Product Team Q3