Frequently Asked Questions

Ibis Flow is not a project management tool. It does not replace Jira, and it does not attempt to manage sprints, track time, or provide resource allocation.

Jira remains your system of record. Ibis Flow connects to Jira to provide decision structure around estimation, prioritisation, and planning - without duplicating data or adding process overhead.

Engineering managers, product leaders, and delivery teams who need to make reliable commitments under uncertainty.

Organisations where missed delivery commitments have real consequences - whether for customer trust, revenue, or strategic planning.

Teams already using Jira who want better structure for estimation decisions without migrating to a different system.

Estimation and team alignment capabilities are fully available. This includes collaborative estimation sessions, Jira integration, voting mechanisms, consensus tracking, and session history.

Teams can create estimation sessions, invite participants, vote on effort, discuss divergent estimates, and record final decisions - all while keeping Jira as the source of truth.

Estimation, prioritisation, and planning are interconnected decisions. Building them correctly requires each layer to be stable before the next is added.

Shipping incomplete or disconnected features would undermine the core value proposition - improving decision quality. Deliberate expansion ensures that each capability genuinely improves team outcomes rather than adding complexity.

A session facilitator creates an estimation session and imports tickets from Jira. Participants are invited via email and can join without creating an account.

For each ticket, participants vote independently. Once votes are collected, results are revealed simultaneously to prevent anchoring bias. The facilitator then guides discussion toward consensus and records the final estimate.

When votes diverge significantly, the system surfaces this for discussion rather than averaging the difference. Outliers are highlighted to ensure concerns are addressed before finalising estimates.

Participants can add reactions to tickets - flagging risks, dependencies, scope concerns, or questions. These annotations create shared context and surface assumptions that might otherwise remain hidden.

Tickets are imported from Jira with their current details - title, description, acceptance criteria, and priority. After estimation, the agreed value can be written back to Jira.

Jira remains the source of truth. Ibis Flow provides the decision structure; Jira stores the results.

Plans reflect delivery maturity rather than feature bundles. Team suits individual teams building alignment through estimation. Delivery suits organisations coordinating across multiple teams. Organisation suits enterprises where delivery reliability is strategically important.

Each tier includes the capabilities appropriate to that maturity stage, with prioritisation and planning features included in Delivery and Organisation plans as they become available.

Delivery and Organisation plans will include prioritisation workflows, cross-team visibility, and planning capabilities as these features are released.

Currently, all plans have access to the same estimation functionality. Plan differentiation will increase as the product roadmap progresses.

Contact your organisation administrator and request an invitation. They can add you through the organisation settings.

If you cannot identify the administrator, contact support and we can help locate the right person. Creating a separate organisation is possible but will result in duplicate subscriptions and isolated data.

Ibis Flow connects to Jira using OAuth with minimal required permissions. Only ticket metadata needed for estimation is accessed - not your entire Jira instance.

Jira remains your system of record. Ibis Flow does not store copies of your Jira data beyond what is necessary for active estimation sessions.