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:

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