The parts of a project component
🟦 Epics, work packages, checklists and acceptance tests
This text provides background information. What types of text are there?
Project components in Leadtime are used to standardize recurring work steps and processes in projects. They break down a project into manageable sections and ensure that similar work always follows the same pattern. This creates reliability in planning and greater efficiency in implementation.
Project components can be made up of four different building blocks - namely
- Epics - the overarching themes of a project
- Work packages - the specific individual tasks to be implemented in the project
- Checklists - Structured lists of points to be checked or ensured
- Acceptance tests - Defined test cases with which the quality of the completed project parts can be checked
These four building blocks form the basic structure of a component. They pre-structure the project.
Structure of a project component
A project component is organized as a tree structure. It is possible to nest work packages, checklists and acceptance tests within epics.
Building blocks
Epics
An epic is a superordinate collective task that thematically bundles several individual tickets (individual tasks). An epic describes a larger goal or a complex requirement that cannot be implemented by a single ticket, but requires several steps or subtasks.
Epics help to maintain an overview of related work and make progress transparent at a strategic level. They prove to be particularly valuable when tasks are staggered or processed by different team members.
Work package
A work package is a self-contained, clearly defined task within a project. It describes a specific stage of work that is carried out by one or more people and delivers a tangible result. Work packages serve as a preliminary stage of a ticket. They provide a standardized task description that can later be specified and individualized based on customer requirements.
The work packages can be provided with a flexible form that enables the systematic recording of all relevant detailed requirements.
Tip: You can move questions to another work package using drag & drop if required!
Available form elements
Work packages can be equipped with a form of any length that enables the systematic recording of customer requirements. The following form elements are available for this purpose.
Element | Purpose | Effects on effort |
Short text | Short, free text input, e.g. to answer a question in one sentence | |
Rich text editor | Longer, formatted text input, e.g. for descriptions, instructions or comments | |
Checkbox | Selection of yes/no or true/false, e.g. to confirm requirements | Yes |
Radio button | Selection of an option from several predefined options, e.g. for decision questions | Yes |
File upload | Upload files such as documents, graphics or specifications | |
Date selection | Set a date, e.g. for deadlines, milestones or delivery dates | |
Multiplier | Enter a number or quantity, e.g. to specify quantities, hours or licenses | Yes |
Person | Selection of a person from the team or on the customer side from the group of project participants |
Checkboxes, radio buttons and multipliers can have an impact on the workload of the work package. More about this here
The various form elements can be used to work with conditions. Read more here
Checklist
A checklist is a special form of a work package / ticket that does not describe a single, completed task, but several small sub-steps or to-dos that can be processed in any order.
Each item on the checklist represents a subtask that can be ticked off individually.
Typical features:
List of tasks: Several individual steps that can be completed in any order or one after the other.
Check-off function: Each item can be marked after completion.
Progress control: The status of the ticket is determined by the number of items ticked off (e.g. 3 out of 5 completed).
Acceptance tests
Acceptance tests are a special type of project component in Leadtime that is used to formally check the successful completion of a project or certain project sections. They ensure that the delivered results meet the agreed requirements and can be released by the customer or an internal quality authority.
In Leadtime, acceptance tests consist of a list of test cases that are systematically processed. Each test case describes what is being tested, which steps are necessary for execution and what result is expected. The test cases can then be marked as passed or failed, supplemented by comments.
Objective:
Formal documentation that the agreed service has been provided correctly. Only when all acceptance tests have been successfully passed is the component or project considered accepted.