đź“—
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?

  1. Background Knowledge

What is an Agile Board?

PreviousOverviewNextWhat is Trello?

Last updated 3 years ago

Was this helpful?

An Agile Board is a way of visualizing the tasks within a project. By using this type of visual framework, one can have a clear understanding of who is responsible for each task. As shown in Figure 1, there often are a few different columns that each task can live in. When a task is created, it is given a name and often a larger description that details what exactly needs to be accomplished. The task first lives in the Backlog, which describes all of the tasks needed to complete the sprint at hand. A task usually then gets assigned to a team member or a group of team members and is placed in the Active column. When that task is completed, it gets moved to the Resolved column. Usually, when a task is in the Resolved column, it passes a series of quality tests to ensure that the job that was supposed to be done was done well. If it doesn’t get accepted by those tests, it gets moved back to the Active column and it is detailed why it wasn’t accepted. If on the other hand it passes the necessary tests, the task gets moved to the Closed column and is fully completed.

The Agile board is a subset of the Agile philosophy, a way of doing project management. The philosophy largely centers around being able to iterate quickly and quickly gather feedback for your product such that it can be developed and improved at a quick pace.

Fig. 1. An Agile board demonstrating tasks being assigned to different contributors of the team.