Back to List

Pre-assigning Work to Team Members (Agile Transformation Pain Point #14)

Rachael Wilterdink Rachael Wilterdink  |  
Dec 13, 2018
 
This pain point is something you definitely don’t want to do.

Agile and Scrum teams are meant to be self-organizing. They should volunteer to pick up assignments, not be assigned.

Development team members are volunteering to do stories, and they might want to learn something new –let them do that. You want to let that team to manage itself. Volunteering also lets people have opportunities to grow by learning to do something new.
 
pre-assigning work to team members
 

Avoid expertise bottlenecks

Otherwise, if you pre-assign stories to someone based on their expertise, you're robbing another team member of the chance to learn. You’re also doing yourself a disservice by creating a bottleneck where only one person has certain knowledge and expertise. You want to spread that knowledge across the team as much as you possibly can.

Again, just because one person has that expertise doesn't mean they shouldn't be actively trying to train someone else. Pair programming is a good way to go: team up a senior person with a junior person, or someone with database skills with a developer, or someone with one development language with another development language. Spread it out and let people learn.
 

Get the free eBook

This is the fourteenth of 20 blogs on 20 Agile Transformation Pain Points (and how to avoid or manage them). To read them all right now, download our free eBook.
 
agile transformation pain points ebook
Agile

 

Love our Blogs?

Sign up to get notified of new Skyline posts.

 


Related Content


Blog Article
Focusing On Projects Rather Than Products (Agile Transformation Pain Point #17)
Rachael WilterdinkRachael Wilterdink  |  
Jan 10, 2019
This is a difficult transition for waterfall companies to wrap their heads around. It's a big mindset shift that needs to happen to be truly successful. I'm not saying that you can't have an agile Scrum team that works on projects with a distinct beginning and end. That might be a...
Blog Article
Skipping Over Quality (Agile Transformation Pain Point #16)
Rachael WilterdinkRachael Wilterdink  |  
Jan 03, 2019
You should not skip over quality because it’s inherently meant to be baked into agile. There are many ways you can do that. You could consider doing acceptance test-driven development, behavior-driven development, or you can write automated tests wherever possible. Again, I really like the...
Blog Article
“O Testing Tree, O Testing Tree” - A Comprehensive Look at QA Testing for the Holidays
Tim MorrowTim Morrow  |  
Dec 21, 2018
“O Testing Tree…O Testing Tree…how lovely are your branches!” Yes, for a Quality Analyst (QA) tester, the tree pictured below is a thing of beauty! It represents a comprehensive plan for testing an application and a roadmap for delivering high-quality products free...
Blog Article
Misusing Scrum Ceremonies (Agile Transformation Pain Point #15)
Rachael WilterdinkRachael Wilterdink  |  
Dec 20, 2018
Avoid having runaway meetings, meetings that go past their time boxes, and meetings that are not for their original purpose. Keep it focused. Create and follow an agenda for the more formal Scrum events –depending on your company and culture. I’ve worked at loose organizations and...
Blog Article
Taking on Too Much Work in a Sprint (Agile Transformation Pain Point #13)
Rachael WilterdinkRachael Wilterdink  |  
Dec 06, 2018
Some teams are super ambitious, and they just think they can climb a whole mountain in a single Sprint, but the whole goal with agile is to maintain a sustainable pace. Take on only what you really think you can get done within your Sprint. Don't overestimate your velocity, and don't...