dewv / project-management-pomodoro

MIT License

0 stars 1 forks source link

Risk: too much or too little implementation work #11

Open smattingly opened 6 years ago

smattingly commented 6 years ago

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 commented 6 years ago

as of yet there is nothing to worry about here.

smattingly commented 6 years ago

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 commented 6 years ago

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

JStanley19 commented 6 years ago

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

JStanley19 commented 6 years ago

same

JStanley19 commented 6 years ago

Still High (guessing for awhile)

JStanley19 commented 5 years ago

Still at a High Risk