On this page

Project and Work Management

Project and work management tools coordinate task planning, progress tracking, team collaboration, and delivery reporting across organisational initiatives. These platforms centralise work items, assignments, timelines, and status updates to provide visibility into project health and resource utilisation.

This page covers general-purpose project management platforms supporting both traditional and agile methodologies. Tools assessed here handle task and issue tracking, project planning, time logging, and team coordination. Adjacent categories not covered include: dedicated agile planning tools (sprint-only), portfolio management platforms (programme-level), case management systems (beneficiary-focused workflows), and grant management systems (funder compliance).

Assessment methodology

Tool assessments derive from official vendor documentation, published API references, release notes, and technical specifications as of 2026-01-24. Feature availability varies by product tier, deployment model, or region. Verify current capabilities directly with vendors during procurement. Community-reported information is excluded; only documented features are assessed.

Requirements taxonomy

This taxonomy defines evaluation criteria for project and work management tools. Requirements are organised by functional area and weighted by typical priority for mission-driven organisations. Adjust weights based on your specific operational context.

Functional requirements

Core capabilities that define what the tool must do.

Task and issue management

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
F1.1	Task creation and editing	Create, modify, and delete tasks with configurable fields including title, description, assignee, dates, and priority. Support for bulk operations on multiple tasks simultaneously.	Full: unlimited custom fields, bulk edit, templates. Partial: limited custom fields or no bulk operations. Basic: fixed field set only.	Review task configuration documentation; test field customisation during trial	Essential
F1.2	Task hierarchy	Support for parent-child task relationships enabling breakdown of work into subtasks. Multiple hierarchy levels allow complex project structures.	Full: unlimited nesting depth, cross-project relationships. Partial: single subtask level or project-scoped only. None: flat task list.	Review hierarchy documentation; test nesting behaviour	Essential
F1.3	Custom fields	Define organisation-specific fields beyond defaults. Field types include text, number, date, dropdown, user picker, and multi-select.	Full: unlimited fields, all types, field-level permissions. Partial: limited number or types. Basic: no custom fields.	Review custom field documentation; test field creation	Important
F1.4	Task templates	Pre-configured task structures for recurring work patterns. Templates capture field values, subtask structures, and checklists.	Full: project and global templates, subtask templates, automation triggers. Partial: basic templates without structure. None: manual recreation.	Review template documentation; verify template capabilities	Important
F1.5	Task linking and dependencies	Relationships between tasks including blocks, blocked-by, relates-to, and duplicates. Dependency chains affect scheduling calculations.	Full: multiple relationship types, cross-project links, visualisation. Partial: single relationship type. None: no linking.	Review dependency documentation; test link creation	Important
F1.6	Recurring tasks	Automatic task creation on defined schedules (daily, weekly, monthly, custom). Recurrence rules specify intervals and end conditions.	Full: flexible schedules, template-based recurrence, conditional recurrence. Partial: fixed intervals only. None: manual recreation.	Review recurrence documentation; test schedule configuration	Desirable
F1.7	Checklists and subtasks	Lightweight task decomposition through checklists or quick subtasks. Checklist completion contributes to progress calculations.	Full: unlimited items, assignable checklist items, progress tracking. Partial: limited items or no assignment. Basic: simple lists only.	Review checklist documentation; test checklist features	Important

Project planning and scheduling

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
F2.1	Gantt chart visualisation	Interactive timeline view displaying task schedules, dependencies, and critical path. Drag-and-drop rescheduling with dependency awareness.	Full: interactive editing, dependency lines, critical path, baseline comparison. Partial: read-only or no dependencies. None: no timeline view.	Review Gantt documentation; test interactive features	Important
F2.2	Milestone tracking	Distinct work items representing key deliverables or checkpoints. Milestones appear on timelines and trigger notifications.	Full: dedicated milestone type, timeline integration, progress tracking. Partial: milestone as task variant. None: no milestone concept.	Review milestone documentation; test milestone functionality	Important
F2.3	Baseline management	Capture planned schedules for comparison against actual progress. Multiple baselines track changes across planning iterations.	Full: multiple baselines, variance reporting, baseline history. Partial: single baseline. None: no baseline support.	Review baseline documentation; test baseline creation	Desirable
F2.4	Resource scheduling	Allocate team members to tasks with capacity awareness. Resource calendars account for availability, leave, and working hours.	Full: capacity planning, workload views, conflict detection. Partial: assignment only without capacity. Basic: simple assignment.	Review resource documentation; test allocation features	Important
F2.5	Calendar integration	Synchronise tasks and milestones with external calendars. Bidirectional sync maintains consistency across systems.	Full: bidirectional sync, multiple providers, iCal export. Partial: one-way sync or export only. None: no calendar integration.	Review calendar documentation; test sync behaviour	Desirable
F2.6	Workload management	Visualise team member capacity and task distribution. Identify over-allocation and balance work across team.	Full: capacity views, utilisation metrics, rebalancing tools. Partial: basic assignment views. None: no workload visibility.	Review workload documentation; test capacity features	Important

Agile and Kanban support

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
F3.1	Kanban boards	Visual boards with customisable columns representing workflow stages. Cards move through columns reflecting status progression.	Full: custom columns, WIP limits, swimlanes, card customisation. Partial: fixed columns or limited customisation. Basic: simple board only.	Review Kanban documentation; test board configuration	Important
F3.2	Sprint management	Time-boxed iterations with backlog grooming, sprint planning, and velocity tracking. Sprint boards show iteration-scoped work.	Full: sprint planning, backlog, velocity charts, retrospectives. Partial: basic sprints without metrics. None: no sprint concept.	Review sprint documentation; test sprint workflow	Context-dependent
F3.3	Backlog management	Prioritised list of work items awaiting scheduling. Drag-and-drop prioritisation, estimation, and sprint assignment.	Full: prioritisation, estimation, filtering, backlog refinement. Partial: basic list without prioritisation. None: no backlog concept.	Review backlog documentation; test prioritisation features	Context-dependent
F3.4	Story points and estimation	Assign effort estimates to tasks using points, hours, or custom units. Aggregation supports capacity planning and velocity tracking.	Full: multiple estimation types, aggregation, velocity calculation. Partial: single estimation type. None: no estimation support.	Review estimation documentation; test point assignment	Context-dependent
F3.5	Burndown and burnup charts	Visual progress indicators showing work completed versus remaining. Charts update automatically as tasks progress.	Full: multiple chart types, custom date ranges, export. Partial: single chart type. None: no progress charts.	Review chart documentation; verify chart availability	Context-dependent
F3.6	WIP limits	Configurable constraints on concurrent work in Kanban columns. Limits prevent overloading and encourage flow.	Full: per-column limits, visual warnings, enforcement options. Partial: limits without enforcement. None: no WIP limits.	Review WIP documentation; test limit configuration	Desirable

Time tracking and reporting

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
F4.1	Time logging	Record time spent on tasks with date, duration, and optional notes. Support for both duration entry and start/stop timers.	Full: duration and timer, bulk entry, approval workflow. Partial: duration only. None: no time tracking.	Review time tracking documentation; test entry methods	Important
F4.2	Timesheet views	Aggregated time entry views by user, project, or date range. Timesheet submission and approval workflows for billing.	Full: timesheets, approval workflow, export. Partial: basic aggregation. None: task-level only.	Review timesheet documentation; test approval workflow	Important
F4.3	Budget tracking	Compare actual time and cost against project budgets. Alerts on approaching or exceeded budgets.	Full: budgets, actuals, variance, alerts. Partial: basic tracking without alerts. None: no budget concept.	Review budget documentation; test budget features	Desirable
F4.4	Custom reports	Build reports with configurable filters, grouping, and metrics. Report templates save common configurations.	Full: report builder, saved reports, scheduling, export. Partial: predefined reports only. Basic: no reporting.	Review reporting documentation; test report builder	Important
F4.5	Dashboard widgets	Configurable dashboard components displaying project metrics, charts, and status summaries. Personal and shared dashboards.	Full: custom dashboards, multiple widgets, sharing. Partial: fixed dashboards. Basic: no dashboard customisation.	Review dashboard documentation; test widget configuration	Important
F4.6	Export formats	Extract data in standard formats for external analysis. Formats include CSV, Excel, PDF, and XML.	Full: multiple formats, scheduled exports, API export. Partial: single format. Basic: no export.	Review export documentation; verify format availability	Essential

