Home_intro

intro story DELWAQ

DELWAQ

DELWAQ is the engine of the D-Water Quality and D-Ecology programmes of the Delft3D suite. It is based on a rich library from which relevant substances and processes can be selected to quickly put water and sediment quality models together.

The processes library covers many aspects of water quality and ecology, from basic tracers, dissolved oxygen, nutrients, organic matter, inorganic suspended matter, heavy metals, bacteria and organic micro-pollutants, to complex algae and macrophyte dynamics. High performance solvers enable the simulation of long periods, often required to capture the full cycles of the processes being modelled.

The finite volume approach underlying DELWAQ allows it to be coupled to both the structured grid hydrodynamics of the current Delft3D-FLOW engine and the upcoming D-Flow Flexible Mesh engine (1D-2D-3D) of the Delft3D Flexible Mesh Suite (or even other models such as TELEMAC).

'DELWAQ in open source' is our invitation to all leading experts to collaborate in further development and research in the field of water quality, ecology and morphology using Delft3D. Feel free to post your DELWAQ related questions or comments in this dedicated forum space. If you are new to DELWAQ, the tutorial (in the user manual) is a good place to start. A list of DELWAQ related publications is available here.

** PLEASE TAG YOUR POST! **

 

 

Sub groups
D-Flow Flexible Mesh
DELWAQ

Cohesive sediments & muddy systems

 


Message Boards

Team Challenges in Retrospectives

PI
priya impex, modified 1 Month ago.

Team Challenges in Retrospectives

Jedi Master Posts: 293 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