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:

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