SDLC model git issue with a meaningful title

[omindu]

A well described description should be added here explaining what problem or use case we are trying to address. Following should be included in the description.

• Attach ideation/user stories doc to the description
• High level estimation (Estimation - Budgeted) - This should be added by the EM of the respective task at the planning phase.
• Detailed estimation (Estimation - Definitive) - This is should be added by Technical Owner after detailed planning and should be updated at each effort revision

Sample effort estimation template

::Estimation - Budgeted:: #Added during the initial planning Effort BE::25 Effort FE::10 Effort SRE::5 Effort QA::5 Effort Docs::5

::Estimation - Definitive:: #Added during detailed planning and updated at effort revisions Effort BE::19 Effort FE::13 Effort SRE::3 Effort QA::3 Effort Docs::3

[omindu]

Detail task break down should be added as a comment and should be linked to the feature gantt chart

Task	Type	Effort
Requirement gathering, User stories	BE	3
Define architecture	BE	2
Design and mockups	FE	3
Threat Model	BE	3
Backend implementation	BE	5
UI implementation	FE	5
Deployment artifacts creation	SRE	3
Unit tests	BE/FE	2
E2E tests	BE/FE	2
Feature effort	QA	3
Content	Doc	3

[omindu]

Effort revisions should be interacted as below. The issue description should be updated with new definitive estimation

::Effort Revision:: Reason:: Revised effort after detailed task breakdown Effort BE:: -8 Effort FE:: +2 Effort SRE:: -2 Effort QA:: -2 Effort Docs:: -2

[omindu]

::Effort Revision:: Reason:: Addressing review feedback Effort BE:: +2 Effort FE:: +1