intro story 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.




Sub groups
D-Flow Flexible Mesh

Cohesive sediments & muddy systems


Message Boards

Product Backlog Refinement

priya impex, modified 1 Month ago.

Product Backlog Refinement

Jedi Master Posts: 274 Join Date: 10/15/20 Recent Posts
Product Backlog RefinementIt is an ongoing process where the Product Owner and the Development Team work together in understanding the highly ordered Product Backlog items. They then add details, estimates, and order to the items in the product backlog. During this activity, the product backlog items are reviewed and revised. The Scrum Team decides how and when the refinement will happen. Backlog Refinement should not take more than 10% of the actual capacity of the Development Team.
The product backlog items can be updated anytime by the Product Owner or at their discretion. The Development Team is responsible for estimating the Product Backlog items as they are responsible for coming up with the Product Increment. The higher ordered PBIs usually have more details and precise than the lower ordered ones. As the Product Owner decides the order of priority of PBIs, they typically have more clarity of the items. Estimates with precision can happen only on the items that have more clarity and precise details.  Refinement usually happens on the ordered items whose chances of getting implemented in the next few sprints are high. The PBIs are refined in such a way that they can be completed within a Sprint. If they are too big or couldn't be done in a Sprint, they will be vertically split so that they could be accommodated in a Sprint. Only those PBIs which could be "done" within a Sprint is considered as "ready" for selection in Sprint Planning. <!--td {border: 1px solid #ccc;}br {mso-data-placement:same-cell;}-->Devops Online Training