Collaboration and communication

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
F5.1	Comments and discussions	Threaded discussions attached to tasks, projects, or other objects. @mentions notify relevant users.	Full: threading, mentions, rich text, reactions. Partial: flat comments. Basic: no comments.	Review comment documentation; test mention behaviour	Essential
F5.2	File attachments	Upload and attach files to tasks and projects. Preview common file types without download.	Full: direct upload, preview, versioning, search. Partial: upload only without preview. Basic: no attachments.	Review attachment documentation; test file handling	Essential
F5.3	Activity streams	Chronological feed of changes to tasks, projects, and team activity. Filtering by user, project, or change type.	Full: comprehensive logging, filters, export. Partial: limited logging. Basic: no activity tracking.	Review activity documentation; test feed completeness	Important
F5.4	Notifications	Alerts for relevant changes via email, in-app, mobile push, or integrations. Configurable notification preferences.	Full: multiple channels, granular preferences, digest options. Partial: limited channels or preferences. Basic: no notifications.	Review notification documentation; test preference configuration	Essential
F5.5	Wiki and documentation	Built-in documentation pages for project knowledge. Wiki supports formatting, linking, and version history.	Full: wiki with hierarchy, versioning, search, templates. Partial: basic pages without hierarchy. None: no wiki.	Review wiki documentation; test wiki features	Desirable
F5.6	Real-time collaboration	Live updates visible to concurrent users without page refresh. Presence indicators show active users.	Full: real-time sync, presence, conflict resolution. Partial: periodic refresh. None: manual refresh required.	Review real-time documentation; test concurrent editing	Important

Technical requirements

Infrastructure, deployment, and integration considerations.

Deployment and hosting

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
T1.1	Self-hosted deployment	Installation on organisation-controlled infrastructure. Full data control and network isolation options.	Full: documented installation, active maintenance, commercial support. Partial: community-only support. None: SaaS only.	Review installation documentation; verify support options	Context-dependent
T1.2	Cloud/SaaS deployment	Vendor-managed hosting with guaranteed uptime. Reduces operational overhead for IT teams.	Full: managed service, SLA, regional options. Partial: limited regions. None: self-hosted only.	Review SaaS documentation; verify SLA terms	Context-dependent
T1.3	Container deployment	Official container images for Docker, Kubernetes, or similar orchestration. Enables consistent deployment across environments.	Full: official images, Helm charts, documentation. Partial: community images. None: no container support.	Review container documentation; verify image availability	Important
T1.4	High availability	Architecture supporting redundancy and failover. Database replication, load balancing, and session handling.	Full: documented HA architecture, clustering, no SPOF. Partial: limited HA options. None: single-instance only.	Review HA documentation; assess architecture	Important
T1.5	Offline capability	Functionality when network connectivity is unavailable. Local data storage with synchronisation on reconnection.	Full: offline mode, sync, conflict resolution. Partial: limited offline. None: always-connected required.	Review offline documentation; test offline behaviour	Context-dependent

Scalability and performance

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
T2.1	User capacity	Maximum concurrent users supported without degradation. Documented limits and scaling guidance.	Full: documented limits, horizontal scaling, enterprise scale. Partial: small team focus.	Review scalability documentation; check user limits	Important
T2.2	Data volume handling	Performance with large numbers of tasks, projects, and attachments. Archival and cleanup options for historical data.	Full: tested at scale, archival features, performance guidance. Partial: limited testing.	Review performance documentation; check volume limits	Important
T2.3	Response time	Page load and API response times under normal and peak load. Published performance targets or SLAs.	Full: documented targets, monitoring, SLA. Partial: informal guidance. None: no performance commitments.	Review performance documentation; test during trial	Important

Integration architecture

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
T3.1	REST API	Programmatic access to all platform capabilities. Well-documented endpoints with consistent conventions.	Full: comprehensive API, versioned, documented examples. Partial: limited coverage. None: no API.	Review API documentation; assess endpoint coverage	Essential
T3.2	API authentication	Secure authentication methods for API access. Support for tokens, OAuth, and service accounts.	Full: OAuth 2.0, API tokens, service accounts. Partial: basic auth or limited methods.	Review auth documentation; verify supported methods	Essential
T3.3	Webhooks	Event-driven notifications to external systems. Configurable events and reliable delivery with retry logic.	Full: comprehensive events, retry, signing. Partial: limited events. None: no webhooks.	Review webhook documentation; check available events	Important
T3.4	Bulk data operations	Efficient large-scale data import and export. Batch APIs, streaming, and asynchronous processing.	Full: batch APIs, streaming, progress tracking. Partial: limited batch size. None: record-by-record only.	Review bulk operation documentation; check limits	Important
T3.5	Pre-built integrations	Native connectors to common systems including version control, communication, and file storage platforms.	Full: official integrations, marketplace, active maintenance. Partial: limited integrations.	Review integrations directory; verify maintenance status	Desirable
T3.6	Version control integration	Connection to Git repositories for commit linking, branch tracking, and development workflow integration.	Full: GitHub, GitLab, Bitbucket native integration. Partial: single provider. None: no VCS integration.	Review VCS documentation; test commit linking	Context-dependent

Security requirements

Security controls and data protection capabilities.

Authentication and access control

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
S1.1	Multi-factor authentication	MFA on user accounts using TOTP, WebAuthn, or push notification methods. Enforceable by policy.	Full: multiple MFA methods, enforced by policy. Partial: single method. None: password only.	Review MFA documentation; test configuration	Essential
S1.2	Single sign-on integration	Federated identity via SAML 2.0 or OpenID Connect. Integration with enterprise identity providers.	Full: SAML and OIDC, multiple IdP. Partial: single protocol. None: local auth only.	Review SSO documentation; check supported protocols	Essential
S1.3	Role-based access control	Granular permission management based on roles. Custom roles with fine-grained permissions.	Full: custom roles, granular permissions, inheritance. Partial: fixed roles. Basic: user/admin only.	Review RBAC documentation; assess permission granularity	Essential
S1.4	Project-level permissions	Access control scoped to individual projects. Members, viewers, and custom roles per project.	Full: configurable per-project roles, inheritance from global. Partial: project membership only.	Review project permission documentation; test configuration	Essential
S1.5	Session management	Controls for session duration, concurrent sessions, and forced logout. Administrative session termination.	Full: configurable policies, session visibility, remote termination. Partial: limited controls.	Review session documentation; verify admin capabilities	Important
S1.6	IP allowlisting	Restrict access by source IP address or range. Support for VPN integration and geographic restrictions.	Full: configurable IP rules, ranges, enforcement. Partial: limited controls. None: no IP restrictions.	Review network security documentation; test IP filtering	Desirable

Data protection

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
S2.1	Encryption at rest	Data encrypted when stored. AES-256 or equivalent with documented key management.	Full: AES-256, documented key management. Partial: encryption available but not default. None: unencrypted.	Review encryption documentation; verify algorithm	Essential
S2.2	Encryption in transit	Data encrypted during transmission. TLS 1.2 or higher enforced for all connections.	Full: TLS 1.2+ enforced, certificate management. Partial: TLS available but not enforced.	Review transport security documentation; test with analyser	Essential
S2.3	Audit logging	Comprehensive logging of data access and changes. Immutable logs with configurable retention and export.	Full: immutable logs, retention configuration, export. Partial: limited logging.	Review audit log documentation; assess completeness	Essential
S2.4	Data residency controls	Specify and enforce data storage location. Regional instances for compliance with data sovereignty requirements.	Full: selectable regions, documented data flows, contractual guarantees. Partial: limited regions.	Review data residency documentation; verify contractually	Important
S2.5	Attachment security	Secure handling of uploaded files. Virus scanning, access control inheritance, and secure download URLs.	Full: scanning, ACL inheritance, signed URLs. Partial: basic storage.	Review attachment security documentation	Important

Security certifications and compliance

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
S3.1	SOC 2 Type II	Independent audit of security controls covering the Trust Services Criteria. Current certification with report availability.	Full: current certification, report available. Partial: SOC 2 Type I only. None: no SOC certification.	Request SOC 2 report; verify audit date	Important
S3.2	ISO 27001	Information security management system certification. Certification scope covers relevant services.	Full: current certification, relevant scope. None: no certification.	Request certificate; verify scope	Important
S3.3	GDPR compliance	Documented compliance with EU data protection regulation. Data Processing Agreement availability and processor records.	Full: DPA available, processing records, DPIA support. Partial: general privacy policy only.	Review GDPR documentation; assess DPA terms	Essential
S3.4	Penetration testing	Regular security testing by independent parties. Annual testing with documented remediation process.	Full: annual testing, remediation documented. Partial: internal testing only. None: not disclosed.	Request pen test summary; verify remediation process	Important

Operational requirements

Day-to-day administration and management considerations.

Administration and configuration

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
O1.1	Administrative interface	Comprehensive admin tools for user, project, and system management. Role-specific views and bulk operations.	Full: comprehensive UI, role-specific, bulk operations. Partial: limited admin UI.	Review admin documentation; assess during trial	Important
O1.2	Configuration as code	Manage configuration through version-controlled files or API. Support for GitOps workflows.	Full: complete configuration via files/API. Partial: limited options. None: UI only.	Review configuration documentation; check IaC support	Desirable
O1.3	Multi-tenancy	Isolated environments for different units, projects, or clients. Tenant-specific configuration and data separation.	Full: tenant isolation, separate configuration. Partial: workspace separation. None: single tenant.	Review multi-tenancy documentation; assess isolation	Context-dependent
O1.4	Localisation	Interface available in multiple languages with configurable date, time, and number formats. Right-to-left language support.	Full: multiple languages, RTL, format configuration. Partial: limited languages.	Review localisation documentation; check language availability	Important

Monitoring and observability

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
O2.1	Health monitoring	Programmatic health check endpoints for monitoring systems. Component status and dependency checks.	Full: detailed endpoints, component status. Partial: basic up/down. None: no health API.	Review monitoring documentation; test endpoints	Important
O2.2	Metrics export	Exposure of operational metrics for monitoring platforms. Prometheus, OpenTelemetry, or equivalent support.	Full: Prometheus/OTLP export. Partial: built-in dashboard only. None: no metrics.	Review metrics documentation; check export options	Important
O2.3	Log export	Forward logs to external systems for aggregation and analysis. Structured logging with configurable destinations.	Full: structured logging, multiple destinations. Partial: batch export only.	Review logging documentation; check export formats	Important

Backup and recovery

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
O3.1	Automated backup	Regular automated data backup with configurable schedules and retention policies. Encryption of backup data.	Full: configurable schedule, retention, encryption. Partial: manual backup.	Review backup documentation; verify for deployment model	Essential
O3.2	Point-in-time recovery	Restore to specific point in time for data recovery. Documented recovery point objective (RPO).	Full: granular PITR, documented RPO. Partial: daily snapshots. None: latest backup only.	Review recovery documentation; verify RPO	Important
O3.3	Self-service restore	Administrative restore capability without vendor intervention. Granular recovery options for individual items.	Full: admin-initiated, granular recovery. Partial: requires support ticket.	Review restore documentation; check admin capabilities	Important

Support and maintenance

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
O4.1	Documentation quality	Comprehensive, current, and searchable technical documentation. Versioned documentation matching releases.	Full: comprehensive, current, versioned. Partial: incomplete or outdated. Poor: minimal.	Assess documentation during evaluation; check update frequency	Essential
O4.2	Support channels	Available methods for obtaining help including community, email, chat, and phone. Response time commitments.	Document channels and response times by tier	Review support options; check SLA terms	Important
O4.3	Release cadence	Frequency and predictability of updates. Published roadmap and long-term support options.	Full: published roadmap, regular releases, LTS. Partial: irregular releases.	Review release history; check roadmap visibility	Important
O4.4	Community health	Vitality of open source community measured by contributors, commit frequency, and issue response time.	Active: regular commits, responsive maintainers. Declining: slow response, few contributors.	Review repository statistics; assess governance	Important for FOSS

Data management requirements

Data handling, portability, and lifecycle management.

Data import and migration

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
D1.1	Supported import formats	File formats for data import including CSV, JSON, XML, and platform-specific formats.	Full: multiple formats, mapping tools. Partial: limited formats.	Review import documentation; test with sample files	Important
D1.2	Migration tools	Vendor-provided utilities for migrating from common source systems. Data mapping and validation capabilities.	Full: migration tools for major platforms. Partial: generic import only.	Review migration documentation; check platform coverage	Important
D1.3	Data validation on import	Verification of imported data quality. Error reporting and correction workflow.	Full: validation rules, error reporting, preview. Partial: basic validation.	Review validation documentation; test import behaviour	Important

Data export and portability

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
D2.1	Complete data export	Export all organisation data including tasks, projects, comments, attachments, and configuration.	Full: complete export including metadata. Partial: limited data types.	Review export documentation; verify completeness	Essential
D2.2	Export formats	Standard formats for exported data. Open formats preferred (CSV, JSON, XML) over proprietary.	Full: multiple open formats. Partial: single format. Proprietary: vendor-specific only.	Review export format documentation	Essential
D2.3	Scheduled exports	Automated regular data exports. Configurable schedules and destinations.	Full: configurable schedule, multiple destinations. Partial: manual trigger.	Review scheduled export options	Desirable
D2.4	Attachment export	Bulk export of files and documents with preserved folder structure and metadata.	Full: bulk export, structure preserved. Partial: individual download only.	Review file export capabilities	Important

Commercial and contractual requirements

Licensing, pricing, and vendor relationship considerations.

Pricing and licensing

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
C1.1	Pricing transparency	Clear pricing structure without hidden fees. Published pricing or calculator available.	Full: published pricing, calculator, no hidden fees. Partial: pricing on request. Poor: opaque pricing.	Review pricing documentation; request detailed quote	Important
C1.2	Nonprofit pricing	Discounted or donated licences for qualifying organisations. Established programme with clear eligibility.	Full: established programme, significant discount. Partial: ad-hoc discounts. None: standard pricing only.	Research nonprofit programme; verify eligibility	Important
C1.3	Pricing predictability	Ability to forecast costs accurately. Fixed pricing or caps available for usage-based models.	Full: fixed pricing, caps available. Partial: variable but estimable. Poor: unpredictable consumption pricing.	Analyse pricing model; assess variability	Important
C1.4	Open source licence	Licence terms for FOSS options. Copyleft implications and commercial use terms.	Document licence type and implications	Review licence file; assess compatibility	Essential for FOSS

Vendor assessment

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
C2.1	Organisation stability	Financial health and longevity. Funding status, revenue model, and customer base for commercial; maintainer commitment for FOSS.	Assess funding, governance, and sustainability	Research company/project; review governance	Important
C2.2	Jurisdictional factors	Legal jurisdiction and data access implications. Headquarters location and applicable laws.	Document HQ location, applicable laws (CLOUD Act, GDPR)	Review legal documentation; assess data flow	Important
C2.3	Sector experience	Track record with mission-driven organisations. Case studies and sector-specific features.	Evidence: case studies, references, sector features	Request references; review case studies	Desirable

Accessibility requirements

Inclusive design and compliance with accessibility standards.

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
A1.1	WCAG 2.1 compliance	Conformance with Web Content Accessibility Guidelines. Level AA as minimum target.	Full: Level AA documented and tested. Partial: Level A or partial AA. None: no accessibility statement.	Review accessibility statement; test with assistive technology	Important
A1.2	Screen reader compatibility	Functionality with screen reader software including NVDA, JAWS, and VoiceOver.	Full: tested with major screen readers. Partial: basic compatibility.	Test with screen reader during trial	Important
A1.3	Keyboard navigation	Full functionality without mouse. Logical tab order and visible focus indicators.	Full: all features keyboard accessible. Partial: limited keyboard support.	Test keyboard navigation during trial	Important
A1.4	VPAT availability	Voluntary Product Accessibility Template documenting accessibility status. Published VPAT or accessibility roadmap.	Full: VPAT available, roadmap published. Partial: general statement only.	Request VPAT; review accessibility documentation	Important

Assessment methodology

Tools are assessed against each requirement using the following scale:

Rating	Symbol	Definition
Full support	●	Requirement fully met with documented, production-ready capability
Partial support	◐	Requirement partially met; limitations documented in notes
Minimal support	○	Basic capability exists but significant gaps
Not supported	✗	Capability not available
Not applicable	-	Requirement not relevant to this tool
Not assessed	?	Insufficient documentation to assess

Additional notation:

$ indicates feature requires paid tier or add-on
E indicates feature available in enterprise tier only
P indicates feature requires plugin or extension
C indicates community-provided (not vendor-supported)

Functional capability comparison

Task and issue management

Req ID	Requirement	OpenProject	Taiga	Redmine	Kanboard	Jira Software	Asana
F1.1	Task creation and editing	●	●	●	●	●	●
F1.2	Task hierarchy	●	◐	●P	◐	●	●
F1.3	Custom fields	●	●	●	●P	●	●$
F1.4	Task templates	●	✗	✗	✗	●	●
F1.5	Task linking	●	✗	●	●P	●	●
F1.6	Recurring tasks	●E	✗	●P	●P	●$	●
F1.7	Checklists	●	●	✗	●	●	●

Assessment notes:

Taiga F1.2: Supports subtasks within user stories but limited hierarchy depth compared to full task decomposition tools.
Redmine F1.2: Native subtask support is basic; enhanced hierarchy available through plugins such as Issue Relations.
Kanboard F1.2: Single subtask level only; no nested hierarchy.
Jira Software F1.6: Automation rules can create recurring issues but require Automation feature (included in Premium tier).

Project planning and scheduling

