M5 Master mov.io

The extensive ideation phase challenged the team as each member brought different perspectives, which led to difficulties in agreeing on a unified vision for mov.io. Uncertainty about the most appropriate technology required thorough research to make an informed decision. In addition, each team member brought unique insights, requiring additional effort to synthesize ideas and define key features, which impacted the initial stages of project build.

Incorporating a range of new technologies, each assigned to a specific team member, presented a multi-faceted challenge. Integrating these technologies required an extensive research and learning process. Becoming proficient in these different technologies, while simultaneously implementing them within the project, added a layer of complexity that required a dedicated effort to master and apply the acquired knowledge.

Merge Conflicts and differences in coding approaches: Collaborative coding presented challenges in managing conflict during the merge process, particularly due to the different coding approaches adopted by team members. Each responsible for specific components, team members had different perspectives on coding styles and methodologies. Establishing uniform coding conventions and improving communication channels became critical to managing conflicts and ensuring seamless integration of different components.

A critical setback occurred shortly before the project submission deadline when the Git server experienced downtime for two days. This unexpected interruption disrupted the team’s workflow, impacting collaboration and version control. Swift adaptation and the implementation of alternative solutions were essential to ensure the project’s continuity despite the server outage.