Bring Work to Your Team(s)!

Are you struggling to find the right team structure? Are your teams aligned for optimal flow across the program? Are your teams precluded from doing important work due to contractual constraints? Are they really efficient... and does that align with driving outcomes with our customer(s)?

We all know that teams are at the heart of Agile - they do all the work. However, we often see 'nominal' Agile teams where individuals are still operating without cross-functionality in a traditional manner. At scale, we often see non-homogenous teams operating in a similar fashion - as siloed groups that prevent optimal job sequencing, create technological 'lock-in', and generally undercut overall business agility. The notion of 'bringing work to the team(s)' is not a new or novel concept but is perhaps largely misunderstood in practice. If you aren't maximizing the power and flexibility of your Agile teams, join us for a brief exploration into what 'bringing work to the team' really means and why it's such a critical part of increasing flow. We'll also discuss how 'color of money' delineations could be better handled to promote overall agility.

 
 

Outline/Structure of the Talk

  1. Bring people to work vs Bring work to the team(s)
    1. What does this mean - compare and contrast
  2. Recognize the problem(s) we are trying to solve
    1. non-economic decision-making and suboptimal job sequencing
    2. Siloed individuals and teams
    3. Technology 'lock-in' - teams aligned to specific technologies (Java, .Net, COTS, etc.) often force less-than-ideal technological decisions and/or solutioning
    4. 'Color of Money' constraints - funds dedicated to 'O&M' or 'Adaptive Maintenance' or 'New Development' preclude program agility and often preclude the 'Bring Work to the Teams' approach
  3. Advantages of 'Bring Work to the Team(s)'
    1. Business Agility
    2. Cross-functional skills development
    3. Enhanced team dynamics
  4. Perceived Deficiencies

Learning Outcome

Attendees should understand the long-term benefits of bringing work to the teams vs. the shorter-sighted reactionary approach of bringing people to work.

Target Audience

Government, Executives, Program Managers, Agile Coaches

Prerequisites for Attendees

A thorough understanding of basic agile concepts and some understanding of scaling approaches.

schedule Submitted 1 year ago

Public Feedback

comment Suggest improvements to the Speaker
  • George Dinwiddie
    By George Dinwiddie  ~  1 year ago
    reply Reply

    The abstract is the place where you sell your session to the right prospective attendees. Help them recognize themselves and their situation, and tell them what benefits they'll get by attending. Give them enough information about the content to convince them that they'll get that benefit.

    In this abstract, are you targeting people who already believe in bringing work to the teams? If so, what benefit are you offering them with this session?

  • Phillip Manketo
    By Phillip Manketo  ~  1 year ago
    reply Reply

    Chris.. the abstract requires additional context regarding "technology lock-in" and "color of money"... suggest you either provide detailed elaboration or a deck that helps the committee understand what these concepts mean and how they inform your proposal.  Regards, Phillip

    • Chris PerDieu
      By Chris PerDieu  ~  1 year ago
      reply Reply

      Thanks Philip. I added additional context for the items you mentioned. Please let me know if I can clarify anything else further!

      Chris