đź“—
MS Teams/DevOps User Document
  • Managing Workflow with Microsoft Teams
  • Introduction
    • Problem Statement
    • Background
    • Project Constraint
    • Project Scope
  • Background Knowledge
    • Overview
    • What is an Agile Board?
    • What is Trello?
    • What is Scrum?
    • What is Microsoft Teams?
  • Getting Started with Microsoft Teams and Trello
  • Installing Microsoft Teams
  • Creating a New Team
  • Features of Microsoft Teams
  • Microsoft Teams Extension - Trello
  • Adding Trello as a Tab on the Top on the Team Page
  • Possible Errors When installing Microsoft Teams and Trello Extension
  • First Steps and Features of Trello
  • Creating Your First Trello Board
  • Inviting Members to Trello
  • Lists and Cards Within Trello
  • Basic Features of a Trello Card
  • Assigning Deadlines Within a Trello Card
  • Assigning Team Members
  • Linking Microsoft Outlook or Gmail to Trello
  • Adding a Card to Your Trello Board
  • Starting the Project
  • Step I. Project Overview
  • Step II. Break Down the Project and Gather Resources
  • Step III. Construct and Iterate
  • Step IV. Test and Release
  • Conclusion
    • Overview
    • Experience and Qualifications
    • Author Biographies
  • References
    • References
Powered by GitBook
On this page

Was this helpful?

Step III. Construct and Iterate

PreviousStep II. Break Down the Project and Gather ResourcesNextStep IV. Test and Release

Last updated 3 years ago

Was this helpful?

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.