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:

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