DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Culture and Methodologies
  3. Agile
  4. Defining 'Scaling' Agile (Part 1): Creating Cross-Functional Feature Teams

Defining 'Scaling' Agile (Part 1): Creating Cross-Functional Feature Teams

When you (and your managers) start to think about cross-functional teams rather than functions, you start to realize the benefits of Agile.

Johanna Rothman user avatar by
Johanna Rothman
·
May. 24, 17 · Opinion
Like (3)
Save
Tweet
Share
5.00K Views

Join the DZone community and get the full member experience.

Join For Free

I keep encountering confusion about what scaling Agile is. I’m writing what I think is a four-part series to define it so we all talk about the same thing.

When I ask people to define what they mean by scaling Agile, they talk about these possibilities:

  1. They have Agile developers. They want Agile testers. This is creating cross-functional Agile teams for projects.
  2. They have had successful one- or two-team Agile projects. Now, they’re ready for an Agile program.
  3. They have Agile product development (it might be called IT or Engineering or R&D or something else), and they want to share Agile approaches across Marketing, Finance, HR, etc.
  4. They want to build an entirely Agile business.

Each of these is different. Each solves a different problem for the organization. This post is about point #1: the developers have been Agile in their single function team. They want to bring the testers along and create cross-functional teams. (It could be the other way around where the testers are Agile, but I haven’t seen that. I have seen testers using iterative and incremental approaches, but often that’s a reaction to the developers.)

I wrote about the problem of staggered iterations in How Long Are Your Iterations? (Part 1). When the developers are on a different cadence than the testers, they don’t act like a cross-functional feature team. The “team” isn’t delivering a finished feature. They’re not solving problems like a team. They often have a ton of WIP (Work in Progress). Using iterations does not make a team Agile.

On the other hand, if this is where you can start, do start there. The next part in your “scaling” of Agile is to move to cross-functional feature teams. That’s where the team works together, in a collaborative fashion, to create finished features. You might do this in iterations, especially if you’ve only heard of Scrum. You might use a kanban board to see all the flow of work through your team and your bottlenecks.

I keep talking about “your team.” Agile approaches use cross-functional teams who focus on delivering features. I’m not big on component teams. That’s because they postpone delivery of finished features. I also hate the idea (and name) of “shared services.” I’ll blog about that later.

You might think, “The developers are Agile. We’ll scale Agile to the testers.” If that’s the way people think about Agile in your organization, maybe that’s the best you can do. Here’s a possible reframe for you:

Scale Agile from one function to a cross-functional team.

When you (and your managers) start to think about cross-functional teams rather than functions, you start to realize the benefits of Agile.

agile scrum Scaling (geometry)

Published at DZone with permission of Johanna Rothman, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Key Considerations When Implementing Virtual Kubernetes Clusters
  • How To Use Terraform to Provision an AWS EC2 Instance
  • Top Five Tools for AI-based Test Automation
  • Visual Network Mapping Your K8s Clusters To Assess Performance

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: