Back to List

Skipping Over Quality (Agile Transformation Pain Point #16)

Rachael Wilterdink Rachael 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 idea of pair programming, peer checking, doing code reviews for each other, etc. It all helps to improve the quality of your product.
agile has testers

Release and test frequently

Another thing you should avoid is waiting until the end of the Sprint to check your quality, leaving no time for fixing things. This is a waterfall problem. Agile is meant to address many of these issues. Release frequently and keep that cycle time short. As you're finishing things, they can be released to your QA environment so you can test them right away, enabling you to get to your definition of done.

No credit for partially done

If you wait until the end of your Sprint (waterfall style), then you're not going to have enough time to get to Done. Nobody likes to carry things over because there was a critical bug that wasn’t found until the last day and there wasn’t time to fix it. When the Sprint is over, the Sprint is over; you're not going to get credit for something that is not completely Done.

Misconception: agile doesn’t have testers

Though agile doesn’t have an official tester role, agile includes a lot of testing (or it should). Testing and quality is a responsibility of the whole team, not necessarily one person. Even if you had a quality analyst on your development team and their primary role would be for QA, that does not mean that the rest of the team couldn't pick up and help if needed. The idea behind a cross-functional agile team is that each member can bring their skills and talents to the team and work together to get to Done.

Get the free eBook

This is the sixteenth 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


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
“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
Pre-assigning Work to Team Members (Agile Transformation Pain Point #14)
Rachael WilterdinkRachael 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 &ndash...
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...