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
Agile

 

Love our Blogs?

Sign up to get notified of new Skyline posts.

 


Related Content


Blog Article
Top 4 Reasons to Attend WI BADD 2019
Shannon PagelsShannon Pagels  |  
Mar 21, 2019
WI BADD® (pronounced ”we bad”) is the annual Wisconsin Business Analyst Development Day held every May in Madison, Wisconsin (This year’s event will be held on May 15-16.) We are excited to again be sponsors and speakers at this event. Keep reading to learn more about the...
Blog Article
6 Hybrid Business Analyst Combinations
Rachael WilterdinkRachael Wilterdink  |  
Feb 19, 2019
There's been a lot of talk lately (and a lot of requests from our clients) for flexible hybrid roles. Our clients are looking for flexible people who can take on a variety of work to bring a project to fruition.   Here, I'm going to explore some of the more common combination roles...
Blog Article
Skipping Inspection and Adaptation (Agile Transformation Pain Point #20)
Rachael WilterdinkRachael Wilterdink  |  
Jan 31, 2019
Inspecting and adapting is one of the key parts of agile and Scrum. But over time, teams start to feel bored as if every session is the same.   If it does become boring, make sure you switch it up to keep it fresh. The Fun Retrospectives website has lots of ideas. Don’t skip this...
Blog Article
Distributed Global Challenges (Agile Transformation Pain Point #19)
Rachael WilterdinkRachael Wilterdink  |  
Jan 24, 2019
So far, I've been primarily discussing co-located teams, which is ideally better. However, this is the real world, and it's a global economy – most people don't have the luxury of being co-located.   If you have a team with dispersed team members, set up your working...
Blog Article
Accruing Technical Debt (Agile Transformation Pain Point #18)
Rachael WilterdinkRachael Wilterdink  |  
Jan 17, 2019
Everyone who works in technology probably knows that you already have a big pile of technical debt. The problem is that you are going to have to eventually pay that bill, and some of it is risky.     Dig out a little every Sprint You really need to be careful about technical...