Skip to content

Instantly share code, notes, and snippets.

@fidenz-chim

fidenz-chim/RadicalLedger_DevProcess.md

Last active August 5, 2020 07:36
Show Gist options
  • Save fidenz-chim/c361b9d4f145c6a7c1770dcfffe18036 to your computer and use it in GitHub Desktop.
Save fidenz-chim/c361b9d4f145c6a7c1770dcfffe18036 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
RadicalLedger_DevProcess.md

Radical Ledger Development/Delivery Process#

This is a guideline on how to engage with software development of process of Radical Ledger for Radical Ledger direct staff. Refer the Opensource Contribution Guideline (Yet to be published) if you are a external collaborator to any of our projects.

Project Management Process

JIRA is the project management tool of choice and it could be access via radicalledger.atlassian.net. Currently there are two separate agile boards to manage developments and operations respectively.

  • Development Tasks Board

  • Operational Task Board

  • Developers must work on tasks which are in the backlog. It does not guarantee, the backlog tasks are defined in away that, those could progress as features. So it is developers responsibility to create managable sub tasks or new tasks that could map to features.

  • Before a developers start development of a task (feature) it is required to estimate the task. It is recommended to have tasks with required effort less than four(4) hours.

  • At the completion of each tasks, developer should log the actual time taken for each task with sufficient description about what work has been carried out.

  • It is understood that estmates could be wrong (actual hours could be less or more), but it is necessary to justify any differences (between estimatec and actual) when log time agains the task.

  • At any given moment, status of the repository should match with the comments available in JIRA (or in other words, status of the repository should be able to understand reading the commnets in JIRA. This could use as a tool to self check a devlopers compliance with the process.

  • It is important to log time daily for tasks developers worked on. Time logs should have sifficient details to identify what actual work carried out by developers. To explains the work carried out, developers could use task comments. Again it is important to provide sufficient details to understand the actual work carried out.

Software Development Process

  • Developments are carried out based on GitHub repositories and it is required to follow the GitFlow in a precise manner.
  • It is required to push the code to remote repository at least two(2) times a day. When you push, you would be pushing the code to a feature branch, so it is not necessary for the code to work at any given push.
  • Whenever feature development is completed, tested and merged to parent branch, feature branch should be deleted to have a clean source tree.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment