• Planning Poker
• Installation & Startup
• Oustanding Questions
• Roadmap
• Decisions
• Requirements
• What is Planning Poker
  • Benefits
  • Pitfallls
• Similar Existing Projects
• Terminology

This project was bootstrapped with R3. Review that repository for standards, design decisions and best practices for this project. Planning Poker, as it pertains to software (product) development.

Refer to Project Board

• Web app, mobile app or Both?
  • Web platform. Design should focus on a mobile-first approach.
• What technology or area do you want to focus on?
  • Firebase for auth, persistence, etc
  • React -- Use jagretz/R3 project boilerplate
• Define MVP for initial release

Timer for estimation

• generate a time given number of tasks & time available
• repeat estimations times are cut in half Cards (points or numbers) - many different progressions are used. Most common is the fibonacci sequence; 0, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89, ?/∞, ☕️ Timer for soapbox discussions Identitys'
• Allow anonymous
• generate uuid's, avatars, or fake names (think halo 1) Estimates
• Save past estimates & time (for same task)
• Save history of estimates and time. This can be useful for attachted / associated / tagged tasks.

The overall process, Reason (the why), procedure, and required resources can be found on wiki

tl;dr estimating effort or relative size of tasks. Tasks are smaller peices of fuctionality, or business value, that have been broken down from the overall completed product or MVP.

• Fun / enjoyable due to it's game-like format
• keeps the meeting focused and moving along at a reasonable pace. Helps to deter off-topic distractions / discussions; aversions from the intent of the meeting.
• Leverage knowledge from entire team
• Pooling insights from all areas of development and expertise

"convergence to consensus estimate" - Agile Aliance

Web Apps

• https://play.planningpoker.com/dashboard

Android Apps

• Scrum Poker
• Scrum Planning

Planning Poker In planning poker, members of the group make estimates by playing numbered cards face-down on the table, instead of speaking them aloud. Once everyone has played a card the cards are revealed, and the estimates are then discussed.

By initially hiding the figures, the group can avoid cognitive bias of anchoring, where the first number spoken aloud sets a precedent for subsequent estimates.

Anchoring or focalism is a cognitive bias for an individual to rely too heavily on an initial piece of information offered (known as the "anchor") when making decisions.