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