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:

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