# 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.
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.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://ms-teams.gitbook.io/ms-teams-devops-user-document/step-iii.-construct-and-iterate.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.