Where Those Who Sprint Go The Extra Mile
 » AgileCareers » CareersBlog » March 2016  » Who’s Who in Agile Teams?

Who’s Who in Agile Teams?

3 March 2016

Waterfall teams vs. scrum teams

Most waterfall teams are manager centric. They look to the the manager to set priorities, track progress, and evaluate performance. Agile teams are self-organizing. They work with a product owner (not usually in the team’s management chain) who sets the vision for what should be built. The team, through a series of sprints, drives how the product should be built.

Self-organizing teams own their destiny. In sprint planning, they decide how much work to commit to the sprint, and because of that, their level of ownership in the success of the program remains high. Engineers who own their own schedules build products of higher quality more consistently because they own their schedules. Engineers want to build high quality products on time. Everyone in the organization has the same goal. As a company we all want to succeed. Tuckman’s stages of group development outlines how teams form and thrive. Agile, self-organizing teams are no exception.

Mutual trust and candor are essential to well-performing agile teams. Management that continually focuses on hiring the right team is able to trust the team to get the job done. The need to then micromanage every detail of the team’s work doesn’t exist. The scrum master and the development manager protect the team from outside distractions such as feature creep, waterfall anti-patterns, cross functional thrash, or side projects that will compromise the integrity of the sprint.

Role 1: scrum mastersAgile teams_scrum master

Scrum masters are the project leaders in agile teams who focus on optimizing performance of the scrum process. They work between the product owner and the team ensuring consistent, successful sprints by running stand-ups, and working to reduce blocking issues for the team. Cross-functional thrashing can be costly for teams, so successful scrum masters own cross-team coordination so the core team can focus on product development. This practice keeps everyone efficient and on the same page.

“Scrum masters are leaders in agile teams who focus on optimizing performance of the scrum process.”

The scrum master coordinates most of the inputs and outputs required for an agile program. He or she drives the sprint kickoffdaily stand-upssprint review, and sprint retrospective. The scrum master is also an agile coach, helping the team to adopt and own agile practices throughout the product life cycle: story point estimation, sprint planning, and continuous delivery. The coaching aspect of the scrum master’s job is critical as they not only help the team to be agile, but advocate for agile development throughout the organization, and spread the good word about why agile development is right for the project and for the company. Often times, when agile methodologies are new at a company, the advisers and stakeholders outside of the team need agile coaching as well.

The scrum master works with the team and the development manager to estimate items in the backlog. At first, the team will need some guidance from the scrum master and development manager. As the team is forming, it builds shared knowledge of the program through successful sprint planning. As the team moves into a performing stage, the scrum master focuses less on estimation and more on optimizing the velocity of delivery.

Role 2: development managersAgile teams_Dev manager

There’s a lot of uncertainty for engineering managers when their team adopts agile – an Admiral Stockdale moment, if you will. But despite the fact that agile development teams don’t rely on their manager for estimation and prioritization, managers still play a vital role.

Hiring well

The most important thing a development manager does is hire. Why spend so much time on hiring the right candidate? Team changes are expensive on two levels:

  • Searching for candidates takes focus away from building great product.
  • When new employees join, the existing team needs to spend time onboarding them. Teams will experience a drop in velocity over a few sprints as each new person integrates into the team.

“The most important thing a development manager does is hire.”

When a team is truly self organizing and performing well, everyone in the organization sees it through the product quality and delivery. No one has more impact here than the development manager.

One of the big differences between agile and waterfall teams is that the development manager is a partner in the estimation process. In a waterfall team, a conversation like this wouldn’t be unheard of:

  • “Hey, how long is it going to take to deliver this feature?” – manager
  • “It’s going to take six weeks. We need to do A, B, C to get the feature to market.” – engineer
  • “Hmm. That makes sense, however, you need to find a way to get it done in four weeks.” – manager

