Skip to content

Retrospective 1

james-gabauer edited this page Jul 9, 2018 · 1 revision

Retrospective

Process Improvements

Using the Agile Model Driven Development style has been beneficial in aiding the teams productivity and provides a means for working on a large scale project on a small timescale. However, it reduces the collaboration needed for such a fast development cycle as everyone is split out into various jobs. For the next stages of development we might use a similar model but increase the amount of work that is shared between team members so that everyone has an insight into all of the components being completed each day and how the project is coming together as a whole. In this specific team working more closely would also be more effective as non of the members are specifically software engineers so sharing experience and knowledge is crucial for the completion of a project like this.

Progress

What has been completed?

Minimal development has been completed as it has only been 2 working days since the commencement of the project. That being said the initial login/signup functionality and the ability to upload photos of books to the database have been completed and there is a rough framework for the app to be built around. This framework will allow for easier progress to be made in the coming week.

What needs to be done?

A list of tasks and features has been compiled that will need to be completed before we can achieve a Minimum Viable Product for the demonstration. This will include most of the personal profile and event creation features and the necessary features for the basics of books sharing, location services, private messaging, and internal currency.

Overview

Overall, given the amount of time that has passed, progress has been satisfactory. Realistic goals were set in the initial breakdown of tasks so at this stage in development all of the tasks that have been set are viable and able to be completed in the time frame established. This evaluation of tasks may be subject to change as development progresses and problems are faced. The time constraint has been accounted for and there are some features that could be removed from the demo build that would still allow for a minimum viable product.