Software development and management best practices

agile-best-practices.md

Scrum

• BAU projects
• 2 weeks sprints with exceptions at times.
• First day of sprint should be backlog grooming and sprint planning sessionn.
• DSM (Daily Stand-up meetings) should be conducted with precise answers to below questions
  • What did you do yesterday?
  • What will you do today?
  • What is blocking your progress?
• Last day of sprint should be a review of sprint with retrospection session.
• Last day of project sprint should be a post mortem of the project with retrospection session. Created epics with stories having tasks to deliver MVP and achieve milestones in a sprint.

Kanban

• Tech Debts and engineering projects

security-best-practices.md

Securing Application

An application needs to be secure for an user to freely use it without any worry and for the application owners to avoid legal issues by preventing the following

• Data exploitation
• Malicious document risk by validating documents being uploaded to the server
• Payment tampering by validating the payments with the payment providers & gateway
• Project dependencies vulnerabilities by updating to stable and secured versions of it or finding an alternates
• DDOS / DOS attack
• CSRF

by

• implementing authentication for relevant server requests
• implementing authorisation for relevant server requests
• fixing SQL injections
• prevent XSS injections
• maintaing private documents with secured access to authenticated and authorised users

software-maintenance-best-practice.md

Regular updates

Why to regularly update?

• Prevent breaking change
• Prevent depreciation
• Prevent losing LTS support
• Ability to use advance features

Keep updating your tech stack to the latest major version and having LTS version without any breaking change.

What to update?

• OS of the server
• Server packages if any
• Web Server if applicable
• Applications whose process is running on the server
• Project dependencies of the application's repository