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:

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