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
How to Use a Glossary to Model and Analyze BI Requirements
Rachael WilterdinkRachael Wilterdink  |  
Jun 13, 2019
If you’re involved in eliciting, modeling, analyzing, or consuming requirements for BI projects, this post is for you. Over the next several months, we will be releasing 10 Techniques for Business Analysts (BAs) to model and analyze Business Intelligence (BI) requirements on our blog...
Blog Article
Why Did Our Team Succeed? (Habits of a Successful Agile Team)
Rachel RieckRachel Rieck  |  
Jun 06, 2019
If you have experience on agile teams and are looking to tweak a few things or try something different, then this blog series is for you. Our Solutions Consulting Director shares proven strategies and tactics she learned from a pivotal agile journey that you can use to capitalize on your current...
Blog Article
How Business Analysts Can Help Maximize Project ROI
Tim MorrowTim Morrow  |  
Jun 04, 2019
In my career as a Business Analyst (BA) over the past decade or so, I've been involved with many different projects and project teams. Some have been wildly successful with a great ROI, happy stakeholders and project team…and some have not. The most successful ones have been done on...
Blog Article
How to Use Decision Modeling to Model and Analyze BI Requirements
Rachael WilterdinkRachael Wilterdink  |  
May 30, 2019
If you’re involved in eliciting, modeling, analyzing, or consuming requirements for BI projects, this post is for you. Over the next several months, we will be releasing 10 Techniques for Business Analysts (BAs) to model and analyze Business Intelligence (BI) requirements on our blog...
Blog Article
How to Use Data Modeling to Model and Analyze BI Requirements
Rachael WilterdinkRachael Wilterdink  |  
May 23, 2019
If you’re involved in eliciting, modeling, analyzing, or consuming requirements for BI projects, this post is for you. Over the next several months, we will be releasing 10 Techniques for Business Analysts (BAs) to model and analyze Business Intelligence (BI) requirements on our blog. The...