Development Workflow

InfoWarningTip

This is the most important development workflow that you need to follow during your course with us as a Developer or an Engineer. Any role needs to follow these workflows. Some things are role-specific which are defined later in this guide.

Setup your

Workstation Setup⁠

⁠

There are daily standup (10:30 AM IST) & wrapup (7:30 PM IST) meetings that needs to be attended. If you are not invited please talk with your @Shriya to invite you into them.

Standup meeting is to discuss what are your tasks and goals for today. You’re free to discuss your tasks and queries for the assigned tasks.

Wrapup meeting is to discuss the status of the tasks which has been assigned to you during the Standup meeting. You’re free to discuss the progress or issue faced while performing these tasks. If there are some task that is left, will later be picked on the next day’s standup meeting.

Each task that assigned to you will live inside Linear (our PMS). All your daily task can either be found on project-wise or under the on-going Weekly Cycle. We follow a modified version of Agile.

<aside> 💡 To understand our Agile methodology, please feel free to give it a read from Agile Methodology Document

</aside>

<aside> 💡 To understand how our PMS ie.. Linear works & it’s feature please read our guide on Linear - Project Management Tool.

</aside>

Some points to know:

Each project will be on Linear

Each project will have it’s own channel inside Slack. All project-wise linear tasks, github requests or important client discussions will be there.

Each project will have it’s repository on Github under Deliverable’s Organisation Profile (unless or until you are not working for client directly)

Each project will have two main branches:

Master: For production environment only

Develop: For staging environment only

Both production & staging are auto-deployed on their respective environments. No developer can directly push their code into these branches. Each developer has to cut their feature or bug branch and raise PR for the merge. To know more please understand how Centralised Git Workflow works under

Git Development Workflow⁠

⁠

Each PR will have Linear ticket ID linked with them for auto-tracking.

Each developer will create their new branch from develop based upon their task. The branch name has to follow standards mentioned inside

Git Development Workflow⁠

⁠

Once the work of the task is done, you need to test it and get screenshots or a demo video of the task.

You’ll then raise PR for develop and mention Linear Ticket ID, your senior merge approval, your tasks screenshots or demo video into the PR.

Once approved & merged by the senior the code will be merged to develop.

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.