The “Manager’s Card”

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

There is nothing like a good long run for clear thinking and giving rise to new ideas. This post is a result of my weekend run, and it’s about managers and why it is so hard to impact their mindset in the Agile journey.

The idea originated as a result of my experience working with this company where the managers find it extremely difficult to relate to the newly formed scrum teams and instead keep communicating with their original teams (Dev and QA teams) and at the same time keep complaining about how the “scrum teams” are not accountable for their end-to-end deliveries.

This made me think about one of the first things we do when implementing Agile in organizations:  restructure teams to include developers and testers together as one scrum team focused on delivery.

What we DON’T do very often is align the entire organization hierarchy with the same focus in mind.

Instead, we keep the old “Dev managers” and “QA managers” concept. The result is that although the teams are focusing on high quality delivery, the organization is still promoting managers in respect to their specific expertise (usually technological/functional) and so the managers find it difficult to focus on end-to-end processes.

This way it is many times too easy and tempting for the managers to “draw the manager’s card” in front of their original team and make decisions that are not aligned with the Agile culture.

Teams get contradicting messages and are in constant confusion. And so are their managers.

I think this is the time to challenge the organizational hierarchy comfort zone and think different.

If the organization wishes to focus on frequent high quality delivery, managers should manage whole group of scrum teams (DEV and QA) with the end-to-end process in mind and be assisted with a high qualified group of experts from different disciplines (architects, developers, qa, and more). No other team definition exist. No more confusion.

This is very similar to the structure of user stories and tasks. Tasks (like experts) are like training wheels that are widely used to assist the team to achieve their goals, but the user stories (scrum team managers) are what we really shoot for.

The main goal of end-to-end high-quality frequent delivery should be at the top of the leadership focus, and they are the ones who lead the entire organization towards great Agile culture.

Subscribe for Email Updates:

Categories:

Tags:

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