Req ID	Requirement	OpenProject	Taiga	Redmine	Kanboard	Jira Software	Asana
F2.1	Gantt chart	●	✗	●	✗	●	●$
F2.2	Milestone tracking	●	●	●	✗	●	●
F2.3	Baseline management	●E	✗	✗	✗	●$	✗
F2.4	Resource scheduling	●E	✗	●P	✗	●$	●$
F2.5	Calendar integration	●	◐	●P	●	●	●
F2.6	Workload management	●E	✗	✗	✗	●$	●$

Assessment notes:

OpenProject F2.1: Interactive Gantt with dependency management included in all editions.
Taiga F2.5: Basic calendar view exists; external calendar sync limited.
Redmine F2.1: Native Gantt chart included; interactivity enhanced through plugins.
Jira Software F2.1: Timeline view available in Premium tier; basic roadmap in Standard.

Agile and Kanban support

Req ID	Requirement	OpenProject	Taiga	Redmine	Kanboard	Jira Software	Asana
F3.1	Kanban boards	●	●	●P	●	●	●
F3.2	Sprint management	●	●	●P	✗	●	◐
F3.3	Backlog management	●	●	●P	✗	●	●
F3.4	Story points	●	●	●P	✗	●	◐
F3.5	Burndown charts	●E	●	●P	✗	●	✗
F3.6	WIP limits	●	●	●P	●	●	◐

Assessment notes:

Taiga F3.1, F3.2: Purpose-built for agile with native Scrum and Kanban support.
Redmine F3.1-F3.5: Agile functionality requires plugins such as Redmine Agile or Agile Board.
Kanboard F3.2: Designed specifically for Kanban; no sprint concept.
Asana F3.2: Basic sprint-like functionality through timeline and milestones; not native Scrum.

Time tracking and reporting

Req ID	Requirement	OpenProject	Taiga	Redmine	Kanboard	Jira Software	Asana
F4.1	Time logging	●	◐	●	●	●	◐
F4.2	Timesheet views	●	✗	●P	◐	●	✗
F4.3	Budget tracking	●E	✗	●P	✗	●$	✗
F4.4	Custom reports	●E	◐	●	◐	●	●$
F4.5	Dashboard widgets	●	●	●P	○	●	●
F4.6	Export formats	●	●	●	●	●	●

Assessment notes:

Taiga F4.1: Basic time tracking exists but less comprehensive than dedicated time tracking tools.
OpenProject F4.2: Timesheet functionality with PDF export included in Community edition.
Asana F4.1: Time tracking requires third-party integration or Asana Premium add-ons.

Collaboration and communication

Req ID	Requirement	OpenProject	Taiga	Redmine	Kanboard	Jira Software	Asana
F5.1	Comments and discussions	●	●	●	●	●	●
F5.2	File attachments	●	●	●	●	●	●
F5.3	Activity streams	●	●	●	●	●	●
F5.4	Notifications	●	●	●	●	●	●
F5.5	Wiki documentation	●	●	●	✗	●	✗
F5.6	Real-time collaboration	●E	○	○	○	●	●

Assessment notes:

OpenProject F5.6: Real-time document collaboration introduced in version 17.0 (January 2026).
Kanboard F5.5: No built-in wiki; external documentation required.
Asana F5.5: No native wiki; project briefs provide basic documentation.

Technical capability comparison

Deployment and hosting

Req ID	Requirement	OpenProject	Taiga	Redmine	Kanboard	Jira Software	Asana
T1.1	Self-hosted	●	●	●	●	✗	✗
T1.2	Cloud/SaaS	●	●	○C	○C	●	●
T1.3	Container deployment	●	●	●C	●	-	-
T1.4	High availability	●	●	●	○	●	●
T1.5	Offline capability	○	○	○	○	○	○

Deployment details:

Tool	Self-hosted infrastructure	Container support	Minimum resources	Cloud regions
OpenProject	Linux (Ubuntu 22.04+, RHEL 8+), PostgreSQL 13+	Official Docker, Helm chart	4 CPU, 8GB RAM, 20GB storage	EU (Germany), custom via self-hosting
Taiga	Linux, PostgreSQL 12+	Official Docker Compose	2 CPU, 4GB RAM, 10GB storage	EU (Spain) via taiga.io, custom via self-hosting
Redmine	Linux/Windows, MySQL 8+ or PostgreSQL 12+	Community Docker images	2 CPU, 2GB RAM, 10GB storage	N/A (self-hosted primarily)
Kanboard	Linux, SQLite/MySQL/PostgreSQL	Official Docker image	1 CPU, 512MB RAM, 1GB storage	N/A (self-hosted only)
Jira Software	SaaS only (Cloud); Data Center being discontinued	N/A	N/A	US, EU, Australia, Singapore
Asana	SaaS only	N/A	N/A	US, EU

Assessment notes:

Jira Software T1.1: Atlassian announced discontinuation of Data Center licensing model; Cloud is the primary offering.
Redmine T1.2: No official SaaS; third-party hosting providers like MyRedmine available.
Kanboard T1.2: No official SaaS; community hosting options exist.

Integration architecture

Req ID	Requirement	OpenProject	Taiga	Redmine	Kanboard	Jira Software	Asana
T3.1	REST API	●	●	●	●	●	●
T3.2	API authentication	OAuth 2.0, API key	API key	API key	API key	OAuth 2.0, API key	OAuth 2.0, PAT
T3.3	Webhooks	●	●	●P	●	●	●
T3.4	Bulk operations	●	◐	◐	◐	●	●
T3.5	Pre-built integrations	25+	10+	100+P	20+P	3000+	200+
T3.6	VCS integration	●	●	●	●	●	◐

API details:

Tool	API documentation	Rate limits	Versioning	SDK availability
OpenProject	docs.openproject.org/api	100 req/15s (configurable)	URL versioning (v3)	Ruby
Taiga	docs.taiga.io/api.html	100 req/min (configurable)	URL versioning	Python, JavaScript
Redmine	redmine.org/projects/redmine/wiki/Rest_api	Configurable	URL versioning	Ruby, Python, PHP
Kanboard	docs.kanboard.org/api	Configurable	JSON-RPC 2.0	Python, PHP, Go
Jira Software	developer.atlassian.com/cloud/jira	Point-based (from March 2026)	URL versioning (v2, v3)	Java, Python, JavaScript, Go
Asana	developers.asana.com	150 req/min (standard)	URL versioning	Python, JavaScript, Ruby, PHP, Java

Security capability comparison

Authentication and access control

Req ID	Requirement	OpenProject	Taiga	Redmine	Kanboard	Jira Software	Asana
S1.1	Multi-factor authentication	●E	○	●P	●P	●	●
S1.2	SSO integration	SAML, OIDC (E)	○	LDAP, ●P	●P	SAML, OIDC	SAML, OIDC ($)
S1.3	Role-based access control	●	●	●	●	●	●
S1.4	Project-level permissions	●	●	●	●	●	●
S1.5	Session management	●	◐	●	●	●	●
S1.6	IP allowlisting	●E	✗	●P	✗	●E	●$

MFA methods supported:

Tool	TOTP	WebAuthn/FIDO2	Push	SMS	Email
OpenProject	●E	●E	✗	✗	✗
Taiga	✗	✗	✗	✗	✗
Redmine	●P	●P	✗	✗	✗
Kanboard	●P	✗	✗	✗	✗
Jira Software	●	●	●	✗	●
Asana	●	●	✗	✗	✗

Assessment notes:

OpenProject S1.1, S1.2: MFA and SSO require Enterprise edition.
Taiga S1.1: Native MFA not available; relies on IdP-provided MFA through SSO.
Redmine S1.1, S1.2: MFA and advanced SSO require plugins (redmine_two_fa, redmine_omniauth_saml).

Data protection

Req ID	Requirement	OpenProject	Taiga	Redmine	Kanboard	Jira Software	Asana
S2.1	Encryption at rest	●	●	●	●*	●	●
S2.2	Encryption in transit	TLS 1.2+	TLS 1.2+	TLS 1.2+	TLS 1.2+	TLS 1.2+	TLS 1.3
S2.3	Audit logging	●	◐	●	●	●	●
S2.4	Data residency	●	●	●	●	●E	●$

*Self-hosted depends on infrastructure configuration

Security certifications

Certification	OpenProject	Taiga	Redmine	Kanboard	Jira Software	Asana
SOC 2 Type II	● (Cloud)	✗	N/A	N/A	●	●
ISO 27001	●	✗	N/A	N/A	●	●
GDPR compliance	●	●	N/A	N/A	●	●

Assessment notes:

Redmine, Kanboard: Self-hosted tools; certifications depend on hosting organisation’s practices.
OpenProject: ISO 27001 and SOC 2 apply to Cloud edition; self-hosted inherits organisation’s certifications.

Operational capability comparison

Administration and monitoring

