Retrospective about exchange-api HOT 6 CLOSED

Mistakes:

• Should give more time on planning/research phase & see how other products are made
• Little more time on sanity, to make sure things are working as expected (like toFixed precision thing)

Took few hours more than deadline & I am bad at estimating
Should research about alternate products & see if my product solves the problem, and api etc don't have demand , like tools used by normal users

from exchange-api.

Codetime metrics:
Active code time: 66% (try increasing this)

1 day metrics(saturday)
active coding: 7 hr (try increasing this)
time in editor: 3 hr (time for thinking, idle etc)
Lines of code added : 2,021
Lines of code deleted : 845

from exchange-api.

Zenhub reports

Almost all issues are closed in 1 day of opening

my speed: 9 story points /day speed

15 story points in 2 days

from exchange-api.

Estimated vs Actual Time:
excel scatter graph


estimationvsactual.xlsx

Seems like I under estimate, when I estimate for core logic ,it's usually 5-6 times more time

Total estimated time with buffer : 250mins
Total Actual time : 850mins (i.e 3.5 times more time)

from exchange-api.

Refer this in future ,for similar task for proper estimations

from exchange-api.

The process was sort of very tiring:, requires ergonomics workstation & strechly (15sec breaks) breaks .

Also I should remember to close vs code , when not coding, for accurate code time metrics

don't forget standard --fix file.js (standardJS)& deepcode for consistency & code review

from exchange-api.