Step III. Construct and Iterate

This step is the actual construction stage of the project - frequent iteration of sprints. Details about the sprint such as the number of sprints and their durations can be customized to match the best interest of the team. A typical sprint in the IT industry is performed within two to four weeks with daily meetings [10]. However, since we are undergraduate students enrolled in several other courses with regular exam schedules, sprints must be flexible. Considering that all projects in an undergraduate course are semester-long projects, a two-week sprint with around two meetings per week would be appropriate.

Fig. 16. Our DevOps Manuel Trello Board that we used to organize the User Document project and to complete its parts.

In terms of the Agile Board as shown in Figure 16, students will designate tasks to complete within that sprint and move those task cards from the “Backlog” column to the “To Do” column. Once a designated member starts working on a task, move the task card to the “In Progress” column. And when the task is completed, move the task card to the “Done” column. In the meantime, schedule regular meetings during the sprint to follow up on the progress, request extra help on a task if needed, and break the task down even further if necessary.