Req ID	Requirement	OpenProject	Taiga	Redmine	Kanboard	Jira Software	Asana
O1.1	Admin interface	●	●	●	●	●	●
O1.2	Configuration as code	●	●	◐	●	◐	✗
O1.3	Multi-tenancy	●E	✗	●P	✗	●	●
O1.4	Localisation	40+	20+	50+	30+	20+	30+
O2.1	Health endpoints	●	◐	○	●	●	●
O2.2	Metrics export	Prometheus	✗	✗	✗	Proprietary	Proprietary
O2.3	Log export	●	●	●	●	●	●

Backup and support

Req ID	Requirement	OpenProject	Taiga	Redmine	Kanboard	Jira Software	Asana
O3.1	Automated backup	●	●	●	●	●	●
O3.2	Point-in-time recovery	●E	◐	●	◐	●	●
O3.3	Self-service restore	●	●	●	●	◐	✗
O4.1	Documentation quality	Excellent	Good	Good	Good	Excellent	Excellent

Support comparison

Aspect	OpenProject	Taiga	Redmine	Kanboard	Jira Software	Asana
Community forum	● Active	● Active	● Active	● Active	● Vendor-moderated	● Vendor-moderated
Email support	●E	●$	Community	Community	●	●
Phone support	●E	✗	✗	✗	●E	●$
SLA availability	●E	●$	✗	✗	●	●
Typical response (critical)	4 hours (E)	24 hours ($)	Community	Community	1 hour	4 hours

Data management comparison

Import and export

Req ID	Requirement	OpenProject	Taiga	Redmine	Kanboard	Jira Software	Asana
D1.1	Import formats	CSV, XML	CSV, JSON	CSV, XML	JSON	CSV, JSON	CSV
D1.2	Migration tools	Jira, MS Project	Jira, Trello, GitHub, Asana	✗	Trello, Kanboard JSON	Extensive	Limited
D1.3	Data validation	●	●	◐	◐	●	●
D2.1	Complete data export	●	●	●	●	●	●
D2.2	Export formats	CSV, PDF, XLS	CSV, JSON	CSV, PDF	JSON	CSV, XML	CSV, JSON
D2.3	Scheduled exports	●	✗	✗	✗	●	✗
D2.4	Attachment export	●	●	●	●	●	●

Migration sources:

Tool	Jira	Trello	Asana	MS Project	GitHub/GitLab
OpenProject	●	◐	✗	●	✗
Taiga	●	●	●	✗	●
Redmine	✗	✗	✗	✗	✗
Kanboard	✗	●	✗	✗	✗
Jira Software	-	●	●	●	●
Asana	●	●	-	✗	✗

Commercial comparison

Pricing models

Tool	Type	Model	Free tier	Nonprofit programme
OpenProject	Open source	Free + Enterprise	● Full Community edition	N/A (free)
Taiga	Open source	Freemium	● Self-hosted; ◐ Cloud (limited)	50% discount
Redmine	Open source	Free	● Full product	N/A (free)
Kanboard	Open source	Free	● Full product	N/A (free)
Jira Software	Commercial	Per-user subscription	◐ 10 users	75% discount (Atlassian Foundation)
Asana	Commercial	Per-user subscription	◐ 10 users (Basic)	50% discount

Pricing detail

OpenProject

Edition	Price	Key features	Limitations
Community	Free	Gantt, Kanban, time tracking, wiki, API	No SSO, MFA, baseline, enterprise support
Enterprise Cloud	€5.95/user/month	SSO, MFA, 2FA, enhanced security, support	Hosted in EU only
Enterprise On-Premises	€5.95/user/month	All features, self-hosted, priority support	Requires own infrastructure

Taiga

Edition	Price	Key features	Limitations
Self-hosted	Free	Full functionality	Requires own infrastructure
Cloud	€7/user/month	Managed hosting, support	Limited customisation

Jira Software

Tier	Price (Cloud)	Key features	Limitations
Free	£0	Basic Kanban/Scrum, 10 users	2GB storage, limited automation
Standard	£8.15/user/month	Audit logs, 250GB storage	No advanced roadmaps
Premium	£16/user/month	Advanced roadmaps, automation, unlimited storage	-
Enterprise	Custom	Unlimited sites, advanced security	Annual commitment

Nonprofit programme: 75% discount through Atlassian Foundation for registered nonprofits.

Asana

Tier	Price	Key features	Limitations
Basic	Free	Tasks, projects, 10 users	Limited views, no timeline
Premium	£10.99/user/month	Timeline, custom fields, forms	No portfolios
Business	£24.99/user/month	Portfolios, goals, workload	No advanced security
Enterprise	Custom	Admin controls, SAML, support	Annual commitment

Nonprofit programme: 50% discount for qualifying organisations through Asana for Nonprofits.

Vendor details

Tool	Organisation	Founded	HQ location	Business model
OpenProject	OpenProject GmbH	2012	Berlin, Germany	Open core, enterprise subscription
Taiga	Kaleidos Ventures SL	2014	Madrid, Spain	Open source, SaaS subscription
Redmine	Community-maintained	2006	N/A	Volunteer open source
Kanboard	Community-maintained	2014	N/A	Volunteer open source (maintenance mode)
Jira Software	Atlassian Corporation	2002	Sydney, Australia (US-listed)	Commercial SaaS
Asana	Asana, Inc.	2008	San Francisco, USA	Commercial SaaS

Jurisdictional considerations:

Jira Software (US-listed, Australian HQ): Subject to CLOUD Act via US listing. Data stored in US, EU, Australia, or Singapore regions depending on selection.
Asana (US HQ): Subject to CLOUD Act. Data centres in US and EU.
OpenProject (Germany HQ): EU jurisdiction; GDPR as primary framework. EU Cloud option available.
Taiga (Spain HQ): EU jurisdiction; GDPR as primary framework.
Redmine, Kanboard: Self-hosted; jurisdiction determined by hosting organisation.

Accessibility comparison

Req ID	Requirement	OpenProject	Taiga	Redmine	Kanboard	Jira Software	Asana
A1.1	WCAG 2.1 compliance	AA (partial)	Not stated	Not stated	Not stated	AA	AA
A1.2	Screen reader tested	●	○	○	○	●	●
A1.3	Keyboard navigation	●	◐	◐	◐	●	●
A1.4	VPAT available	●	✗	✗	✗	●	●

Assessment notes:

OpenProject: Significant accessibility improvements in 2025 releases including dark mode and high contrast options.
Taiga, Redmine, Kanboard: No formal accessibility statements; community-reported compatibility varies.
Jira Software, Asana: Published VPATs and documented accessibility features.

Detailed tool assessments

OpenProject

Type: Open source with enterprise tier
Licence: GNU GPL v3 (Community edition); proprietary Enterprise add-ons
Current version: 17.0 (released 2026-01-14)
Deployment options: Self-hosted (Linux), Docker, Kubernetes, managed Cloud
Source repository: github.com/opf/openproject
Documentation: docs.openproject.org

Overview

OpenProject provides comprehensive project management combining traditional waterfall planning with agile methodologies. The platform centres on work packages (the unified work item concept), Gantt chart scheduling, and team collaboration features. Development is led by OpenProject GmbH in Berlin with active community contribution.

The architecture follows a monolithic Ruby on Rails application with PostgreSQL backend. Version 17.0 introduced real-time collaborative document editing through the BlockNote editor, representing a significant enhancement to team collaboration capabilities. The platform emphasises data sovereignty with EU-hosted Cloud options and comprehensive self-hosting documentation.

OpenProject positions itself as the open source alternative to commercial platforms, with explicit migration tooling from Microsoft Project and Jira. The 2025 recognition by Gartner Digital Markets and discontinuation of Atlassian Data Center has driven increased adoption among organisations seeking alternatives with greater control.

Capability assessment

OpenProject delivers strong traditional project management with interactive Gantt charts, dependency tracking, and resource management. The work package system unifies tasks, features, bugs, and milestones under a consistent interface with configurable types and workflows.

Agile support includes Kanban boards and backlog management, though the implementation reflects traditional PM origins rather than agile-first design. Sprint velocity tracking and burndown charts require Enterprise edition. The meeting module with agenda management and recurring meetings provides integrated collaboration beyond task tracking.

Time tracking integrates throughout the platform with multiple entry methods, cost types, and budget tracking (Enterprise). The API covers all platform capabilities, enabling deep integration with development and business systems.

Key strengths:

Interactive Gantt charts: Drag-and-drop scheduling with automatic dependency recalculation, baseline comparison (Enterprise), and critical path visibility. The implementation rivals commercial alternatives.
Data sovereignty: EU-hosted Cloud option, comprehensive self-hosting documentation, and full data export ensure organisational control over project data.
Comprehensive time tracking: Built-in time logging with cost tracking, timesheet views, and PDF export supports both internal management and client billing.
Active development: 28 releases in 2025 with substantial feature additions including real-time collaboration, improved accessibility, and meeting enhancements.

