Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

The Slippery Slope from Personal Task Assignment to Lack of Team Ownership and Commitment

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

Sprint planning is an important event that has a significant impact on the team’s effectiveness and productivity during the sprint.
The most critical aspects of successful sprint planning are the level of the team’s commitment to the goal of the sprint and handling the sprint backlog.
To encourage the team’s commitment to the sprint, the Scrum Master (SM) should include all the members of the team in planning the sprint and, together with them, craft a challenging sprint goal and estimate the tasks involved. Another important mission of the SM is to prevent managers from putting pressure on team members to take on more than they can deliver and commit to.

By following these guidelines, the team can create a challenging but achievable plan for the sprint and so improve the team’s commitment to their jointly devised plan.

During sprint planning, personal tasks are often assigned to specific team members based on the estimated time they need, until the full capacity available for the sprint is reached.

This practice is supported by ALM tools (like Jira, ADO, and others) that help create a linkage between the team members and their tasks. These tools help each team member to filter their own tasks, making their efforts more comfortable and convenient to them and, by doing this, they create new habits.

So, what’s the problem with doing this?

The practice of assigning personal tasks may give the team members the wrong impression that the sprint backlog and the tasks are personal; however, they should not forget that the main goals of a sprint planning event are to determine the team’s mission and to encourage the team members to take ownership of tasks.
If each team member focuses on completing just their own tasks, they tend to perform more like a “group” of people working side by side than an actual team.

This situation impacts team productivity from different aspects:

  • It loses the advantages of working as a team. Aristotle said: “The whole is greater than the sum of its parts”. This pearl of wisdom is especially relevant when it comes to working within a team.
  • It creates a high level of Work in Progress (WIP) – Each team member focuses only on their own tasks, which increases the cycle time and reduces the team’s overall velocity.
  • Measuring personal performance – It creates a need for micromanagement and harms motivation.

How should we handle this situation?

The SM should understand that task assignment is solidly connected to the level of the team’s maturity and must be handled based on the team’s actual maturity and experience.
In the early days of the team, the practice of assigning personal assignments can be used to give the team more confidence in the process and in the sprint plan itself. However, throughout the sprint, the SM can challenge the team members by advising them to switch tasks with other members, while still focusing on the overall goal of keeping up the team’s commitment to the sprint and conveying the message that “backlog items are not personal items”.
As the team grows and matures, the SM can guide them to the next level by assigning only the first few tasks that the team should start working on in the first days of the sprint and leaving the rest ready to be picked up by the next available free member.

In summary:

The SM plays a significant role in helping the team to increase their sense of accomplishment.
SMs need to make sure that the members of their team do not confuse “personal assignment” with “personal ownership”.
By ensuring that the team is focused on the overall goal of the sprint and the team’s mission, the SM can help their team to achieve a much higher level of satisfaction, effectiveness, and productivity.

The team’s motto should be: “Do more in the same amount of time”.

Subscribe for Email Updates:

Categories:

Tags:

Reading List
PI Planning
Scrum Master
SAFe DevOps
Sprint Retrospectives
Implementation of Lean and Agile
Effective Agile Retrospectives
The Agile Coach
ATDD
Nexus Integration Team
Professional Scrum Master
What Is Kanban
AgileSparks
System Archetypes
Continuous Delivery
Large Scale Scrum
Implementing SAFe
Video
Lean Agile Basics
Program Increment
The Kanban Method
Risk Management on Agile Projects
Frameworks
Lean Agile
Sprint Iteration
Business Agility
Nexus and SAFe
Risk Management in Kanban
Coaching Agile Teams
Agile
Value Streams
Kanban
Hybrid Work
Lean Agile Organization
Kaizen Workshop
Scaled Agile Framework
lean agile change management
Tools
Agile Contracts Best Practices
Software Development Estimation
Jira admin
predictability
Lean Startup
System Team
Enterprise DevOps
IT Operations
Acceptance Test-Driven Development
Applying Agile Methodology
Agile Techniques
Introduction to Test Driven Development
Operational Value Stream
WIP
Scrum and XP
Legacy Code
Agile Development
Achieve Business Agility
Kanban Game
Agile Testing Practices
Systems Thinking
Daily Scrum
RSA
A Kanban System for Software Engineering
RTE
Lean Risk Management
AI
Scrum Guide
Certification
Presentation
Agile Program
Risk-aware Product Development
Agile Release Planning
Atlaassian
Kaizen
GanttBan
Test Driven Development
Agile Product Ownership
Jira Cloud
Lean Budgeting
Covid19
Lean-Agile Budgeting
Scrum.org
EOS®
Scrum
Professional Scrum with Kanban
AI Artificial Intelligence
Nexus and Kanban
DevOps
Software Development
Agility
ART Success
Scrum Primer
Managing Projects
Agile Delivery
Agile Community
Legacy Enterprise
Agile Outsourcing
Manage Budget Creation
Jira
LAB
Pomodoro Technique
Lean and Agile Principles and Practices
Agile Games and Exercises
Entrepreneurial Operating System®
Lean and Agile Techniques
Agile Assembly Architecture
SA
Agile Israel Events
Agile in the Enterprise
Artificial Intelligence
Process Improvement
Managing Risk on Agile Projects
Atlassian
An Appreciative Retrospective
Continuous Integration
Limiting Work in Progress
Agile Exercises
Engineering Practices
Agile Product Development
Continuous Deployment
Jira Plans
Agile Marketing
Kanban Basics
PI Objectives
Continuous Improvement
Principles of Lean-Agile Leadership
Introduction to ATDD
BDD
Professional Scrum Product Owner
Quality Assurance
Games and Exercises
LPM
NIT
Certified SAFe
Agile Project
Development Value Streams
ScrumMaster Tales
Agile Israel
RTE Role
Release Train Engineer
Spotify
Product Management
Scrum Values
Releases Using Lean
TDD
Webinar
speed at scale
SAFe
POPM
Agile and DevOps Journey
Accelerate Value Delivery At Scale
Story Slicing
speed @ scale
Agile Risk Management
Lean Agile Management
agileisrael
Slides
Perfection Game
Agile Basics
Code
Scrum Master Role
Sprint Planning
Rapid RTC
Advanced Roadmaps
Lean Software Development
LeSS
chatgpt
SAFe Release Planning
Elastic Leadership
QA
Built-In Quality
Lean-Agile Software Development
System Integration Environments
Product Ownership
Agile India
Nexus
Lean Agile Leadership
Nexus vs SAFe
ROI
Agile Mindset
Self-organization
Tips
Kanban 101
ARTs
ATDD vs. BDD
Scrum With Kanban
User stories
Portfolio for Jira
ALM Tools
Continuous Planning
Kanban Kickstart Example
Iterative Incremental Development
Agile for Embedded Systems
Amdocs
Agile Project Management
Agile Games
Agile Release Management
Planning
Change Management
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart