As agile practitioners, we are well aware that we need to delegate decision-making and responsibility to members of the team, but it's often easier in principle than it is in practice. Frequently, delegating triggers some angst in most of us, usually revolving around our biggest fear: "What if they fail miserably?"

Fortunately, there are better questions to ask before we delegate, including:

  • How can I determine whether the person is capable of handling the responsibility delegated?
  • If they're not ready, how do I help them to acquire that ability?

In this combination tutorial and workshop, we'll answer both these questions so you can be more successful when you delegate. We'll also give you an opportunity to apply your newly acquired knowledge via in-class simulation and provide information to help you coach others in effective delegation.

 
1 favorite thumb_down thumb_up 2 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/Structure of the Workshop

  1. Why Delegation is so Difficult - and Why it's Important (5 minutes)
  2. Gauging Ability - A Simple Guide (5 minutes)
  3. Practical Delegation Described (8 minutes)
  4. Let's do it! A Delegation Exercise (20 minutes)
  5. Sharing & Recap (7 minutes)

Learning Outcome

When the finished, the attendee will...

  1. Be able to gauge a person's level of ability to complete delegated work
  2. Apply a simple, effective strategy for successful knowledge transfer and delegation.

Target Audience

Anyone working in an agile environment (all roles)

Prerequisites for Attendees

Participants do not need to have any agile experience.

