---
# System prepended metadata

title: Modus Operandi
tags: [meta]

---

---
tags: meta
---

# Modus Operandi

### Introduction :maple_leaf: 
 

This is for you, if you're contributing or interested in contributing to r/IndiaInvestments communities' new initiatives.

We are trying to streamline our delivery process.

_Agile_ gets bad rep, but when done well, can bring joy for all stakeholders.

The alternatives to agile processes are much worse. Agile's not perfect, but it's the only viable model we have.

We can certainly borrow some ideas that have helped workforces around the world consistently ship high quality solutions for end-users.

### New Mode of Operation :bow_and_arrow: 

- We have _sprints_, lasting no more than a week (Monday-Sunday)
- Sprint has _deliverables_. 
- Anyone can commit to a task or two in a sprint, and deliver on those.

  Tasks can be picked from _backlog_. New task created, can go in _backlog_.
- Every task needs a _done criteria_. 

  For most tasks that are about adding or improving content, _done criteria_ is getting that content shipped to end-user. Otherwise, that'd remain _in progress_, and spill over into next sprint.
  
- Before beginning of a new sprint, say on the day new sprint starts, a _backlog grooming_ takes place, where core team & contributors go over the projects / tasks in backlog, as well as any urgent requirements - to decide what next sprint should look like.

- End of every sprint, we showcase what all we've delivered that sprint, and celebrate our sucess.

- Ideally, it's better to under-commit and over-deliver.

  If you're not sure, just pick a single FAQ item, work on that, get it reviewed & merged, then review how it looks on website & discord. That's when it can be moved to _done_.

### Where is the task board? :clipboard: 

We don't want use something as batteries-included as Jira. At the same time, GitHub projects cards are woefully inadequate, one cannot even tag / assign to any project member.

For the time being, core team would maintain the task board themselves on a Trello board. Updating Trello boards, adding details of progress made etc. are the responsibility of the core team.

As a contributor, you just focus on the work, and we are here to help you. **You do NOT need to add or update any tickets**.

[This is our public Trello board](https://trello.com/b/NPlSa3C7/agile-sprint-board)


### Concerns & Epilogue :butterfly: 

Agile can be good at certain aspects, such as maintaining good steady velocity of delivery.

But it can also inculcate short-term thinking.

We'd need long-term thinking to complement this process. Projects would be broken down into sprints, and estimated with sprint as a unit of time.

[T-shirt sizing](https://www.sitepoint.com/3-powerful-estimation-techniques-for-agile-teams/) can be used for that.

We'd closely monitor and periodically evaluate how this has been shaping up, and if we are matching our expectations.