Why Story Points are Trash - a thread 🧵
1. Story Points are Subjective: Different people may have different interpretations of a particular story point value, leading to misaligned estimates and potential discrepancies in the overall estimation process. #estimation #noestimates 2. Story Points are Fragile: Changes in team composition invalidate relative estimation efforts. WIP impacts relative estimation efforts. Hidden dependencies impact story points.

Reasons NOT to use #MobProgramming as a software development strategy:

1. Mob programming may only be suitable for some types of projects, teams, or initiatives. It may be more effective for certain tasks or projects but less effective for others. 2. Mob programming may not be suitable in a distributed work world because it requires a high level of collaboration and communication. To communicate effectively, geographically dispersed teams may need a significant investment in tools and infrastructure.

Advantage of #mobprogramming:
1. Increased collaboration on the Scrum Team - all team members are working on the task at hand, exchanging ideas, working together, and creating a shared understanding of the code and solution. 2. Transparent Codebase - team members can gain a deeper understanding of the system and code as a whole rather than just their own areas of responsibility. This entire team understanding removes "knowledge silos" and removes fragility from the team.