Jason C. McDonald discusses the flaws of story points and introduces his alternative called Quantified Tasks. They explore various scales used for measuring tasks in agile development. The concept of quantified tasks and how they capture effort in software development is explained. The pushback encountered during implementation and the use of quantified tasks for bug detection are discussed. The benefits and challenges of using quantified tasks to identify problems within a team or company are explored. Learn how to implement and use the quantified tasks system.
Read more
AI Summary
Highlights
AI Chapters
Episode notes
auto_awesome
Podcast summary created with Snipd AI
Quick takeaways
Quantified Tasks introduces three key metrics: distance, friction, and relativity to address the shortcomings of story points.
Quantified Tasks offers advantages like better planning and estimation, and identifying quality control failures through bug volatility assessment.
Deep dives
Introduction
This episode of Software Engineering Radio features a discussion with Jason C. Macdonald on his development called Quantified Tasks as an alternative to story points.
Understanding Story Points
Story points originated from the agile methodology and were created to estimate the effort required to complete a task or release. However, in practice, story points often became synonymous with time estimation. Story points are measured relative to other tasks using arbitrary numbers, which lack standardization and objectivity.
Introducing Quantified Tasks
Quantified Tasks, developed by Jason C. Macdonald, aims to address the shortcomings of story points. It introduces three key metrics: distance, friction, and relativity, which are on a scale of one to five. These metrics measure the raw work, resources available, and level of uncertainty for each task. By combining these metrics, an energy point score is derived as a replacement for story points.
Benefits and Applications of Quantified Tasks
Quantified Tasks offers several advantages, such as providing a clear and meaningful measurement system and enabling better planning and estimation. The system also assists in identifying and addressing quality control failures through the assessment of bug volatility. While quantified tasks can be implemented gradually and tailored to specific team needs, it is important to approach it as part of a larger mindset shift towards Agile principles.
Jason C. McDonald, author of the book Dead Simple Python, speaks with host Samuel Taggart about leveraging quantified tasks to improve estimation, particularly across projects. They discuss the origin of the concept and its relationship with story points, and Jason offers examples to show how quantified tasks can capture nuances in software tasks that are often lost with story points. He also points to the ability to compare them across projects as a major advantage of quantified tasks. Among other topics, they consider also how to use quantified tasks to analyze the stability of a codebase. Brought to you by IEEE Computer Society and IEEE Software magazine.
Get the Snipd podcast app
Unlock the knowledge in podcasts with the podcast player of the future.
AI-powered podcast player
Listen to all your favourite podcasts with AI-powered features
Discover highlights
Listen to the best highlights from the podcasts you love and dive into the full episode
Save any moment
Hear something you like? Tap your headphones to save it with AI-generated key takeaways
Share & Export
Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more
AI-powered podcast player
Listen to all your favourite podcasts with AI-powered features
Discover highlights
Listen to the best highlights from the podcasts you love and dive into the full episode