Agile Management

Kanban, the Japanese word for billboard, is a process developed by Toyota to visually organize ‘to do, doing, and done’ data. This process has since been developed into digital boards such as Trello. Boards allow users to visually organize data, such as, member responsibilities, tasks, task status, task priorities. In order to manage the GBIM1121 FMT Project, BIMSQUAD has organized boards using a SCRUM process, and a communication strategy in accordance with Agile principles. To achieve this we have developed a synchronized process via two digital platforms ‘Slack’ and ‘Trello’.

Scrum Process

Slack allows group members in different time zones to organize communication, by organizing specific channels with different tasks, as well as linking apps such as ZOOM, Google Calendar, Google Drive and Trello. It also provides useful apps such as Simple Poll, which allows for simple and fast decision making.

The Tables below describes the SCRUM process stategy used illustrated on Trello boards.

Stage SCRUM Process Description

1 Assign Roles and Responsibilities

2 Plan Roadmap

3 Block xx User Story Map

4 Create Block xx Sprint Planning Board

In this board, the SCRUM team roles are illustrated with its assigned members. Boards include detailed job descriptions, and task cards that illustrate the various associated responsibilities. As the project progresses, responsibilities must be updated, and time durations should be added to each responsibility to manage work distribution. This is to enable efficient transfer of responsibilities throughout the project.

The road map board is for the vision and targets. A Road Map provides an overview of the entire FMT project and lists the project goals for each block, as well as the expected delivery date.

The user storyboard is for a summary of all required activities at a high level. Visually present activities and tasks to be completed within each block. User Story map will show how many sprints and releases will be used for each user activity column. The header of each User Activity column to show the Date of Completion. Definition of Ready and Definition of Done checklist can be found on this board.

The Sprint Planning Board helps the scrum team to conduct a sprint planning session where the items necessary to complete the user story on the backlog is broken down into smallmore easily manageable chunks. The team selects User Stories from the User Story board and copy to the backlog of the Sprint planning board. In this board detailed requirements for each task are determined under each Sprint, member responsibilities are defined as well as delivery dates.

5 Create Scrum Board We then create a Sprint Scrum board to focus on task delivery and implementation. Scrum master to check the task delivery date to ensure everyone is on board. Labels used to assign member tasks and illustrate levels of priority. Scrum content to cover:

• Work to do

• Work in Progress

• Work to Review/ Check/ Approve

• Work Shared or Published

6 Plan for Daily Scrum, Scrum Review, Scrum Retrospective

SCRUM meetings will be held via Zoom, unless otherwise specified. Additional daily content to be discussed via slack, including meeting minutes and itineraries.

The sprint review is to inspect the outcome of the Sprint and determine future adaptations. The team to refer

Definition of Ready (DoR) and Definition of Done (Dod) at each card.

The Sprint Retrospective aims to improve team efficiency and quality of the work. It will be held at the end of a sprint by ZOOM. So far there is no specific time.