Work Ops

Project management, task tracking, sprints, and team collaboration — built into the platform.

What Is Work Ops?

Work Ops is Bosca's integrated project management system. It provides everything a team needs to plan, track, and deliver work — from individual task assignments to portfolio-level roadmaps — without leaving the platform or relying on external tools.

Think of it as a full-featured project management suite comparable to Jira or Azure DevOps, but tightly woven into Bosca so that your content, analytics, experiments, and work tracking all live under one roof. Teams can adopt lightweight Kanban workflows or run disciplined Scrum sprints, and managers get the visibility they need through dashboards, burndown charts, and cross-project reporting.

Organizational Hierarchy

Work in Bosca is organized in a four-tier hierarchy that mirrors how most organizations think about delivery:

This hierarchy lets individual contributors focus on their project's backlog while team leads see program-level progress and executives track portfolio-level health — all from the same data, just at different zoom levels.

Key Capabilities

Task Tracking

Every piece of work is represented as a task with a globally unique key (like BOS-42). Tasks carry all the information your team needs: type, priority, assignee, reporter, due dates, estimates, time logs, labels, components, attachments, and comments. A full audit history records every change so nothing is ever lost. Tasks can link to each other to express relationships like "blocks," "duplicates," or "is caused by."

Kanban and Scrum Boards

Boards give your team a visual, drag-and-drop interface for managing work. Kanban boards support continuous flow with optional WIP (work-in-progress) limits. Scrum boards are tied to sprints and let the team focus on the current iteration. Columns map directly to workflow statuses, so dragging a card always triggers a proper workflow transition — boards never bypass your process.

Sprint Planning

For teams running Scrum, Work Ops provides a complete sprint lifecycle. Plan upcoming sprints by pulling tasks from the backlog, set sprint goals, and track progress through burndown and burnup charts. When a sprint closes, velocity is automatically recorded for trend analysis. Scope creep is tracked separately so the team can see how much work was added after the sprint started.

Workflow-Driven Status Management

Workflows are state machines that control how tasks move between statuses. Each transition can have conditions (rules that must be true), validators (checks like "a resolution must be selected"), and post-functions (automated actions like sending notifications). Different task types within the same project can follow different workflows through workflow schemes.

Time Tracking and Estimation

Tasks support original estimates, remaining estimates, and time-spent tracking through work logs. Team members log time as they work, and the system automatically adjusts remaining estimates. This data feeds into sprint velocity calculations, capacity planning, and project-level time reports.

SLA Policies

Define service-level agreements that set time-based expectations for task resolution. SLA policies can be configured by task type, priority, or other criteria. When a task approaches or breaches its SLA, the system triggers notifications and can execute automation rules to escalate the issue.

Automation Rules

Automation rules let you define event-driven actions that fire automatically. Each rule has a trigger (such as "task created" or "status changed"), optional conditions (like "priority is Critical"), and one or more actions (such as "assign to the on-call lead" or "send a Slack notification"). Automation reduces manual toil and ensures consistent processes across your team.

OKRs, Milestones, and Roadmaps

Connect daily work to strategic goals. Objectives and Key Results (OKRs) let leadership define measurable targets, and tasks can be linked to key results so progress rolls up automatically. Milestones mark significant delivery checkpoints, and roadmaps provide a timeline view of planned work across projects and programs.

Specs and Requirements

Capture detailed specifications and requirements alongside the tasks they relate to. Specs provide a structured space for acceptance criteria, technical designs, and stakeholder sign-off — keeping all context with the work rather than scattered across documents and chat threads.

Comprehensive Reporting

Work Ops includes built-in reports to help teams and managers understand delivery performance:

• Burndown charts — Track remaining work against time within a sprint to see if the team is on pace.
• Burnup charts — Show completed work over time, making scope changes visible.
• Velocity charts — Plot story points or task counts completed per sprint to establish a sustainable pace.
• Cycle time reports — Measure how long tasks spend in each status, revealing bottlenecks in your process.
• Lead time reports — Track the total time from task creation to completion.
• Cumulative flow diagrams — Visualize how work moves through statuses over time, highlighting queues and constraints.
• SLA compliance reports — Show how well the team meets its service-level targets.
• Workload reports — See how tasks and hours are distributed across team members to prevent burnout and balance capacity.

Who Is It For?

• Project managers — Plan sprints, track milestones, manage roadmaps, and report on delivery health.
• Team leads — Configure workflows, manage boards, balance workloads, and monitor team velocity.
• Individual contributors — Pick up tasks, log time, update statuses, and collaborate through comments.
• Executives — View portfolio-level dashboards, track OKR progress, and monitor cross-program delivery.

Explore Work Ops

• Tasks — The fundamental unit of work: tracking, assigning, estimating, and resolving
• Projects — Organize work into projects within programs and portfolios
• Boards — Kanban and Scrum boards for visualizing and managing work
• Sprints — Plan iterations, track velocity, and manage scope
• Workflows — Define how tasks move through statuses with conditions, validation, and automation