3 steps towards better team work

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

Working with teams I sometimes feel that teamwork is similar to the weather: everybody talks about it but not much is done. When I talk about teamwork I mean doing the work together, as a team. Advising with each other is good, planning together is necessary, going to lunch as a group is fun and like the other activities, is probably a good way to get nearer to team work. However , as said above, I’m talking about doing the work together. And here are 3 steps that will help you get nearer to that worthy cause.

First step: no personal assignments. Most electronic boards (e.g. Jira, TFS, Gitlab etc.) have an “assigned” field on stories. Don’t use it. As simply as that. Let it be empty. During planning meetings don’t talk about who’s going to do a story, leave it to later. When is later? Later is when we need to start working on the story, when it is next in priority. And then also don’t assign a person. Talk about who will start working on it today. Who in plural, I mean. Then tomorrow, in your daily meeting or during the day, agree who should work on it then. This is a team thing. There is no specific one developer responsible for the story, it is the team.

Some people will say: but how will we know who is working on what? The answer is simple: if you are working on many stories in parallel it might indeed be difficult to know that. So work on less stories in parallel and then everyone knows who’s working on what.

Second step: Weekly mob programming sessions. Mob programming is the activity where the entire team is developing together. Set a meeting room with a big screen, one computer and one keyboard. The keyboard moves every 5 minutes from one person to the next. The team decides what the driver (the person on the keyboard) does. Now work on your ongoing tasks. People who hear about this for the first time find it hard to understand this but you need to try it out. It works like magic. This is an activity that brings the team together. Spend every week 1.5-2 hours on this, going on some of the ongoing tasks and good things will start to happen. Llewellyn Falco wrote a book about this.

Third step: Pairing. Pairing is when two developers develop on the same workstation. Remember that most of what you do during development is thinking, not writing, so one keyboard is not a problem. In workshops, I’ve led people who always say it’s more fun to work together and they think of more creative solutions. Alistair Cockburn and Laurie Williams show pairing is 15% more effort (e.g. while one person will do the job in 2 days, two will do it together in 1.15 days) but other benefits make it a thing you must do.  Arlo Belshee wrote an essay about promiscuous pairing, a must-read.

The daily meeting is a good place to think about who will pair with whom today.

To summarize, the main problem with teamwork is that it doesn’t look good on a spreadsheet: you see plainly more people on the same job and you don’t see that magic that it does. Don’t let this stop you. Start by not assigning specific people to tasks, move on to mob programming and then find opportunities to pair. You will see results quite quickly.

Subscribe for Email Updates:

Categories:

Tags:

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