Risk: too much or too little implementation work

[smattingly]

11 Issue by smattingly,

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.

[abed12345]

as of yet there is nothing to worry about here.

[smattingly]

I don't have enough information for an informed opinion, but I see a possibility that there might be higher risk here. @abed12345 is already doing a certain amount of coding, and I wonder if some of that might be at risk of inconsistency with the architecture we need. As noted elsewhere, we need to better document our understanding of the design/architecture.

[abed12345]

A lot of the coding i already did may not get used or may need to be changed slightly.

[JStanley19]

REVIEWED. Still high until new MVC design is implemented into architecture.

[JStanley19]

same

[JStanley19]

Still High (guessing for awhile)

[JStanley19]

Still at a High Risk