intro story Coast / Estuary

Coast / Estuary

Coastal systems are among the most dynamic physical systems on earth and are subject to a large variety of forces. The morphodynamic changes occurring to coastlines worldwide are of great interest and importance. These changes occur as a result of the erosion of sediments, its subsequent transport as bed load or suspended load, and eventual deposition. 
Estuaries are partly enclosed water bodies that have an open connection to the coast. Estuaries generally have one or more branching channels, intertidal mudflats and/or salt marshes. Intertidal areas are of high ecological importance and trap sediments (sands, silts, clays and organic matter).
Within the Delft3D modelling package a large variation of coastal and estuarine physical and chemical processes can be simulated. These include waves, tidal propagation, wind- or wave-induced water level setup, flow induced by salinity or temperature gradients, sand and mud transport, water quality and changing bathymetry (morphology). Delft3D can also be used operationally e.g. storm, surge and algal bloom forecasting. 
On this discussion page you can post questions, research discussions or just share your experience about modelling coastal and/or estuarine systems with Delft3D FM. 




Sub groups
D-Flow Flexible Mesh
Cohesive sediments & muddy systems



Message Boards

Team Challenges in Retrospectives

priya impex, modified 1 Month ago.

Team Challenges in Retrospectives

Jedi Master Posts: 274 Join Date: 10/15/20 Recent Posts
Team Challenges in Retrospectivesif the team is reluctant to have a Retrospective as they feel they are having the same points over a few meetings. Even after explaining to them the importance of retro meeting they are not willing to continue discussing. They don’t want to have retrospectives anymore. What can be done to bring more participation and outcomes from a retrospective?On 13-Feb-2020, on Agility Thinking WhatsApp groups, there was a discussion on the below topic. Many of the practicing Scrum Masters from the group participated in the discussion in WhatsApp and below are some of them.I would focus on selective points mostly the ones which team want to stop- have a realistic goal - action item - have a target date and an owner and make the results visible to the teamSo by setting the example and make that working - will help the team understand how useful it is to have retros.Unless Retro giving value out of it, team members won't participate wholeheartedly. Ensure Retro action items are documented, monitored and tracked. Team needs to be convinced that retro gives an effective platform to raise your voices, concerns along with positive feedback. SM really has to use his soft skills to ensure retro won't become blame game exercise but troubleshooting exercise for issues put on the table.We need to understand what are the blockers that do not let the implementation of improvements that are coming out in the Retro meeting. Then need to have some quick wins to show that their feedback is valuable and is being actioned. Once the team members see some positive action they will open up. We also need to set realistic expectations from the team on the ground reality and culture, which will take some time to change.Even after a few retrospective meeting the point raised by team are not address means there is a big problem. There should be an open discussion and the reason for not implementing should give a team this will give a clear idea that whatever they are suggesting is not ignored and management is working to fix it and soon they will notice the change.I think SM & PO together can find a new findings for each retro either achievement or improvement.If the same points are getting discuss than forcing them for meeting .. can change the way of meeting to some informal way for some time. Devops Online Training