Scrum Poker in BioAffix Product Development Process

Scrum Poker, also known as Planning Poker, is an estimation method that originated in software projects but is now widely used in advanced technology projects as well. By gamifying the planning process, it makes estimation more effective, participatory, and accurate. This method provides significant advantages, especially for companies managing multidisciplinary and complex projects. In this article, we will explore the fundamentals of Scrum Poker, why it is preferred in high-technology projects, and how it can be used in the development processes of the BioAffix product family developed by Ones Technology.

What is Scrum Poker?

Scrum Poker is a group estimation technique used to determine the estimated effort of a task or user story. In this method, each team member individually selects a card that represents the perceived complexity of the task. The cards usually follow the Fibonacci sequence: 1, 2, 3, 5, 8, 13, 21, and so on. These numbers represent the estimated workload of a task or project. Depending on the team’s approach, they may be associated with time, difficulty, uncertainty, complexity, or technical risk. Each participant selects a card privately from the deck. The selected cards are then kept hidden and collected in a physical or digital environment. Once the moderator ends the voting round, all cards are revealed at the same time. After the cards are revealed, participants who selected the lowest and highest values are usually invited to explain their reasoning first. The differences between estimates are discussed. If the team aims to analyze the topic more deeply, the voting process can be repeated.

This method was first suggested by James Grenning in 2002 and became widely known after Mike Cohn’s book Agile Estimating and Planning was published in 2005.

“Estimation is not just a number; it is the product of shared understanding.”

— Mike Cohn

With Scrum Poker cards, the estimation process becomes more interactive and engaging.

Scrum Poker Process: Step by Step

1. Preparation: The Project Manager Explains the Topic
   Bu aşama, tüm sürecin temelini oluşturur. Proje yöneticisi, takımın tahmin yapacağı konuyu detaylı bir şekilde açıklar. Bu açıklama, ürün gereksinimlerinin net bir şekilde anlaşılmasını ve her bir ekip üyesinin görev hakkında ortak bir anlayış geliştirmesine yöneliktir. Burada şunlar yapılabilir:
   • Konunun, deThis stage forms the foundation of the entire process. The project manager explains the subject to be estimated in detail. The purpose of this explanation is to make sure that product requirements are clearly understood and that each team member develops a shared understanding of the task.
   • At this stage:
   • The topic can be explained in detail with its scope, sub-items, epics, and features.
   • Information about the customer or end user can be shared to help the team better understand the project.
   • Quick feedback can be collected regarding requirements or changing priorities.
2. Card Selection: Team Members Estimate Task Difficulty
   Her ekip üyesi, görevlerin tahmini zorluklarını belirlemek için kartlarını seçer. Burada, ekip üyeleri bireysel olarak, görevin karmaşıklığına göre kendilerine verilen desteden bir kart seçer. Ancak bu aşama sadece puanlama değil, aynı zamanda her takım üyesinin görev hakkında düşündüğü ve hangi unsurları dikkate aldığı bir beyin fırtınası fırsatıdır.
   • Each team member selects a card to estimate the difficulty of the task. This is done individually and privately. However, this stage is not only about assigning a score; it also gives each team member an opportunity to think about the task and reflect on the factors that may affect its complexity.
   • It may also be useful to discuss alternative estimation systems beyond the Fibonacci sequence, such as T-shirt sizing: XS, S, M, L, and XL.
   • Team members make their estimates based on technical and functional requirements. Software challenges, hardware limitations, dependencies, integration risks, or testing needs may all influence the selected score.
3. Revealing the Cards: All Estimates Are Shown at the Same Time
   Bu aşama, tahminlerin hızla karşılaştırıldığı ve grubun genel görüşünün belirlenmeye başladığı kısımdır. Kartlar aynı anda açıldığında, ekip üyelerinin birbirlerinin tahminlerinden etkilenmeleri engellenir. Özellikle özgün yaklaşımı artırmaya yardımcı olur.
   • Bu aşamada, takım üyelerinin neden bu tahminleri verdikleri hakkında açıklamalar yapması teşvik This is the stage where estimates are quickly compared and the group’s general opinion begins to emerge. Since all cards are revealed simultaneously, team members are not influenced by each other’s estimates before making their own decision.
   • This helps encourage independent thinking.
   • At this stage, team members are encouraged to explain why they selected a certain estimate. If there are major differences between the cards, discussion begins and the team tries to understand the reasoning behind each estimate.
4. Discussion: Differences Are Explained
   Discussing different estimates is one of the most valuable parts of Scrum Poker. Team members try to understand why estimates differ significantly.
   • For example, if one team member gives a task 3 points while another gives it 13 points, understanding the reason behind this difference is critical.
   • These discussions help reveal hidden difficulties within the task. A software developer may point out the complexity of a specific API integration, while a hardware engineer may have a different perspective on physical design constraints.
   • This stage helps team members better understand each other’s areas of expertise.
