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:

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