Project Management

The Team Lead Role: Different Types of Teams Need Different Types of Leaders

From the Disciplined Agile Blog
by , , , , , ,
This blog contains details about various aspects of PMI's Disciplined Agile (DA) tool kit, including new and upcoming topics.

About this Blog

RSS

View Posts By:

Tatsiana Balshakova
Mark Lines
Mike Griffiths
Scott Ambler
Bjorn Gustafsson
Curtis Hibbs
James Trott

Past Contributors:

Joshua Barnes
Michael Richardson
Daniel Gagnon
Valentin Tudor Mocanu
Kashmir Birk
Glen Little
Klaus Boedker

Recent Posts

DA 5.6 is released

Disciplined Agile 5.5 Released

Choose Your WoW! Second Edition Is Now Available

Requisite Agility applied in Project Management

Disciplined Agile and PMBoK Guide 7th Edition

Categories

#ChoiceIsGood, #ChooseYourWoW, #ConsumableSolution, #ContinuousImprovement, #CoreAgilePractices, #experiment, #Experimentation, #GuidedContinuousImprovement, #Kaizen, #LifeCycles, #ProcessImprovement, #TealOrganizations, Adoption, agile, agile adoption, Agile Alliance, Agile Business Analyst, Agile certification, agile data, agile governance, agile lifecycle, agile metrics, agile principles, agile transformation, Agile2018, Agile2019, Agile20Reflect, AgileData, Analogy, announcement, Architecture, architecture, architecture owner, Articles and publications, Asset Management, Atari, Backlog, Barclays, being agile, benefits, bi, blades, book, Branching strategies, Browser, Business Agility, business intelligence, business operations, capex, Case Study, Certification, certification, charity, Choose your WoW, CMMI, cmmi, Coaching, Collaboration, Communications Management, Compliance, Compliancy, Conference, Construction, Construction phase, Context, Continuous Improvement, coordination, COVID-19, Culture, culture, Cutter, DA, DAD, DAD Book, DAD discussions, DAD press, DAD roles, DAD supporters, DAD webcast, DADay2019, Data Management, database, dependencies, Deployment, Development Strategies, DevOps, disaster, Discipline, discipline, Disciplined Agile, disciplined agile delivery, disciplined agile delivery blog, Disciplined Agile Enterprise, disciplined devops, Documentation, Domain complexity, dw, DW/BI, Energy Healing, Enterprise Agile, Enterprise Architecture, Enterprise Awareness, enterprise awareness, Essence, estimation, Evolving DA, Executive, Experiment, facilitation, FailureBow, feedback-cycle, finance, Financial, FLEX, Flow, foundation layer, Funding, GCI, GDD, Geographic Distribution, gladwell, global development, Goal-Driven, goal-driven, goals, Governance, GQM, Guideline, Hybrid, Improvement, inception, Inception phase, India, information technology, infosec, Introduction, iterations, Kanban, large teams, layer, lean, Lean Startup, learning, Legal Project Management, LeSS, Lifecycle, lifecycle, Manifesto, mark lines, marketing, MBI, Metaphor, Metrics, metrics, mindset, Miscellaneous, MVP, News, News and events, Non-Functional Requirements, non-functional requirements, Non-solo development, offshoring, Operations, opex, Organization, Outsourcing, outsourcing, paired programming, pairing, paper, People, People Management, phases, Philosophies, Planning, PMBoK, PMI, PMI and DA, PMI Chapter, Portfolio Management, post-format-quote, Practices, practices, Principle, Process, process improvement, process tailoring, Product Management, product owner, Product Owners, productivity, Program Management, Project Management, project-initiation, Promise, Quality, quality, rational unified process, Refactoring, Reiki, Release Management, release management, Remote Training, Remote Work, repeatability, requirements, Requirements Management, research&development, responsibilities, retrospectives, Reuse, Reuse Engineering, ride for heart, rights, Risk Management, Risk Management, Risk management, Roles, RUP, SAFe, sales, Scaling, scaling, scaling agile, Scheduled Workshops, SCM, scorecard, Scrum, ScrumMaster, SDLC, Security, security, self-organization, SEMAT, serial, skill, solutions software consumable shippable, Stakeholder Management, strategy, Support, Surveys, Teal organizations, team development, Team Lead, team lead, Teams, Technical Debt, Teleconferencing, Terminology, terraforming, test strategy, testing, time tracking, Tool kit, Toolkit, tools, traditional, Transformation, Transition iteration, transition phase, Uncategorized, Upmentors, Using PMI Standards, value stream, velocity, vendor management, Virtual Training, Workflow, workflow, workspaces

