Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  New to Agile
Previous Previous
 
Next Next
New Post 12/8/2010 5:09 AM
User is offline Tony Markos
493 posts
5th Level Poster


Re: New to Agile 

So, what does a Business Analyst do on an Agile project?

Tony

 
New Post 2/18/2011 11:33 PM
User is offline SteveBoulanger
38 posts
9th Level Poster


Re: New to Agile 

 vidya967 wrote

 Hello Phill

I hope it is already been 4 months for you working on Agile methodologies

I just joined this group and I could see your question but could not find any satisfying answer so I would like to share what I know

1. Agile is a Methodology (Not a model or a framework) under which you have different models such as Extreem programming, Scrum and DSDM etc. but most prominently used models are Extreem programming and Scrum

2. Agile is known as Light weight model because it has No or less documentation present in it.

3. Agile best suits for the projects where the delivery of the application or the product is immidiate in nature.

4. Through Agile methodology you actaully deliver a project or a part of a project with in short periods

5. Here Developers are kings and they run the whole show and client interaction (participation is the project)  is high and feed backs are rapid

6.some times the product can be developed and delivered to the client with in 30 days

7. Code it self is the documentation and their by further enhancements in future might take little longer

8. By this methodology one can give a quality product but their will always questions arises on it's architecture and design ( it will not have robust architecture i.e scalability and extendability of architecture).

I got some content this might help you

 

Best practices for increasing the agility of documentation:

  1. Writing

  2. Simplification

  3. Determining What to Document

  4. Determining When to Document

  5. General

 

 

I am trying to throw some light on this and do write me if you need more information.

regards

Sagar

Hey!

You have good knowledge about agile I like him fast service and I hope developers also good. 

 
New Post 9/22/2011 1:34 AM
User is offline bernard
18 posts
9th Level Poster


Re: New to Agile 

Hi Tony,

As far as I can see - a BA isn't a requirement for a SCRUM team.

 

 ajmarkos wrote
 

Hi:

So what exactly does a BA do on an Agile project?  Something more concrete that "just enough", "update only when it hurts", or "document with a purpose".  

Tony

 
New Post 9/26/2011 12:00 PM
User is offline dldelancey
61 posts
8th Level Poster


Re: New to Agile 

As a BA on a Scrum project, I do all the same things I would do on any other project.  I identify stakeholders and their interests.  I don't necessarily have to write it down, but I do have to determine who are the pigs and who are the chickens.  I get to the root of what the business really needs and produce a list of actors and features.  I coordinate requirements gathering sessions, both formal and informal, with the development and testing team present along with the users.  With my list of features as my guide, I use BA techniques as old as time to prod and poke until everyone understands a handful of small tasks that need to be accomplished.  A question I end up asking a lot is, "Do you know what you need to know in order to complete the task assigned to you?."  If the answer is yes, I take a picture of my whiteboard and move on.  If the answer is no, I either poke and prod some more, or I guide the team to make a decision about whether or not it's okay that we don't know this thing yet, whatever it might be.  If someone starts gold-plating, I steer the team back to the original feature list.  If someone suggests doing something that contradicts something else we decided two sprints ago, I tell them so.

I could go on, but you get the picture.  It's the same stuff, the same techniques, but the deliverables are different.  Whether you tack up index cards, or you use a software tool, it's really nothing new under the sun.  What you actually produce as deliverables is really up to the stakeholders, but user stories are typical.  In my organization, we produce something closer to a use case than a user story.  The important part is that the entire team fully understands what is expected.

Your next question may be, "Why can't the developers do this?"  Well, they can.  However, in my experience, most developers want to develop, not lead this kind of interaction or get too involved in the big picture.  Management prefers it that way, as well.  When you're churning out a shippable product in 4 weeks, you want the developers to be doing more of what they do best.

 
New Post 10/1/2011 1:35 PM
User is offline Tony Markos
493 posts
5th Level Poster


Re: New to Agile 

 

Hi:

The major contribution a BA makes on an Agile project is to come up with a just-good-enough big picture.  This is used to scope the project and to plan the iterations.

Key points:  Just-good-enough does not mean poor quality.  It means capturing the essential relationships between high level requirements.

Tony

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  New to Agile

Community Blog - Latest Posts

Gen1us2k
Gen1us2k
Most of the IT projects imply constant cooperation between the team members and customers. Although it might be often overlooked, the role and the importance of the client within the project is very crucial. Thus, it is in your interest to build a strong relationship based on trust. However, gaining trust on a single occasion is not a dealmaker &md...
0 Responses
emorphistechno
emorphistechno
Introduction In today's world, most enterprises work aggressively to achieve a higher level of business growth, which is made possible by leveraging one of the best automation technologies. One such technology is Robotic Process Automation (RPA) that plays a vital role in streamlining the customer experience in the most profitable manner.&nb...
0 Responses
Nick Stowers
Nick Stowers
Introduction   When I was introduced to scrum, the burndown chart was a tool that was highly emphasised however I feel the purpose has changed from it being a tool to predict (to a certain level) timescales for delivery to a tool that measures a team’s productivity…..in other words, the focus is on the number of points clear...
0 Responses






Latest Articles

Copyright 2006-2020 by Modern Analyst Media LLC