Using the Estimation Component in Quely

This guide will walk you through the Estimation component within Quely, explaining both the traditional team-based estimation process and our AI Estimation feature.

1. The Estimation Component (Team-Based)

The estimation component in Quely allows your team to collaboratively estimate the effort required for a task, often using a Fibonacci sequence for "story points" or effort units.

How it Works:

• **Enabling Estimations: **Navigate to the "Components" section within your Quely interface.

• Locate the "Estimation" component and click its associated checkbox to enable it for the current session.
• (Optional) Apply to All Issues: If you wish to make the Diagram Component available across all your issues, toggle the switch labeled "Apply selected components to all issues?" to the "on" position.

You can estimate following 2 formats:

• Effort Estimation using the Fibonacci Sequence (Planning Poker): You'll see a series of numbers (1, 2, 3, 5, 8, 13, 21, 34, ?) displayed. These are standard values used in Agile methodologies for relative sizing of tasks.
• Time Estimation

Effort Estimation (Planning Poker)

The effort estimation process in Quely allows your team to collaboratively estimate the effort required for a task, often using a Fibonacci sequence for "story points" or effort units.
How it Works:
Individual Effort Estimation:

• Click on the number from the Fibonacci sequence that best represents your individual estimate for the task's effort.

Viewing and Managing Estimates:

• Reveal: Once all team members have submitted their individual estimates, clicking "Reveal" will display everyone's individual estimates, facilitating discussion and alignment.
• Hide: This option allows you to conceal individual estimates from view, promoting independent voting before a reveal.
• Clear: If you need to re-estimate the task, the "Clear" button will remove all current estimates, allowing the team to start fresh.

Finalizing and Submitting the Consensus Estimate:

• After team members have voted on their individual estimates and discussions have taken place, a final, agreed-upon estimate (average) is determined.
• This final consensus estimate is then manually entered into the dedicated input field located next to the "Submit" button.
• Clicking this "Submit" button will record the team's final estimate for the task.

Time Estimation

The time estimation process in Quely allows teams/ individuals to estimate the time required to complete a task.

How it Works:

• Click on the time Icon in the upper right corner of the estimation component
• A popup to estimate time appears, where you can select your estimate, or type in the value and save.

2. The AI Estimation Feature

Quely's AI Estimation feature provides an intelligent, automated suggestion for your task's effort, along with a detailed breakdown of its reasoning. This can be a valuable starting point or a second opinion for your team's estimation process.

How it Works:

Initiate AI Estimation: Within the "Estimations" component, click on the AI Estimation Icon

• If more context is needed for the AI to do generate a comprehensive estimate suggestion, it prompts for more info and asks questions in the chat section, which anyone on the team can respond to.

• Once the responses are provided in the thread, the button changes to a "Generate AI Breakdown"

AI Estimation Suggestion: A pop-up titled "AI Estimation Suggestion" will appear, displaying:

• AI-Suggested Estimate: The AI's proposed effort for the task, often highlighted for easy identification.

Detailed AI Breakdown: The AI provides a comprehensive explanation of its estimate, typically including:

• Sub-Task Breakdown: The main task is broken down into smaller, manageable components. Each sub-task will have its own estimated duration.
• Overview: A concise description of the sub-task.
• Success Criteria: What needs to be achieved for this sub-task to be considered complete.
• Additional Information: You may find tabs like "Requirements & Specifications" and "Potential Benefits" providing further context and details about the AI's rationale.

Adjusting for Experience Level: The AI estimation allows for dynamic adjustments based on the assumed experience level of the individual or team performing the task:

• Senior / Mid / Junior: You can select one of these options.
• Impact on Estimate: Observe how the AI's estimate for the sub-tasks (and consequently the overall task) changes based on your selection. A "Senior" developer may have a lower estimate, while a "Junior" developer's estimate might be higher, reflecting the time needed for learning or additional support.

Updated on: 26/07/2025