đDaily Life on Agile Teams
Let's talk about what day to day life looks like on Waterfall and on Agile cross-functional teams.
Last updated
Let's talk about what day to day life looks like on Waterfall and on Agile cross-functional teams.
Last updated
âHow are Agile Teams Structured? It depends!
The team who is cross-functional in their nature brings many background and perspectives. They get together and build a consensus in what they will be responsible or accountable for, together as they agree to work week-to-week.
They don't stick within these boundaries either: they live a cross-functional lifestyle where they can float across responsibilities and functions for the purposes of learning.
You should never hear teammates say "That's not my job, that's their job" on an Agile team.
You should hear teammates say, "I was hired for research but this week I want to get into product strategy!"
Your team may have job titles, but their duties vary and may fall outside of those titles. Everyone should be celebrating and encouraging this kind of environment for all of the reasons we talk about regarding making strong Agile teams.
The more your team collaborates across functions:
The quicker they will get to Performing stage.
The more they will all "self-heal" from team conflict.
The stronger your self-organization becomes.
The stronger your continuous improvement becomes.
The title you have doesn't mean that you only do that kind of work on a cross-functional team.
If you operate with different responsibilities, it does not mean you have multiple job titles.
A title is the function. A role is not a function. A role is a set of responsibilities that you agree to on an Agile cross-functional team.
Learn more details about cross-functional functions, duties, and people here:
Let's talk about what day to day life looks like on Waterfall and on Agile cross-functional teams.
It's more common that teams call themselves agile and they don't live in the agile philosophies.
If you're building things on a waterfall team, this is what happens:
Everybody in the beginning of a project agrees to the scope before doing the work. Someone produces what's called a Product Requirements Document which outlines everything in scope for the whole project.
When the product requirements are outlined, each team works in phases. Every team function is working alone. They meet alone, they talk alone, they decide alone. They don't communicate across functions. They don't collaborate across functions. They ship their work in silos to the next team.
When the project is finished, they ship it, and gather feedback from clients and users. When it may be too late!
Life on an Agile team is the opposite of Waterfall teams.
The teams are working together across functions in cross-functional teamwork.
When they start the work, all functions rally to understand high level goals and outcomes to achieve.
Everyone collaborates across functions to gather the most important requirements to deliver first.
Everyone collaborates to quickly deliver those requirements across research, design, and development. They check their work as they go with users and with clients.
They ship in usable, small chunks quickly, and gather feedback in order to pivot and refine their plans ahead.
