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.

Categories:

Tags:

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

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