Back to Forum

Responsibilities of being an Agile Leader / Guard-rails and limits to teams being self-organising

Last post 06:29 pm June 5, 2019 by Chris Rook
No replies yet
Chris Rook
06:29 pm June 5, 2019

I thought there would be value in creating a summary of the things which things which a Scrum Teams need help with. On reflection this is probably also the responsibilities of an agile leader.

  • hiring new team members (support and enablement not candidate specific deciding) 
  • improving test environment capabilities
  • improving Dev Team member and PO availabilty
  • creating right culture and reward systems
  • personal development of Dev Teams
  • enabling knowledge transfer between teams or individuals
  • managing/unblocking interruptions with the Scrum Team
  • overall business planning, capability assessments, performance across multiple products
  • oversee organisation agile standards, rules and policies
  • liaising with Scrum Owners on how a team is doing and potential assistance the team requires

Is there anything missing from this list or people have alternative thoughts on?

 

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.