Project Scope (1.)

WorkPackage as a central element (9.)

Work packages are the essential elements in the project scope and centrally reference the requirements in the system scope that have to be implemented. On the one side, work packages are the link to the referenced requirements, on the other hand, work packages are the right items for organizing work in projects. All further elements in the project scope (project plan, status reports, controlling and release description) refer to their part on work packages. Important parts in work packages are:

• title,
• goal and resultingArtefacts for describing the targets to be reached,
• description and plannedEfford for recording the implementations steps and their costs,
• asignee for the personnel planning and
• realEffort for identifying estimation errors.

At https://www.domaindrivenarchitecture.org/vorlagen you'll find a template for work packages.

Tests

In the context of implementation projects, two types of tests are relevant, the acceptance test and additionally the development test. Acceptance Tests: With the requirements, that are referenced in the work package, the relevant acceptance tests are labeled, that must be passed in context of the implementation. Development Test (10.): Additionally, it's useful to formulate some development tests that are only valid in the scope of the implementation project. Chosen development test can be adopted to the acceptance tests if it's necessary. Then, they are longer available than only for the project lifetime.

ScreenFlows

ScreenFlows are essential elements to form the user guidance. After an implementation, screen flows can persist in the form of entries in the user manual.