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:

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