Posted by tac_admin, July 2, 2014

3 Misunderstandings About Agile Methodologies

<" alt="Waterfall" />Agile Methodologies for business analysis…

If you’ve been at this for a while, you’ve probably gotten your fair share of weird looks when you mention Agile. (Trust me, I get the “huh?” question at least three or four times a week.)

When it comes to being a successful business analyst who implements lasting solutions, clear and direct communication is the make-or-break factor. With so much jargon floating around between IT and the less-techy departments, no wonder there are so many misunderstandings about Agile Methodologies.

No worries. In this blog, you’ll discover the 3 most common misconceptions about Agile Methodologies. More importantly, you’ll be able to clear up any misunderstandings that arise as you do your job.

1. Agile doesn’t work for tight deadlines.

If you’re working your way up the BA ladder, you know all too well that dead-lines are paramount. Since Agile Methodologies are team-based, there’s a myth that collaboration leads to late deadlines.

That’s the farthest thing from the truth.

One of the tenants of the Agile Discipline is that self-organization will result in faster turnaround times. Of course, one of the pitfalls is how to implement that self-reliant strategy. No worries, because with IIBA-endorsed Agile education, you’ll know exactly what to do when a deadline looms over your head.

My advice: when every team member knows their role and how important it is, the pieces will all fall into place.

2. “I already use Waterfall Methodologies; why bother with Agile?”

There’s always a reason for talking yourself out of something. Many people are reluctant to Agile, because they’re so comfortable using the same methods. But, if you’re looking to accelerate your career, you need more and more resources in your toolbox.

In fact, it’s especially helpful in your interviews when you can articulate knowledge in both Waterfall AND Agile Methodologies.

Part of your Agile success hinges on communicating progress with stakeholders. When the client is left in the dark, it only creates frustration and confusion. Not only does this hold your career back, but the lack of progress reporting also lessens the effectiveness of Agile all together.

3. “Agile Requirements, What is the Difference?”

Eliciting requirements…

Are your stories and reports detailed enough? If you’re like so many business analysts out there, you’ve experienced what it’s like to not have a thorough report. Long story short: you lose respect…and maybe even confidence.

When it comes to nailing down your Agile requirements, the best practice is to create and maintain and prioritize a product backlog. Think of this as a checklist that lets you know you’re completing every task correctly.

When it comes time to submit those requirements to stakeholders, you’ll have everything you need for a thorough report.

I have so many stories to tell about how my job used to be more difficult than necessary. But…

Once I mastered business analysis with Waterfall AND Agile Method-ologies, that’s when my income skyrocketed and stress level dwin-dled.

Leave a Reply

Your email address will not be published. Required fields are marked *

Get in touch today

Speak directly with The Analyst Coach
and get pointed in the right direction.

Preferred Contact EmailPhone

Subscribe to receive our free white paper on how weak requirements effect strong companies


Sign up to get your FREE Business Analyst Survival Guide

Don't worry, we hate spam too. We will never share your information to third parties.