[DevPlan]

[incr3m]

Feature Name

11

Module

11

Projects

11

Goal

...

Functional

1.
2.
3.
...

Non-functional

1.
...

Dependencies

...

Constraints

...

Success Metrics

...

Tasks

1. sample ticket Test issue #1 #1

embrace-issues/README.md

Lines 9 to 10 in ddf353c

	- [Good first issue](https://github.com/moreton-blue-software/embrace-issues/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22)
	- [Help wanted](https://github.com/moreton-blue-software/embrace-issues/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22)

User Guide

Step by step happy path testing c/o QAs and Devs
...

Technical Guide

- Try to minimize code snippets as those routinely change, focus on core functions AND their workflow logic
- To include at least one sequence diagram or basic flowchart to visually describe flow of data/logic.
...

Design Summary

- Can be as simple as linking Figma Design if applicable or if N/A this can be blank
...

UI/UX

- Can be as simple as linking Figma Design if applicable or if N/A this can be blank
...

Data Model

- This should provide overview of relationship of the data (if applicable i.e. New modules or updates to existing modules that required addition to existing features or revamp of existing features)
...

Strategy

...

Key Test Cases

...

Acceptance Criteria

...