AA175 - Why You Need to Make Space Learn: Cognitive Load in Agile Software Development

Arguing Agile Podcast

In this episode of the Arguing Agile podcast, Enterprise Agile Coach Om Patel and Product Manager Brian Orlando dive into the concept of cognitive load and how it impacts agile software development teams. Drawing from the 1988 paper "Cognitive Load During Problem Solving" by John Sweller, they discuss:

• What is cognitive load and how does it manifest on agile teams?
• Why the mental effort required for day-to-day problem solving doesn't necessarily lead to learning new skills
• The importance of making space for developers to acquire new "schemas" or patterns through activities like communities of practice and pair programming
• How an overemphasis on utilization and treating problem solving as the primary means of learning can hamper a team's ability to grow their expertise
• Ideas for measuring and managing cognitive load on agile teams

If you're a product manager, agile leader or coach looking to enable your teams to continuously learn and improve, this is the episode for you!
0:00 Podcast Intro
0:11 Topic Intro: Cognitive Load
1:16 What is Cognitive Load
2:36 Claim #1: Problem Solving is Heavy Stuff
6:08 A Software Development Example, #1
8:11 Claim #2 Distinctly Different Learning Mechanisms
10:48 We're Too Busy to Improve
12:27 Being More Effective
14:35 Time to Innovate
15:55 Claim #3 - Normal Work Doesn't Lend to Learning
18:32 Sprint Goals
19:45 Claim #4 - Expertise Development
22:27 Making Space for Learning
24:06 Surprise: Taylorism
25:31 Utilization & Overhead
27:24 Claim #5 - Modification is Required
28:54 Pair Programming
30:33 Measuring Cognitive Load
34:20 Wrap-Up
cognitive load agile development, agile team learning, problem solving vs skill acquisition, managing cognitive load software teams, developer utilization agile, pair programming, communities of practice agile
= = = = = = = = = = = =
Watch it on YouTube
= = = = = = = = = = = =
Subscribe to our YouTube Channel:
https://www.youtube.com/channel/UC8XUSoJPxGPI8EtuUAHOb6g?sub_confirmation=1
Apple Podcasts:
https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596
Spotify:
https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3
Amazon Music:
https://music.amazon.com/podcasts/ee3506fc-38f2-46d1-a301-79681c55ed82/Agile-Podcast
= = = = = = = = = = = =
Toronto Is My Beat (Music Sample)
By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)
CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

บท

1. Podcast Intro (00:00:00)

2. Topic Intro: Cognitive Load (00:00:11)

3. What is Cognitive Load (00:01:16)

4. Claim #1: Problem Solving is Heavy Stuff (00:02:36)

5. A Software Development Example, #1 (00:06:08)

6. Claim #2 Distinctly Different Learning Mechanisms (00:08:11)

7. We're Too Busy to Improve (00:10:48)

8. Being More Effective (00:12:27)

9. Time to Innovate (00:14:35)

10. Claim #3 - Normal Work Doesn't Lend to Learning (00:15:55)

11. Sprint Goals (00:18:32)

12. Claim #4 - Expertise Development (00:19:45)

13. Making Space for Learning (00:22:27)

14. Surprise: Taylorism (00:24:06)

15. Utilization & Overhead (00:25:31)

16. Claim #5 - Modification is Required (00:27:24)

17. Pair Programming (00:28:54)

18. Measuring Cognitive Load (00:30:33)

19. Wrap-Up (00:34:20)