Risk: too much or too little implementation work

Too much implementation work can increase risk if:

- the work is unnecessarily performed on a project that turns out to be unfeasible, or
- the work turns out to be inconsistent with the architectural decisions for the system, or
- the work is "gold plating": implementing features in unnecessarily complex ways, or features that are not needed.

Too little implementation work can increase risk if:

- important features are missed, or
- implementation work is not finished in time to make the window of opportunity.

No files, tests, or entry points are mentioned. Start by reading the repository contents and the surrounding project-management material to determine where this risk belongs. Done is undefined because the issue does not specify a document, template section, or acceptance criteria to change.

Written by the indexing model from the issue text.