Key limitations:

Enterprise feature gating: SSO, MFA, baseline management, and advanced reporting require Enterprise licence. Organisations needing security features face commercial commitment.
Agile maturity: Scrum support exists but lacks depth of purpose-built agile tools. Sprint planning and velocity tracking are adequate but not exceptional.
Learning curve: Interface density reflects feature depth; new users require orientation time. Documentation is comprehensive but extensive.
Mobile experience: Web-responsive design works on mobile; dedicated mobile application in development but not yet publicly available.

Deployment and operations

Self-hosted requirements:

Operating system: Ubuntu 22.04/24.04 LTS, Debian 11/12, RHEL 8/9, SLES 15
Database: PostgreSQL 13+ (14+ recommended)
Runtime: Ruby 3.2, Node.js 18+
Minimum resources: 4 CPU cores, 8GB RAM, 20GB storage
Recommended resources: 8 CPU cores, 16GB RAM, 100GB storage

Deployment complexity: Medium. Package-based installation (DEB/RPM) simplifies deployment; Docker and Helm charts available for containerised environments. Configuration through environment variables or YAML files.

Operational overhead: Medium. Regular updates required (monthly releases); automated backup configuration included in packages. Monitoring through Prometheus metrics export.

Upgrade path: Minor versions typically upgrade without breaking changes. Major versions (annually) may require migration steps documented in release notes. No LTS releases; continuous incremental updates preferred.

Integration capabilities

API coverage: Comprehensive REST API (v3) covering all platform objects. HAL+JSON responses with hypermedia links. OAuth 2.0 and API token authentication.

Key integrations:

Integration	Type	Status	Documentation
Nextcloud	Native (bidirectional)	Production	docs.openproject.org/system-admin-guide/integrations/nextcloud/
Microsoft 365 / SharePoint	Native (files)	Production	docs.openproject.org/system-admin-guide/integrations/one-drive/
GitHub/GitLab	Native (commits, PRs)	Production	docs.openproject.org/system-admin-guide/integrations/github/
Microsoft Project	Import	Production	docs.openproject.org/user-guide/projects/project-settings/import/
Jira	Import	Production	docs.openproject.org/user-guide/projects/project-settings/import/

Security assessment

Authentication: Password with configurable complexity, LDAP integration (Community), SAML 2.0 and OIDC (Enterprise), TOTP and WebAuthn MFA (Enterprise).

Authorisation: Role-based permissions with global roles and project-specific membership. Custom roles with granular permission assignment. Work package-level access through project membership inheritance.

Data protection: TLS 1.2+ enforced, encryption at rest configurable (infrastructure-dependent for self-hosted), comprehensive audit logging of user actions.

Security track record: Participates in YesWeHack bug bounty programme funded by European Commission. CVEs addressed promptly with security releases (e.g., CVE-2026-22601 through CVE-2026-22605 addressed in December 2025).

Certifications: SOC 2 Type II and ISO 27001 for Cloud edition.

Cost analysis

Direct costs:

Community edition: Free
Enterprise Cloud: €5.95/user/month (annual billing)
Enterprise On-Premises: €5.95/user/month (annual billing)

Infrastructure costs (self-hosted):

Scale	Infrastructure estimate	Notes
Small (<50 users)	£50-150/month	Small VPS or on-premises server
Medium (50-500 users)	£200-500/month	Dedicated server or managed PostgreSQL
Large (500+ users)	£500-2000/month	High availability configuration, load balancing

Hidden costs:

LDAP/SSO integration: Requires Enterprise for SSO; organisations may need Enterprise solely for identity integration.
Backup infrastructure: Self-hosted requires separate backup solution; Cloud includes automated backups.

Organisational fit

Best suited for:

Organisations requiring traditional project management with Gantt charts alongside agile boards
Teams prioritising data sovereignty with EU hosting or self-hosted deployment
Organisations migrating from Microsoft Project or seeking Jira alternatives with open source option

Less suitable for:

Teams needing exclusively agile tooling; purpose-built tools like Taiga or Jira offer deeper Scrum support
Small teams needing quick setup without IT capacity for self-hosting

Migration considerations:

Migrating to OpenProject: Import tools available for Jira and MS Project. CSV import for generic sources. API enables custom migration scripts.
Migrating from OpenProject: Full data export via API. Export formats include CSV, XML, and PDF.

Taiga

Type: Open source
Licence: MPL 2.0 (backend), AGPL 3.0 (frontend)
Current version: 6.9.0 (released 2025-10)
Deployment options: Self-hosted (Docker), managed Cloud (taiga.io)
Source repository: github.com/taigaio
Documentation: docs.taiga.io

Overview

Taiga delivers agile project management designed for cross-functional teams using Scrum, Kanban, or hybrid approaches. Developed by Kaleidos in Madrid, the platform emphasises visual design and usability over feature breadth. The architecture separates frontend (AngularJS/CoffeeScript) from backend (Django/Python), communicating via REST API.

The platform won the 2015 Most Valued Agile Tool award and maintains active development with version 6.x focusing on stability and refinement. Taiga aims to provide an intuitive alternative to complex enterprise tools, prioritising team experience over administrative flexibility.

Capability assessment

Taiga excels at agile workflows with native Scrum and Kanban support. Sprint planning, backlog management, and burndown charts work seamlessly. The Kanban board implementation includes WIP limits, swimlanes, and customisable columns. User stories, tasks, and issues follow agile terminology throughout.

Traditional project management features are limited. No Gantt chart exists; timeline visibility relies on sprint boundaries. Milestone support exists but lacks dependency tracking. Time tracking is basic compared to dedicated tools.

Integration capabilities focus on development workflows with GitHub, GitLab, and Bitbucket connections. Import tools cover migration from Jira, Trello, GitHub Issues, and Asana, reflecting the target user base.

Key strengths:

Agile-first design: Scrum and Kanban implementations feel native rather than bolted-on. Sprint planning, velocity tracking, and burndown charts integrate naturally.
Visual interface: Clean, modern design reduces cognitive load. Drag-and-drop interactions throughout. Interface translated into 20+ languages.
Import flexibility: Migration tools for major platforms (Jira, Trello, Asana, GitHub) ease transition for teams switching tools.
Cost-effective: Full functionality in self-hosted deployment. Cloud pricing competitive with commercial alternatives.

Key limitations:

No traditional PM features: Absence of Gantt charts, dependency tracking, and baseline management limits use for waterfall or hybrid methodologies.
Limited enterprise features: No native MFA, limited SSO support, no advanced access controls. Security relies on infrastructure-level controls.
Basic time tracking: Time logging exists but lacks timesheets, budget tracking, and billing features.
SaaS limitations: Cloud edition lacks customisation options available in self-hosted deployment.

Deployment and operations

Self-hosted requirements:

Operating system: Linux (Docker-based deployment)
Database: PostgreSQL 12+
Runtime: Python 3.8+, Node.js (for frontend build)
Minimum resources: 2 CPU cores, 4GB RAM, 10GB storage
Recommended resources: 4 CPU cores, 8GB RAM, 50GB storage

Deployment complexity: Low-Medium. Docker Compose deployment simplifies installation. Configuration through environment variables.

Operational overhead: Low. Stable platform with infrequent updates. Backup through standard PostgreSQL tools.

Upgrade path: Version upgrades documented with migration scripts. Breaking changes rare in 6.x series.

Cost analysis

Direct costs:

Self-hosted: Free
Cloud Premium: €7/user/month

Infrastructure costs (self-hosted):

Scale	Infrastructure estimate	Notes
Small (<50 users)	£30-80/month	Small VPS sufficient
Medium (50-200 users)	£100-250/month	Moderate server resources

Nonprofit programme: 50% discount on Cloud pricing for qualifying organisations.

Organisational fit

Best suited for:

Agile-focused teams using Scrum or Kanban methodologies
Software development teams wanting integrated VCS connection
Teams prioritising usability over feature depth

Less suitable for:

Organisations requiring Gantt charts, dependency tracking, or traditional project management
Teams needing advanced security features (MFA, SSO) without infrastructure-level implementation

Redmine

Type: Open source
Licence: GNU GPL v2
Current version: 6.1.1 (released 2026-01-06)
Deployment options: Self-hosted (Linux/Windows)
Source repository: github.com/redmine/redmine (mirror), svn.redmine.org
Documentation: redmine.org/projects/redmine/wiki

Overview

Redmine provides flexible project management with extensive customisation through plugins. Built on Ruby on Rails, the platform has served organisations since 2006 with continuous community development. The architecture supports multiple databases (MySQL, PostgreSQL, SQLite) and deployment models.

Core functionality includes issue tracking, Gantt charts, calendar, wiki, forums, and time tracking. The plugin ecosystem extends capabilities significantly, with over 1,000 plugins addressing agile boards, advanced reporting, automation, and integrations.