5. Re-Voting: The Team Reaches a Shared Estimate
   After the discussion, the team votes again. Team members may revise their initial estimates after misunderstandings are clarified. This helps produce a more accurate final estimate.
   • The process also strengthens trust within the team and ensures broader participation. Although most team members may eventually converge around a similar score, different perspectives remain highly valuable.
   • In some cases, certain tasks may require more detailed analysis and additional evaluation.

Team members exchange ideas after revealing their scores.

Why Is Scrum Poker Important?

Scrum Poker offers several key advantages:

• Democratic participation: Every team member has an equal opportunity to contribute.
• Independent thinking: Since the cards are revealed at the same time, the influence of the first opinion is reduced.
• Early risk analysis: Complex tasks can be identified during estimation before they become project risks.
• Knowledge sharing: Explanations from different disciplines expand the team’s shared knowledge.
• Planning culture: The process encourages the entire team, not only managers, to participate in planning.

Scrum Poker in BioAffix Product Development Process

BioAffix, developed by Ones Technology, is an advanced biometric security solution family that combines hardware and software. These types of projects bring together many areas of expertise. Scrum Poker can add value to BioAffix product development in several ways:

• Prototype phase: Hardware, software, and mechanical design teams estimate task complexity together. For example, the enclosure design of a fingerprint reader and its compatibility with the PCB can be evaluated jointly.
• Integration and testing: Risks that may occur during the integration of different hardware components with software can be identified in advance.
• Production planning: Potential bottlenecks in the production process can be estimated by the team and prioritized for resolution.
• Supply chain processes: Tasks related to fragile points in the supply chain can be scored so that solutions can be developed on time.
• Security and software updates: The difficulty level of firmware updates can be measured through Scrum Poker, helping teams create better deployment strategies.

During voting, cards remain hidden. When voting is complete, all cards are revealed simultaneously.

Role-Based Estimation Analysis and Consensus Process

Example Estimation Table

Detailed Descriptions

• Hardware Engineer — 8 points The placement of a high-precision screen can be highly challenging due to hardware design complexity. PCB compatibility, limited physical space, and the impact on hardware testing processes all increase the complexity of the task.
• Software Developer — 3 points Since the software is based on a previous version and the requirements are largely similar, the estimated difficulty is relatively low. However, minor optimization work or bug fixes may still be required.
• Test Specialist — 5 points Special equipment may be needed for visual testing. Therefore, setting up the test environment and executing the tests may take time. Fine adjustments in the user interface may also add complexity.
• Project Manager — 5 points The delivery date is approaching and resource planning is required. Considering budget and available resources, workforce and time management must be handled efficiently.

Consensus Score: 5

In this example, different perspectives from multiple areas of expertise come together to create a clearer shared understanding of the task’s complexity. In such cases, after cross-disciplinary discussion, the team may agree on a balanced estimate.

Best Practices for Scrum Poker

• Define scoring criteria: For example, “3 points = one day of work” or “5 points = a task with dependencies.”
• Set a time limit: Long discussions can reduce motivation and efficiency.
• Analyze sprint results: Compare estimates with actual delivery results.
• Use digital tools: Digital tools are especially useful for hybrid and remote teams.

Best Digital Tools for Scrum Poker

Estimate by Microsoft DevLabs

Digital tools provide great convenience for Agile teams during the estimation process. Although there are many digital Planning Poker tools available, for teams working with Azure DevOps, one of the strongest options is Estimate by Microsoft DevLabs.

Estimate provides full integration with Azure Boards, supports real-time estimation sessions, reflects story points directly on work items, and is free and open source. In short, it is a fast, simple, and integrated estimation solution for teams using Azure DevOps.

Other Suggested Tools

Additional Recommendations to Enrich Scrum Poker

• Use it at the beginning of the sprint: Applying Scrum Poker at the start of planning meetings helps create clearer time estimates.
• Use it for training new teams: The method is ideal for improving communication within newly formed teams.
• Compare estimates with delivery results: After each sprint, comparing estimated points with actual outcomes supports data-driven improvement.

Long-Term Benefits of Scrum Poker for BioAffix

Scrum Poker plays a strategic role beyond short-term sprint estimation, especially for the long-term success of high-technology products such as BioAffix. Accurate and repeated estimation creates important benefits over time:

• Improved budget and resource management
• Data-driven decision-making
• Reduced uncertainty in R&D processes

Common Mistakes and Solutions in Scrum Poker

Conclusion: Planning the Future with BioAffix and Scrum Poker

Scrum Poker is an effective method for all technology companies that want to improve the predictability of complex projects and use workforce capacity more efficiently.

While developing the BioAffix product family, Ones Technology integrates Agile methods such as Scrum Poker into planning and risk management processes, gaining both time and cost advantages.

No matter how complex a project is, success is possible with the right planning culture. Scrum Poker can become an important, enjoyable, and educational part of that culture.

Sources

1. Cohn, M. (2005). Agile Estimating and Planning. Pearson Education.
2. Grenning, J. (2002). Planning Poker Origin. renaissancesoftware.net
3. http://Scrum.org . “Estimation in Scrum.” scrum.org
4. Wikipedia: Planning Poker – Planning poker
5. DevPoker: https://devint.io