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:

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