Redmine’s longevity creates both strength (maturity, stability) and challenge (dated interface, technical debt). Recent releases (6.x) modernised the codebase with Ruby 3.4 support, SVG icons, and CommonMark formatting.

Capability assessment

Core Redmine delivers solid issue tracking with customisable trackers (issue types), workflows, and custom fields. The Gantt chart provides read-only visualisation; interactive editing requires plugins. Wiki documentation integrates well with project structure.

Agile functionality requires plugins. Options include Redmine Agile (commercial), Agile Board (free), and SCRUM plugin. Plugin quality varies; evaluation required.

The plugin ecosystem is both strength and liability. Extensive functionality available but plugin compatibility, maintenance, and quality require assessment. Core updates may break plugin compatibility.

Key strengths:

Flexibility: Highly customisable through trackers, workflows, custom fields, and plugins. Adaptable to diverse organisational needs.
Plugin ecosystem: Extensive functionality available through plugins covering agile, reporting, integrations, and automation.
Maturity: Long production history with proven stability. Large user base and community knowledge.
Multi-database support: PostgreSQL, MySQL/MariaDB, SQLite. Deployment flexibility for existing infrastructure.

Key limitations:

Dated interface: Visual design reflects 2006 origins. User experience lags modern tools significantly.
Plugin dependency: Core functionality limited; agile, advanced reporting, and integrations require plugins with varying quality and maintenance.
No official SaaS: Self-hosted only; third-party hosting available but not vendor-supported.
Technical learning curve: Ruby on Rails deployment, plugin management, and customisation require technical expertise.

Deployment and operations

Self-hosted requirements:

Operating system: Linux (Ubuntu, Debian, RHEL) or Windows
Database: MySQL 8+, MariaDB 10.4+, PostgreSQL 12+, SQLite
Runtime: Ruby 3.1-3.4
Minimum resources: 2 CPU cores, 2GB RAM, 10GB storage
Recommended resources: 4 CPU cores, 4GB RAM, 50GB storage

Deployment complexity: Medium. Installation documented but requires Ruby environment configuration. Packages available for some distributions.

Operational overhead: Medium. Core updates straightforward; plugin compatibility testing required. Backup through standard database tools.

Cost analysis

Direct costs:

Redmine core: Free
Commercial plugins: Variable (Redmine Agile: €159-899/server)

Infrastructure costs (self-hosted):

Scale	Infrastructure estimate	Notes
Small (<100 users)	£30-100/month	Basic server sufficient
Medium (100-500 users)	£100-300/month	Moderate resources

Organisational fit

Best suited for:

Organisations with Ruby/Rails expertise seeking highly customisable issue tracking
Teams comfortable with plugin evaluation and management
Long-running deployments where migration cost exceeds modernisation benefit

Less suitable for:

Organisations without technical capacity for self-hosting and plugin management
Teams requiring modern user interface and agile-first workflows

Kanboard

Type: Open source (maintenance mode)
Licence: MIT
Current version: 1.2.49 (released 2026-01-06)
Deployment options: Self-hosted (PHP)
Source repository: github.com/kanboard/kanboard
Documentation: docs.kanboard.org

Overview

Kanboard focuses exclusively on Kanban methodology with minimal complexity. The PHP application runs on standard web hosting without elaborate infrastructure. Development is in maintenance mode, meaning no major new features but continued bug fixes and community contributions.

The platform provides customisable Kanban boards, task management, swimlanes, and WIP limits. Simplicity is intentional; Kanboard avoids feature creep in favour of focused functionality.

Capability assessment

Kanboard delivers effective Kanban boards with columns, swimlanes, WIP limits, and task cards. Time tracking, comments, and subtasks exist at appropriate depth. The plugin system extends functionality for integrations and customisations.

Missing features include Gantt charts, sprint management, milestones, and advanced reporting. These omissions are by design; Kanboard targets teams wanting Kanban without project management complexity.

Key strengths:

Simplicity: Focused Kanban without unnecessary complexity. Quick to deploy and learn.
Lightweight requirements: PHP/SQLite deployment runs on basic hosting. Minimal resource consumption.
MIT licence: Permissive licence enables any use without copyleft requirements.
Continued maintenance: Regular releases despite maintenance mode. Security fixes applied promptly.

Key limitations:

Kanban only: No Gantt, sprints, milestones, or traditional PM features. Single methodology focus.
Maintenance mode: No major new features expected. Community-driven development only.
Limited enterprise features: Basic authentication; SSO requires plugins. No native MFA.
Self-hosted only: No official SaaS option.

Deployment and operations

Self-hosted requirements:

Operating system: Linux (any), Windows
Database: SQLite, MySQL, PostgreSQL
Runtime: PHP 7.4+
Minimum resources: 1 CPU core, 512MB RAM, 1GB storage
Recommended resources: 2 CPU cores, 2GB RAM, 10GB storage

Deployment complexity: Low. Standard PHP application; Apache/Nginx configuration. SQLite requires no database server.

Operational overhead: Low. Stable application with infrequent updates. Minimal maintenance requirements.

Cost analysis

Direct costs: Free

Infrastructure costs:

Scale	Infrastructure estimate	Notes
Any size	£10-50/month	Runs on basic shared hosting

Organisational fit

Best suited for:

Small teams wanting simple Kanban without complexity
Organisations with basic hosting but no dedicated IT staff
Teams wanting quick deployment with minimal learning curve

Less suitable for:

Organisations needing project planning, timelines, or reporting
Teams requiring enterprise security features

Jira Software

Type: Commercial
Current version: Cloud (continuous deployment)
Deployment options: Cloud (primary); Data Center being discontinued
Documentation: support.atlassian.com/jira-software-cloud/
API documentation: developer.atlassian.com/cloud/jira/

Overview

Jira Software is the market-leading project management platform for software development teams. Atlassian’s Cloud-first strategy means new features deploy continuously; Data Center (self-hosted) is being phased out with end of support announced.

The platform provides comprehensive issue tracking, agile boards (Scrum and Kanban), roadmaps, automation, and extensive integration ecosystem. The Atlassian Marketplace offers 3,000+ apps extending functionality.

Jira’s complexity reflects extensive capability. Power users leverage advanced JQL queries, automation rules, and custom workflows; casual users face steep learning curves.

Capability assessment

Jira delivers comprehensive agile project management with native Scrum boards, Kanban boards, backlog management, and sprint planning. Advanced roadmaps (Premium tier) provide cross-project planning and dependency tracking. The automation engine handles complex workflow rules.

Issue types, workflows, screens, and fields customise extensively. The flexibility enables sophisticated configurations but requires deliberate governance to prevent complexity accumulation.

Integration breadth is unmatched. Native connections to Atlassian products (Confluence, Bitbucket) plus marketplace apps for virtually any system. Forge development platform enables custom extensions.

Key strengths:

Comprehensive agile support: Native Scrum and Kanban with depth exceeding most alternatives. Sprint planning, velocity, burndown, and capacity planning included.
Advanced automation: Rule-based automation handles task assignment, status updates, notifications, and cross-project coordination. Premium tier includes unlimited automation.
Integration ecosystem: 3,000+ marketplace apps. Native DevOps integrations with CI/CD pipelines, monitoring, and deployment tracking.
Enterprise scale: Handles thousands of users and millions of issues. Global infrastructure with regional data residency.

Key limitations:

Pricing complexity: Per-user pricing with tier-gated features creates cost unpredictability as needs expand. Premium features require significant uplift.
Learning curve: Interface complexity and configuration depth require substantial onboarding investment. Casual users struggle without training.
Cloud dependency: Data Center discontinuation removes self-hosted option. Cloud-only creates jurisdiction and connectivity dependencies.
CLOUD Act exposure: US-listed company subject to CLOUD Act regardless of data residency selection.

Cost analysis

Direct costs:

Free: 10 users, basic features
Standard: £8.15/user/month (100 users tier)
Premium: £16/user/month (100 users tier)
Enterprise: Custom pricing

Nonprofit programme: 75% discount through Atlassian Foundation. Requires annual application and verification.

Organisational fit

Best suited for:

Software development teams with DevOps integration requirements
Large organisations with dedicated Jira administrators
Teams already using Atlassian ecosystem (Confluence, Bitbucket)

Less suitable for:

Organisations prioritising data sovereignty; Cloud-only model limits control
Small teams without budget for Premium features or Marketplace apps
Teams seeking simplicity over capability depth

Asana

Type: Commercial
Current version: SaaS (continuous deployment)
Deployment options: Cloud only
Documentation: help.asana.com
API documentation: developers.asana.com

Overview

Asana provides work management for cross-functional teams spanning project management, workflow coordination, and goal tracking. The platform emphasises accessibility for non-technical users while offering depth for power users through features like custom rules, portfolios, and goals.