schedule Submitted 7 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • George Dinwiddie
    By George Dinwiddie  ~  6 months ago
    reply Reply

    Donald,

    I like these aspects of the submission, and they should be retained:

    • Helping managers delegate to teams

    I think the submission could be improved by:

    • being clearer on who it's for
      • If it's about delegating to the teams, it's presumably someone higher ranking, though the submission says it's for "all roles." The abstract is vague about the target audience, and therefore might not attract the right people.
    • accommodating delegating to the team as a whole. This seems to be only about delegating to individuals, which can break the teamwork.
    • being clearer about the content
      • The content is represented by 5 bullets which say more about how you'll present than what you'll present. What is the guide? What is the description? What is the exercise?

    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.

    The outline/structure is the place where you sell your session to the reviewers. Help them recognize that you'll deliver on your abstract. Give them details about the content and the way that you'll present it to convince them that you'll do a good job.

    See also https://threadreaderapp.com/thread/1028714041349263360.html for an independent description of submitting a successful proposal.

    - George, AgileDC Program Chair

    • Donald Patti
      By Donald Patti  ~  6 months ago
      reply Reply

      Thank you, this is good feedback. I am working on revisions and will post another comment once I have updated.


  • 45 Mins
    Talk
    Intermediate

    Despite thinking that organizations are slow to innovate, innovation actually abounds at many companies. Kodak, DEC, and Xerox did not fail due to lack of new, cutting-edge innovation; they failed because their organizations were tuned to their traditional markets, and a failure to change their business models and organizations led to their eventual disruption.

    The key to achieving business agility lies in leadership that transforms organizations. Transformational leaders succeed by changing the system, leading with purpose, and steering from the edges. They own their responsibility and boldly lead their organizations into the future. As leaders, we can accelerate this evolution by enabling true self-management and team-based governance.

    Join Bob and Sanjiv to learn how leaders can transform organizations with a flatter organization structure, work anywhere flexibility, participatory profit sharing, and delegated hiring and firing. Explore the agile leadership journey needed for true business agility.

  • Liked Julie Wyman
    keyboard_arrow_down

    Julie Wyman / Wm. Hunter Tammaro - Breaking Up is Hard to Do: How to Split a Team (Without Breaking It)

    45 Mins
    Experience Report
    Beginner

    Struggling to fit your Agile team into one room for ceremonies? Daily stand-up meetings dragging on? Finding it harder to keep the whole team informed? It might be time to split into the three- to nine-person teams the Scrum Guide recommends for better communication, collaboration and decision making. But abruptly changing the team structure can disrupt the larger group's dynamic and culture, and by breaking existing lines of collaboration, hurt the sense of team and organizational unity that already exists. By sharing our experience working with a large team at a non-profit client, we will illustrate the challenges that can face an Agile transformation when a team already has a culture of collaboration worth preserving. The lessons learned from our story will highlight not just the principles for nurturing Agility in a team's culture, but also specific strategies we used to overcome challenges and ensure the journey was one all our teams could embark on together.

  • Liked Salah Elleithy
    keyboard_arrow_down

    Salah Elleithy / Ganesh Murugan, CSP, CSM, CLP, PMP - Mobbing for learning!

    45 Mins
    Talk
    Intermediate
    “We don’t have time for learning but we want to deliver value fast. And by the way, we need to develop new skills and attract talent but we have limited to no budget!” Huh!
    Does that sound familiar? If it does, you are not alone! This is one of the most prevalent patterns we have seen in organizations. We see this almost everywhere. Leaders and Managers demand that teams deliver value fast with no time to learn new skills. It's an oxymoron or may be a paradox!
    It's difficult (dare I say impossible) to attract talent if your organization keeps doing what it has always done. And if your organization needs to develop new skills internally, how will it be able to do that without dedicating time for deliberate learning?! A vicious cycle to say the least not to mention the impact on morale.
    I am not a mind reader but I could imagine you looking at us with a puzzled look and a thought that goes like, "Ya think!" It would be a valid response, I say, as I am sure you have seen or experienced this vicious cycle in many places. You may be even experiencing it right now!
    In this session, Salah and Ganesh can help you explore concrete ideas for experimentation on balancing speed and learning using concepts from Mob Programming. We can't promise any silver bullets however we do believe in experimenting and learning fast!
    Questions to explore:
    1. What is Mob Programming (or Mobbing)?
    2. Where to find talent/skills currently in your organization?
    3. How to introduce Mobbing to accelerate the learning?
    4. What does it take to amplify the good? (or as Woody Zuill puts it "turn up the good!")
    5. What is mobbing for learning and how does it help solve this problem?
    At the end of this session, you will be able to introduce Mobbing to your organization (perhaps even with a demo), attract developers who really want to shake things up and start finding places to "turn up the good!".
  • Liked Ken Horton
    keyboard_arrow_down

    Ken Horton - Retrospective Jedi Mind Tricks

    45 Mins
    Talk
    Intermediate

    Retrospectives are a key component in assisting you teams to improve. Most Jedi, er, Scrum Masters know how to facilitate a retrospective. However, many do not consider how to SELECT a retrospective based on the needs of their teams. Different types of retrospectives will be considered, such as the 6 Thinking Hats, Appreciation, Sailboat, and in addition, two Custom retrospectives. Have you considered which retrospectives you would facilitate for your team based upon their needs? For example, if you are with a new team, what would retrospective would you select? If your team seems to have trouble working together or communicating, which retro? How could you customize a retrospective to address the needs of your team?

  • Liked Bruce Telford
    keyboard_arrow_down

    Bruce Telford - Velocity--A little talk on what it is and isn’t, and how to make it meaningful

    Bruce Telford
    Bruce Telford
    Project Manager/Agile Coach
    UKY
    schedule 8 months ago
    Sold Out!
    10 Mins
    Lightning Talk
    Beginner

    Scrum relies heavily on Velocity for planning and performance improvements. Let's talk about what it really means, some anti-patterns and good practices.

    One of the more abstract concepts in Agile is how to use Story Points and Velocity. It seems pretty straightforward in concept--assign each work unit (story) relative points; at the end of the sprint count up how many points you completed and plan that number for next sprint. But in practice...

    Do points represent days? Complexity? What if something is easy to develop but hard to test? Maybe a task is UI heavy or back-end heavy? Should all teams in an organization use the same scale? What happens when the team composition changes?

    One of the most common challenges is how velocity is viewed outside the Scrum team. Why is Team A's velocity 70 while Team B's is 90? How can we increase velocity to 90? Of course the team can and will fix that just by changes the SPs assigned to each task--that three-point story is now magically worth five; how did that happen?

    Points and Velocity are just tools. Learn some ways to not let them take over.