But an agile development manager knows to hire great people, then trust them. A fundamental tenet of the agile process is that those closest to the work are best able to scope and deliver. The team sets the schedule. The development manager adds unique value in inquiring and vetting assumptions made in the estimation exercise – partnering in the process, rather than dictating it.

“A tenet of the agile process: those closest to the work are best able to scope and deliver.”

Developing well

While scrum masters focus on team velocity, development managers build up team members’ velocity by coaching individuals one on one. Development managers curate and inspire great talent in their organizations. Great managers are adept at the fundamentals of management: one on ones, giving feedback, and coaching their teams. Successful development managers mentor engineers to bring greatness to the table: ideas, code, tests, and culture. Great development managers partner with their teams. At times, the team will struggle or come to an impasse with architecture design decisions. Adept development managers know when to intervene to break the impasse or let the team continue to struggle to grow the team. The scrum master may not be as technical as the rest of the team so the development manager lends valuable context between the scrum master and the team when there is a clear knowledge gap.

In addition, they also partner with the senior developers in the company to set the development culture. They’re often influential in the technology choice for the program, and continue to own responsibility for the quality of the product from the code architecture to the end-user experience. Development managers engage in code reviews to ensure team members are contributing code that meets the short and long term goals of the program. They also set context internally for the team and in the larger organization.

To learn more

We’ve spent a fair amount of time looking at what makes a great manager in an agile culture and now we’d love to know: how does your team practice the agile methodology? Drop us a line in the comments!

  • This article was written by Dan Radigan, Technical Account Manager JIRA 
  • Read more of his content HERE 


Article Rating
Current rating: 0 (0 ratings)

Blog post currently doesn't have any comments.
 Security code

How To Bomb An Interview
Six Critical Questions Candidates Should Ask During an Interview
Agile for Recruiters Part 4
Agile for Recruiters Part 3
Agile for Recruiters Part 2
Agile for Recruiters, Part 1
Meaningful Careers and Growth (Agile HR – Q&A Series Part 4)
Interview Preparation – A Little Planning Goes a Long Way
Are Certifications Really Necessary?
Rethinking Reward and Recognition (Agile HR – Q&A Series Part 3)
Don’t Sabotage Your Hiring Process
Shifting to Iterative Performance Flow (Agile HR – Q&A Series Part 2)
Candidate Brand Management
Gamification of Talent Acquisition (Agile HR – Q&A Series Part 1)
In Agile, It’s Not Just Whom You Hire, But When You Hire Them
Q&A Series: Agile Leadership Webinar «Agile HR | People Operations»
Use Agile to Hire Agile - Part 2
Software Development Career Path - The Agilist Perspective
Why Attending an Online Career Fair is a No-Brainer for Employers
How to Write a Great Personal Statement
Use Agile to Hire Agile - Part 1
Five Ways Lean | Agile Enterprises Rock At Onboarding
Advice to New Graduates
First Impressions Count When Hiring Agile Talent
Want to Develop a Strong Talent Pipeline? Four Things to Consider
Six Behaviors to Consider for an Agile Team
The State Of Agile Recruitment
Is an Agile Career Right For You? 7 Unique Qualities of Agile Work
Can the Scrum Master also be the Product Owner?
Agile is not Scrum
What Do You Look for in a Servant Leader or a Scrum Master?
Product Owners and Scrum Masters: Partners in Adversity
Six Behaviors to Consider for an Agile Team
What is Agile Leadership?
Six tips for hiring Agile people with Lena Bednarikova
How to Hire an Agile Coach
Six Tips for Interviewing Scrum Masters, Part 1
Who’s Who in Agile Teams?
Advice for Interviewing Scrum Masters
38 Scrum Master Interview Questions

February 2017(1)
January 2017(4)
December 2016(5)
November 2016(7)
October 2016(4)
September 2016(3)
August 2016(3)
July 2016(2)
June 2016(4)
May 2016 (3)
April 2016(1)
March 2016 (3)
February 2016(2)