Guiding Principles and User Stories,

Design Principles

• A user should never need to use the keyboard (the one exception is entering an optional recipe name)
• Less flexibility is better than too many options. The existing software already has too many options.
• Less is more. Ancillary data should be hidden until a user wants to drill down.

Stories

Configure the brew house

• Brewer can set their default batch size, which will obviate the need to select a batch size when designing or brewing
• Brewer can set their average mash extraction efficiency
• Brewer can measure and set their boiler energy output (which obviates the need to estimate boil off)

Design a new beer

• A brewer can create a recipe customized to their tastes in under one minute
• Recipe should have a default name that can be changed later
• Select a beer style in order to receive a shorter list of malts and hops
• Select malts for the beer in a way that necessitates initial gravity selection
  • Select malt quantities without using the keyboard
  • Easily target seek a starting gravity by tweaking quantities
  • User can see entire malt bill on one screen without scrolling
• Select hops in a way that necessitates IBU selection
  • Select hop quantities and boil times
• Select yeast in a way that necessitates ABV selection

Brew a beer from a recipe

Taste a finished beer