Denis Cercasin

How we would improve for future projects

• Better project scoping and time estimation
  Our project idea turned out to be slightly too ambitious for the available timeframe. In the future, we would try to break down the scope more realistically, define an even smaller core MVP, and add extras only if time permits.

• More structured team coordination
  We could have benefitted from more frequent check-ins, especially in person, to push each other toward milestones and keep momentum. Regular standups or weekly syncs would help with accountability and alignment.

• Clearer role division and ownership
  Although we collaborated well, certain tasks could have had clearer ownership from the start to avoid duplicated work or dependencies blocking progress.

• Earlier focus on edge cases and validations
  While we implemented core flows early, some validations and edge-case handling (e.g. error feedback) came late. Next time, we would treat these as part of “done” earlier.

• Testing and code review habits
  Our project would benefit from more systematic testing and mutual code reviews. Future projects should include basic test coverage and review steps in the workflow.

• Customer feedback earlier in the process
  We collected user feedback near the end. Next time, involving potential users earlier (e.g., after wireframes or mid-way) could help shape features more efficiently and also help us better understand the MVP core functionalities that are most needed.

• Write documentation continuously, not just at the end
  We postponed most of the documentation work to the end of the project. While that’s tempting, it made the process more stressful. In the future, we’d aim to document important decisions and components step-by-step, even if it’s a bit boring or unglamorous.

Last build: 20 Jul 2025, 00:44+00:00