top of page
Search
Writer's pictureSean Lazo
2 min read

The Multitasking Paradox in Sprints

You have been assigned 2 feature requirement tickets in a sprint. You conduct research and design processes for both features simultaneously. You mix up learnings, thoughts, and even designs between the two features. Focus is compromised and ambiguity ensues. You waste time and effort re-tracking your thinking. This confusion and error leads to poor design.



To design with focus, commit to one feature per sprint at a time. Understanding multitasking impacts will encourage you to stop running concurrent UX projects.


Here is a list of drawbacks and impacts for multitasking factors, along with advantages when working on just 1 task at a time.


Cross contamination

  • Ideologies will be mistakenly commingled between features, leading to incorrect solution. This is due to constant switching between two schools of thought.

  • Working on one feature will allow you to stay focused and hone in on details without confusion.


Scope increases past sprint capacity

  • New problems, solutions, dependencies arise, extending efforts beyond the current sprint.

  • Working on one feature will reduce scope creep and be contained within the sprint.


Overwhelmed pod mates, users, and self

  • Developers will be burdened with tech debt and implications. Users need to five more of their time for research. You will burn yourself out.

  • Working on one feature will be manageable for everyone involved.


Low Agile sprint performance ratings

  • Deferring or not completing tickets due to scope creep or time results in poor sprint performance ratings.

  • Working on one feature is easier to contain within a sprint, helping to achieve good performance ratings.


Loss of information and thinking

  • Valuable ideas and insights will disappear or not materialize when your mind is overloaded.

  • Working on one feature will allow you to retain information and develop better ideas.


Summary


Comments

bottom of page