Date

linkedin twitter facebook Request to reuse this  


We are often asked why Disciplined Agile (DA) has a team lead role instead of  Scrum master or project manager.  The answer is three-fold: different types of teams require different types of leaders, leadership responsibilities vary based on the type of team they are leading, and DA strives to be agnostic wherever possible.  Let's explore the implications of this strategy.  

Team lead is what is known as a meta role.  What we mean by this is that there are different types of team lead depending on the situation, as depicted in Figure 1.  Think of team lead as a place holder for a more specific type of lead.  So, a scrum master is a team lead of a Scrum team, a project leader is a team lead of a project team, a sales manager is a team lead of a sales team. At times, the team will choose to stick with the name “team lead” for the role due to their way of working best fitting that description. 

Figure 1. Types of team leads.

Disciplined Agile Team Lead Role

As I said above, there are three reasons for taking this approach with the team lead role:

  1. Different teams require different types of leads.  A Scrum team needs a scrum master, or better yet a senior scrum master, as team leader. Similarly, a project team needs a project manager or project leader.  A finance team or a sales team need a function manager such as a chief financial officer or a sales manager respectively as the team lead. Each type of team needs a team lead that is fit for purpose. Because all these teams (and many more) are part of Disciplined Agile, we cannot prescribe a single type of team lead.  
  2. Leadership responsibilities will vary across teams. The responsibilities of team leads will vary depending on the type of team they lead. For example, when leading a team a project manager takes on different responsibilities compared to a scrum master.  Similarly, a sales manager leading a team would have responsibilities around educating business leaders on the sales strategy that a project leader typically wouldn't have.   
  3. Being agnostic.  Let’s imagine for a moment that it made sense to have a single set of responsibilities for the team lead role. Which one should it be? Adopting the scrum master role would only fit Scrum teams. Similarly, adopting the project manager role would only fit project teams. In the end, either choice ends limiting the applicability of the Disciplined Agile tool kit. Remember that DA is a hybrid approach that opens your options by combining great ideas from a wide range of sources: some agile, some lean, and some traditional. Ultimately, leading teams appropriately to a better way of working.  

The end result is that you may see some DA teams with a senior scrum master as the team lead, some DA teams with a project leader as a team lead, some DA teams with a functional leader in the role of team lead, and some teams with someone who is simply the team lead. Just like your way of working (WoW) should be fit for purpose, so should your approach to roles and responsibilities.


Posted by Scott Ambler on: July 07, 2020 09:13 AM | Permalink

Comments (8)

Please login or join to subscribe to this item
avatar
Thomas Walenta Global Project Economy Expert Hackenheim, Germany
Good explanation.
And it suits to PMBoK definition of a project manager:
".. person assigned .. to lead the team that is responsible for achieving the project objectives"

avatar
Eduin Fernando Valdes Alvarado Project Manager| F y F Fabricamos Futuro Villavicencio, Meta, Colombia
Thanks for sharing

avatar
Jean-Claude Greco Sierre, Valais, Switzerland
Thanks fot sharing !

avatar
Marcus Zonis Bartlett, Il, United States
Thank you for sharing

avatar
VIMAL RAJ NEDUNCHEZHIAN Program Manager| Mphasis Limited UK Nuneaton, Na, United Kingdom
Team lead - seem to be the next proxy stakeholder beside Product owner , Thanks Scott

avatar
Junaid Sagheer Staff, Technical Program Manager| Walmart Global Tech Bentonville, AR, United States
Thank you for writing, It really helped to answer my question.

avatar
Scott Ambler Consulting Methodologist| Ambysoft Inc. Toronto, Ontario, Canada
@Junaid, glad I could help. We get asked this question a lot.

avatar
Mário Gourgel Luanda, Angola
Clear and simple explanation.

Please Login/Register to leave a comment.

ADVERTISEMENTS
ADVERTISEMENT

Sponsors