Asana’s design philosophy prioritises task clarity and team visibility. Views include lists, boards, timelines, and calendars showing the same underlying data. The “Work Graph” connects tasks, projects, portfolios, and goals into organisational hierarchy.

Capability assessment

Asana handles task and project management with intuitive list and board views. Timeline view (Premium) provides Gantt-like visualisation. Forms capture structured requests; templates standardise project setup.

Agile support is implicit rather than explicit. No native sprint concept exists; teams adapt using sections, milestones, and custom fields. Kanban boards work well; Scrum requires workarounds.

Portfolios and Goals (Business tier) enable programme-level oversight. Workload view shows team capacity. Custom rules automate routine operations. Integration through native connectors and API.

Key strengths:

User experience: Clean interface accessible to non-technical users. Low onboarding friction for basic usage.
Flexible views: Same data visible as list, board, timeline, or calendar. View switching without data migration.
Cross-functional focus: Designed for marketing, operations, and business teams alongside software development.
Goal alignment: Goals feature (Business) connects work to organisational objectives.

Key limitations:

No native agile: Sprint management, velocity tracking, and burndown charts absent. Scrum implementation requires adaptation.
Feature gating: Timeline (Gantt), custom fields, and portfolios require Premium or Business tiers. Basic tier is limited.
No self-hosting: Cloud-only deployment without data sovereignty options beyond regional selection.
CLOUD Act exposure: US company subject to CLOUD Act.

Cost analysis

Direct costs:

Basic: Free (10 users)
Premium: £10.99/user/month
Business: £24.99/user/month
Enterprise: Custom

Nonprofit programme: 50% discount through Asana for Nonprofits. Verification required.

Organisational fit

Best suited for:

Cross-functional teams (marketing, operations) alongside technical teams
Organisations prioritising ease of use over methodology depth
Teams wanting goal-to-task alignment visibility

Less suitable for:

Scrum teams needing native sprint management
Organisations requiring self-hosted deployment

Selection guidance

Decision framework

Use this framework to narrow options based on primary constraints:

                                   START
                                     |
                                     v
                    +--------------------------------+
                    | Must data stay in-jurisdiction |
                    | with full control?             |
                    +---------------+----------------+
                                    |
                    +---------------+----------------+
                    |                                |
                    v                                v
                   YES                              NO
                    |                                |
                    v                                v
         +------------------+            +----------------------+
         | Self-hosted      |            | Do you have IT       |
         | options only:    |            | capacity to manage   |
         | OpenProject,     |            | self-hosted?         |
         | Taiga, Redmine,  |            +-----------+----------+
         | Kanboard         |                        |
         +------------------+            +-----------+-----------+
                                         |                       |
                                         v                       v
                                        YES                     NO
                                         |                       |
                                         v                       v
                              +------------------+    +------------------+
                              | Evaluate all:    |    | Cloud options:   |
                              | All 6 tools      |    | OpenProject      |
                              +------------------+    | Cloud, Taiga.io, |
                                                      | Jira, Asana      |
                                                      +------------------+

                              METHODOLOGY CHECK
                                     |
                                     v
                    +--------------------------------+
                    | Primary methodology?           |
                    +--------------------------------+
                                     |
         +---------------+-----------+-----------+---------------+
         |               |                       |               |
         v               v                       v               v
      SCRUM         KANBAN              TRADITIONAL         HYBRID
         |               |                       |               |
         v               v                       v               v
+----------------+ +----------------+ +------------------+ +----------------+
| Taiga,         | | Kanboard,      | | OpenProject,     | | OpenProject,   |
| Jira           | | Taiga,         | | Redmine          | | Jira           |
|                | | OpenProject    |                    |                  |
+----------------+ +----------------+ +------------------+ +----------------+

Recommendations by organisational context

For organisations with minimal IT capacity

Primary recommendation: Asana (Premium tier)

Asana provides the most accessible entry point for teams without dedicated IT staff. The intuitive interface requires minimal training. Premium tier at £10.99/user/month includes timeline, custom fields, and forms essential for project management. No infrastructure to maintain; updates automatic.

Trade-offs: Cloud-only limits data control. US jurisdiction means CLOUD Act exposure. Premium features (timeline, custom fields) require paid tier. No native agile methodology support.

Configuration notes: Start with free tier to validate fit before Premium commitment. Enable Forms for intake processes. Use Templates to standardise project setup.

Alternative: OpenProject Cloud

For organisations preferring EU data residency and open source principles, OpenProject Cloud at €5.95/user/month provides managed hosting without infrastructure burden. Trade-off is more complex interface requiring orientation time.

For organisations with established IT capacity

Primary recommendation: OpenProject (self-hosted Enterprise)

Self-hosted deployment provides data sovereignty, integration flexibility, and feature customisation unavailable in SaaS platforms. Enterprise edition adds SSO/MFA, baseline management, and enterprise support. Total cost often lower than per-user SaaS pricing at scale.

Trade-offs: Requires infrastructure management, backup procedures, and update discipline. Enterprise licence required for SSO/MFA even if other Enterprise features unnecessary.

Configuration notes: Deploy using Docker or Helm for consistent environments. Configure Prometheus metrics export for monitoring integration. Implement SAML/OIDC for identity provider connection.

Alternative: Redmine with plugins

For organisations with Ruby expertise and highly specific requirements, Redmine with curated plugins provides maximum customisation. Trade-off is plugin management overhead and dated interface.

For organisations with specific constraints

Strict data sovereignty requirements:

Recommendation: OpenProject (self-hosted) or Redmine
Rationale: Self-hosted deployment keeps data entirely within organisational control. No vendor access to data at rest.
Configuration notes: Deploy in secured network segment. Implement encryption at rest through infrastructure. Document data flows for compliance evidence.

Software development teams (DevOps focus):

Recommendation: Jira Software (Premium)
Rationale: Native integration with Bitbucket, Confluence, and CI/CD tools. Marketplace apps cover virtually any DevOps toolchain.
Configuration notes: Implement Jira Software with Bitbucket for full commit traceability. Use Automation for deployment status updates.

Agile-only teams (Scrum/Kanban):

Recommendation: Taiga (self-hosted)
Rationale: Purpose-built for agile methodologies. Clean implementation of Scrum and Kanban without PM feature overhead.
Configuration notes: Docker Compose deployment simplifies installation. Import from Jira or Trello if migrating existing data.

Minimal budget:

Recommendation: Kanboard (self-hosted)
Rationale: MIT-licensed, runs on basic PHP hosting. Focused Kanban without complexity.
Configuration notes: SQLite database requires no separate database server. Deploy on shared hosting for lowest cost.

Migration paths

From	To	Complexity	Approach	Typical timeline
Jira	OpenProject	Medium	Use OpenProject Jira importer. Map issue types to work package types.	2-4 weeks
Jira	Taiga	Low	Taiga includes Jira importer. Focuses on user stories and tasks.	1-2 weeks
Trello	Taiga	Low	Native importer available. Board structure maps directly.	1 week
Trello	Kanboard	Low	Native importer available. Simple board migration.	1 week
MS Project	OpenProject	Medium	MPP import available. Complex dependencies may need adjustment.	2-4 weeks
Asana	OpenProject	Medium	CSV export from Asana, CSV import to OpenProject. Custom field mapping required.	2-4 weeks
Spreadsheets	Any	Variable	CSV import available in all tools. Data cleanup typically required.	1-4 weeks

External resources

Official documentation

Open source projects

Tool	Documentation	Repository	Issue tracker	Community
OpenProject	docs.openproject.org	github.com/opf/openproject	community.openproject.org	community.openproject.org
Taiga	docs.taiga.io	github.com/taigaio	github.com/taigaio/taiga-back/issues	community.taiga.io
Redmine	redmine.org/projects/redmine/wiki	svn.redmine.org (github mirror)	redmine.org/issues	redmine.org/projects/redmine/boards
Kanboard	docs.kanboard.org	github.com/kanboard/kanboard	github.com/kanboard/kanboard/issues	github.com/kanboard/kanboard/discussions

Commercial products

Tool	Documentation	API reference	Nonprofit programme	Trust centre	Status page
Jira Software	support.atlassian.com/jira-software-cloud/	developer.atlassian.com/cloud/jira/	atlassian.com/software/views/community-license-request	atlassian.com/trust	status.atlassian.com
Asana	help.asana.com	developers.asana.com	asana.com/nonprofit	asana.com/trust	status.asana.com

Relevant standards

Standard	Description	URL
WCAG 2.1	Web Content Accessibility Guidelines	w3.org/WAI/WCAG21/quickref/
ISO 21500	Guidance on project management	iso.org/standard/50003.html
PMBOK	Project Management Body of Knowledge	pmi.org/pmbok-guide-standards