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:

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