SCRUM Retrospective

Scrum Retrospectives were collected on Slack chanel and meeting minutes for Phase 1, for delivery on Feb 20, 2022

Member Comments

Group two members In this exercise, we brainstormed our scrum retrospective in Slack, and then discussed the points in a daily scrum. Our findings can be found illustrated and described below.

Continue

Summarize references in format that can be inserted into documents when necessary.

Tidy the channels.

Stop

At the moment some channels are crowded with individual group noise.

Some large documents have been posted on channels that can be intimidating to go through with our time frames.

Invent

We can add channels for group work coordination eg. BIM Coordination/ Scrum Master board, Discipline Managers board. etc.

We need to test the time constrain if works for everyone:

We still need to discuss the severity level and time constrain during scrum planning. Act After each scrum meeting, our team shall discuss the following items to improve our agile process. What worked well? What could be improved? What will we commit to doing in the next scrum circle?

Mentor (from Meeting Minutes)

We gave a brief introduction of ourselves and of our projects to the mentor. Karol pointed out that the FMT will not be graded with each hand in, but the project will receive a cumulative grade at the end. This suggests:

The importance of Agile management and implementation. We have to make sure that our plans remain simple, well illustrated and easy to follow. Although details are not a priority, remember that processes need to be implemented to effectively coordinate.

It is important that we focus on efficient procedures. The details can be updated throughout the FMT as we build our knowledge. But good foundation protocols are very important. With each SCRUM retrospective, we should be able to suggest improvements that should be reflected in the final delivery.

It is important that each block of information is illustrated in each assignment, so that the final project can prove a complex understanding of the entire Master’s program.

It is important to keep things simple. Focus on accuracy/ precision over a final output. Each assignment should show a minimum of information delivered in lectures. Remember details can always be added.

Descriptive documentation. As we continue to present the Sprint Planning and other boards, remember to document a detailed description of the board design. Eg. Use legends to describe what colours, and labels mean.

FINALLY! Let’s try to enjoy the process. With the potential to revise and improve work throughout the FMT, don’t be too hard on yourselves. Work hard, be consistent and do your best! “Fighting!”

Think of the BIG picture. Think of BIMSQUAD as a startup company. With goals:

To add value to the owner/shareholder through BIM implementation, whether by saving money or time. The creation of automated templates and BIM processes to be improved and implemented in future projects. To improve communication with all parties and therefore make faster and better decisions. Etc. Why should a client choose BIMSquad over any other company?

Summarize references in format that can be inserted into documents when necessary.

Tidy the channels. SLACK

At the moment some channels are crowded with individual group noise.

Stop

Posting large research references without attached summaries

Invent

How can we do things differently?

We can add channels for group work coordination

We need to test the time constrain if works for everyone:

We still need to discuss the severity level and time constrain during scrum planning.

What worked well/ could be improved? What we commit to doing in the next scrum cycle?

Act

What should we do next?

Use of agile retrospective template as judging criteria.

What help us back? Continue What help us move forward? 1.

Individually, reflect on what worked and you should continue doing and stop doing, Write down any ideas into the yellow section.

Reflect together

4 min per section 15 min together

Individually, rthink of next steps. Present and commit together.

4 min per section 10 min together