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:

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