PROJECT MANAGEMENT DECISIONS (CLOSED ON 20TH OF FEB)

This “Project Management Decisions” milestone covers the two goals – as a questionnaire - stated below

1- “How should we handle project planning?” 2- “Decisions on project and development management”

As a team, we use Github’s issue feature as the technical communication tool to assign and track tasks. The initial question has been lurked in order to provide a planning report for the end of this semester. Individual and team tracking tools are discussed over the issue opened on Github.

As a result we have decided to track project and development management under the Wiki tab on Github.

The “Project Management” part consists the sections as it follows;

1- Sprints – We use Scrum as the project management methodology. We briefly explained the road map for retrospective, sprint planning and sprint review phases on the associated Wiki page. 2- Board Management – This section describes the scrum board (To-Do, In Progress and Done sections) and how do we select tasks in order to deliver them.
3- Issue Management – Issue description and appropriate labelling.

The “Development Management” part consists of;

1- Modules – API, front-end and mobile. Each module has been represented on the individual folder on the repository. 2- Branching – Git flow will be followed. Each commit should start with the associated issue number. Developer communication is necessary when there are conflicts on the issue where which developer is responsible. 3- Testing – Every developer should test their code before sending it to review. 4- Unit Tests – They will be practiced after the code is written.

As a team we collect the meeting notes on the “Group Communication” section under the Wiki index. We also shared a contributing guideline page to create knowledge in the group. The contributing guideline documentation has been completed as the second milestone on the sprint 2. “Contributing Guideline” could also be found under the Wiki index.

As a result the project management road map stated above describes our working agreement for the “Heredot” project. We achieved to find a balance to track tasks and maintain the work flow over the semester. This part has been all up voted and accepted by the entire team so we closed the issue on the 20th of Feb. We also closed the milestone successfully on 20th of Feb.