Allegra: An awork Alternative

awork: Simple Work Management Software

awork is straightforward software for general task management in teams. With awork you can structure, assign, and track tasks. awork has features for basic project management, but it does not count among true project management tools.

Pros and Cons

General Functionality

Operation

awork is offered exclusively as Software as a Service (SaaS) in a cloud operated by the vendor. The vendor guarantees compliance with European data protection standards. Data is stored exclusively within the EU.

Projects and Project Types

In awork, items are managed in projects or workspaces. Areas have types, so settings can be configured centrally for all areas of a given type.

In awork you can create templates for projects or workspaces.

Issues and Issue Types

In task and project management, almost everything revolves around “issues.” In awork, issue types are fixed and cannot be added to or changed.

Issue Hierarchies

awork offers exactly one level of hierarchy. These “sub-tasks” are in some ways treated and displayed differently from “regular” issues. Hierarchical structuring of work packages cannot be achieved with this.

The type of subordinate issues cannot be restricted based on the type of the parent issue. This means it is not possible, for example, to prevent an issue of type “Car” from being subordinated to an issue of type “Engine.”

Notifications

awork has a well-configurable notification system. You can set what is sent to whom and when.

There is an @-mention function and a reminder function.

Access Permissions

You can define custom roles with corresponding permissions.

Attributes

awork does not support custom attributes.

Input Forms

Custom input forms cannot be defined in awork.

Dependencies

In project management and task management, issues often have relationships with one another. For example, a task cannot be started before another one is completed, or an issue cannot be closed until a dependent issue has been resolved.

awork does not support defining dependencies or links between issues.

Cockpits

The system provides users with an overview page (cockpit, dashboard).

Each user can use preconfigured cockpits or assemble their own cockpit from an extensive list of cockpit tiles. However, there are no cockpit templates, and cockpits cannot be centrally assigned to users by system administrators. Available cockpit elements include, among others:

• My issues
• Number of issues in state X over time
• Activity stream
• Predefined filters

Reporting

Reports in awork cannot be generated based on report templates or through direct export to Excel or PDF. Report templates do not exist.

User Management

Synchronization of awork with a directory server is not supported.

awork does not offer integration with common single sign-on systems.

There is no support for two-factor authentication.

User Interface and Usability

The software offers an attractive, clean, and modern-looking user interface. Regular users can get up to speed fairly quickly, even without training. Context-sensitive help guides you when something is not immediately obvious.

For configuration, you need to become familiar with the basic concepts of awork. Material is available in the form of tutorials, videos, slide decks, and user manuals. Training courses are also offered.

The user interface can be adapted to users’ needs. The available menu items can be individually configured for each user or user group.

Interfaces and Extensibility

Nearly all functions available in the user interface are also accessible via a comprehensive REST API in awork. For example, users can be managed, projects created, modified, and deleted, and queries executed.

awork can be extended by the user; corresponding interfaces are provided for this purpose.

Task Management

Delegation

The software does not support the delegation of issues. It is not possible to mark an issue as delegated after passing it on to someone else.

Deputy Function

In awork it is not possible to assign deputies to users.

Recurring Tasks

Some tasks and appointments repeat on a cyclical basis — for example, every first Monday of the month. Handling such recurring issue series can be very helpful and time-saving in task management.

awork allows the creation of recurring issues in the same way you would expect from good calendar applications.

Time Tracking

awork allows you to track the effort (time and cost) for each issue and assign it to accounts. Accounts can be grouped into cost centers and released for projects.

It is possible to use timers within the application to automatically log time spent. Reports provide an overview of who was working on what activities during any past time period.

Support for the Getting Things Done Method

The Getting Things Done method is a proven approach to personal work organization. It allows personal categorization of issues — for example, personal follow-up dates or marking issues as personal favorites.

awork does not support the GTD method.

Support for the RACI Matrix

For task management and project management, the RACI method defines four issue-specific roles through which project participants can be related to a task. Normally, roles are assigned at the project level rather than for individual issues — for example, a project manager or Scrum Master for the entire project. RACI, by contrast, allows roles to be assigned issue-specifically (see /de/blog/projektmanagement/methoden/raci-matrix/).

awork unfortunately does not provide a way to model a RACI matrix.

Workflows

Workflows are typically represented in task management systems in two forms. The first method relates to the workflow of an individual issue as it passes through various stages. The second method involves defining sets of tasks and then working through them.

awork provides a workflow editor.

Project Management

Programs and Portfolios

In many organizations, projects run within the context of programs, portfolios, or product areas. Groups of projects need to be consolidated to maintain an overview.

A fundamental prerequisite for program or portfolio management is the ability to group projects and arrange them hierarchically.

awork unfortunately does not support program and portfolio management.

Subprojects

Larger project undertakings with many issues cannot be sufficiently structured through issue hierarchies alone — they must be broken down into subprojects. Subprojects may require different processes, for example for hardware and software development.

Multi-Project Reports

All queries and reports can span multiple projects and subprojects, which can be freely defined using appropriate filters.

Work Breakdown Structure

Before a project plan can be created, the activities to be performed or the deliverables to be produced must be structured. To represent such a product structure or work breakdown structure (WBS), issues must be able to be arranged hierarchically to any depth.

awork supports only one level of hierarchy with sub-tasks. This means WBS or project plans cannot be created.

Interactive Gantt Chart

With Gantt charts, the timeline of project activities and predecessor-successor relationships can be defined and visualized. awork offers a simple, interactive Gantt component. It is not possible to display the critical path. There are also no project progress bars, and you cannot compare the current planning status with a baseline.

Resource Planning

Resources of various types can be managed and assigned to issues. There is a view that displays resource utilization over time, making over- or under-utilization immediately visible. Resources can be sorted by project or department.

Employee Availability

Each employee has a personal calendar showing their availability. Availability is taken into account by the system during resource planning.

Project Progress

In awork it is possible to measure project progress based on the number of completed tasks relative to the total number of tasks. Additionally, for tasks still open, it is possible to specify the estimated remaining effort until completion.

This gives awork a rudimentary, low-effort way to monitor progress — however, it is not sufficient for more demanding project management requirements.

Agile Project Management

The software offers rudimentary support for agile project management through a taskboard view. Important agile process elements such as epics, user stories, backlogs, and sprints are not available or are only inadequately provided.

For software developers, integrations with source control systems such as Git and Subversion, as well as with CI/CD servers such as Gitlab and Jenkins, are missing.

Alternative Solutions

In addition to Allegra, Jira is certainly also a powerful alternative to awork.

Form your own impression of the comprehensive project management software Allegra and book a free live demo.