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:

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