Scope

• What will and what won't be in the database?
• Only what is known and can be controlled well. Avoid wrong and maybe outdated data. Create for example an interface with an other system, where that data is inside the scope.
• Keep the scope as small as possible. That is hard to do, as users prefer to play safe. They want everything, so they don't miss anything. Scopeless projects have a high chance of failure. The best is the enemy of the good.