Agile Business Analysis

You open a Business Analyst website like http://www.modernanalyst.com, read blogs or receive a digest email from Business Analyst groups and communities; Agile Business Analysis is a hot topic coveredin blogs or discussed in groups/communities these days.

This blog on Agile is actually to keep myself into this Agile Season and to give my readers an idea about Agile Business Analysis.

By using Agile methodolgy, project deleivery is chopped up into short iterations – one-to three-week timeboxes depending on the project lenght. Each timebox begins with an iteration planning workshop in which the customer decides which wok should be delivered.

It is the cutomer’s responsibility to select the highest priority requirements from the requirements catalogue.

The selected requirements are built by developers and demonstrated to the customer. During the User Acceptance Criteria, preparations are made for the next possible iteration.

Most of the companies currently not practising Agile processes. There are advantages and disadvantages of using Agile iteration technique. But one thing i should emphasize on is to keep the balance on iterations. The overall project scope should not go beyond the control limits.

In my next blogs, i will write about How Agile Practices Reduce Requirements Risk.

Happy reading!

Tags: , ,

5 Responses to “Agile Business Analysis”

  1. Ed Taaffe Says:

    The toughest thing I find when doing Agile is to maintain sufficient discipline. Agile is just so flexible it is all too easy to lose the discipline.
    What a breath of fresh air though if you have been used to disciplines like Prince 2 .

  2. Kashif Says:

    Hi Ed,

    Thank you for visitng my website and leaving comments.

    My main concern using Agile is to watch the boundries of the project. It should not increase the expectations of the customer and also should not go beyond the deadlines.

  3. Ellen Gottesdiener Says:

    Hi Kashif:
    thanks for your blog comments. analysis is still vital to agile projects. indeed, i think that analysis on agile projects is even more challenging, and rewarding, than traditional development.

    as to Ed’s comment, i find agile done right is //very// disciplined.

    Kashif, you mentioned in your next blog you are writing about how agile practices reduce requirements risks. Well what a coincidence! ;-)

    i published an article on that very topic and title. I hope you and your blog readers might be interested in, in Better Software (July/August issue). here is the link:

    http://www.nxtbook.com/nxtbooks/sqe/bettersoftware_0709/index.php?startid=14&elq=6AACF5E07B9B437791A069956AC9C442#/16

    all the best,
    ~ ellen
    http://www.ebgconsulting.com

  4. Peter Says:

    Interesting and informative. But will you write about this one more?

  5. Kashif Says:

    Hi Ellen,
    Thank you for your thoughtful inputs. I agree that analysis on Agile projects is more challenging and rewarding.

    I couldn’t open the provided link but i will try again and i believe it would be helpful for me and my readers.

    I would expect/appreciate your comments in future as well.

    @Peter, Thank you for your comments. I would definitely write more about this.

Leave a Reply