SCRUM Retrospective

Scrum Retrospectives were collected on Slack and meeting minutes for Phase 3, for delivery on August 28, 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 Validation and Issue tracking

Update folder organization on CDE to work in progress, published, shared and archived as per lecture notes.

We have updated the Sprint planning to reflect what needs to be developed for the FMT Stop

Do not move as a zip into BIM Sync.

Invent

Plan to resolve a detailed issue management and clash detection process , and implement a better collaboration workflow.

Once we have finalized the issue management and clash detection we need to update our collaboration workflow.

Act There were some issues with M8/units 4 and 5, and as a result there was some confusion on how to proceed with our validation and clash detection for our discipline model.

Organize daily scrums to catch up with requirement deliverables.

Mentor (from Meeting Minutes)

Instal BIMCollab/ (BCF Managers):

One person checks clashes. Exports packages as BCF. Import issues to BIMSync.

OPTION 1

Install BCF managers into proprietary software. Can also use BIM Collab Zoom for issue report. All issues should be transferred to BIM Sync. Create rule sets and smart views. Perform issue management. Move at the end of the coordination to close the data flow in order to close the cycle. Visually validate models on BIM Sync, and add any associated documents

OPTION 2

Do visual checks in Solibri/ BIM Collab. NB. Solibri has built in tools where you can create rule sets and instantly move into BIM Sync. In BIM Sync @ right hand corner (RED circle) there is BCF manager plugin. Solibri can check escape zones, accessibility and building code accommodations COORDINATION

Deliver all models to specific space. Check models (download models or reap from plugins) for seamless issue management. Check models 2 for BCF and IFC for rules e.g don’t delete elements, edit instead. Check BIM uses. In BIM Sync you can link objects e.g warranty cards and relevant information.

BIM Sync PLUGIN

Choose the read files for submission. Can always update in backlogs

If we have a problem handling IFC models, try IFC optimizer by Solibri -like WINZIP, can delete empty containers. Focus on optimizing geometry and not the data. Will be filled by you in the future

Validation and Issue tracking Update folder organization on CDE to WIP, published, shared, archived

We updated the Sprint planning to reflect what needs to be developed for the FMT

Stop

Invent

How can we do things differently?

Plan to resolve a detailed issue management and clash detection process

Plan to implement a better collaboration workflow

We need to update our collaboration workflow and process maps

Do not move as a zip into BIM Sync

Act

What should we do next?

Resolve confusion around M8/units 4/ 5.

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

Research how to proceed with our validation and clash detection for our discipline model.

Organize daily scrums to catch up with requirement deliverables

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