Documentation Fragment & Correlating Task Classification

Small change

Should affect only one screen. If multiple screens are affected, please make multiple small changes, which can be grouped together as a package of small changes.

Examples for small changes:

• label changes
• typos
• moviing buttons
• adding a new property (not having effect on a process), e.g. adding a descriptiive field to an adminstration form

Default estimations:

• Frontend time max. 1h, Backend 1h
• Regular delay after development before it typically can be handed over to Customer: 0h
• Clocked extra time on fixes on development Senior Frontend 0h, Senior Backend 0h OR Junior Frontend 0h, Junior Backend 0h

Change

Example for regular changes:

• Adding a new table on page
• Extension of an existing page (multiple fields)
• Updating Standard Frontend-Component - Changing behaviour on a single simple component, like search component or dropdown component.

Default Estimations

• Frontend time max. 4h, Backend 2h
• Regular delay after development before it typically can be handed over to Customer: 1h
• Clocked extra time on fixes on development, Senior Frontend 0h, Senior Backend 0h OR Junior Frontend 1h, Junior Backend 1h

New Standard (Admin) Page

Example: Standard Overview-page with Standard Grid plus a Details-page (not many fields, typically one tab, some validations)

Field Example:

• Incoming Payments Administration
• Bank Administration

Default Estimations

• Frontend time max. 12h, Backend 6h
• Regular delay after development before it typically can be handed over to Customer: 4h
• Clocked extra time on fixes on development, Senior Frontend 1h, Senior Backend 0.5h OR Junior Frontend 2h, Junior Backend 1h

New Dashboard Standard App (Dashboard Widget + App with Overview and details page)

- major layout changes / on-screen process changes

- new simple process

- new complex process

- simple new process chain

- complex process chain with interaction on already existing processes