Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Business Proces...  Your steps as a BA with a new project!
Previous Previous
 
Next Next
New Post 1/8/2013 6:26 PM
User is offline ludasky
5 posts
10th Level Poster


Your steps as a BA with a new project! 

 Hi guys,

 

What are steps as a BA that you usually take for a new project? The reason im asking is because there is so many different type of BAs out there I just want to see if we all follow some type of trends or some people make their own type of steps. Discussion would be great on this.

 
New Post 1/10/2013 8:07 AM
User is offline Tony Markos
493 posts
5th Level Poster


Re: Your steps as a BA with a new project! 

Here are REAL WORLD steps fro  Business Analysis in a very Agile fashion:

*  Logically, naturally  partition the essential behavior (irregardless of whether automated or manual) of the business at hand.  Decompose downard a few levels.

*  In doing the above, pay special attention to the essential interrelationships between the above chunks of behavior.   These essential interrelationships are the input/output data flows.

*  Break down the data flows into small items and then create a dictionary of terminology.

*  Use the dictionary to create some higher level  data models.

*  Given all the above, create some hypotetical screen shots.

Give all the above to the development and testing staff and let them hash out the details through discussions.

Tony

 

 

 

 

 

 
New Post 6/12/2013 5:59 AM
User is offline Jayman21
28 posts
9th Level Poster


Re: Your steps as a BA with a new project! 

 Regardsless of the type of project  I am involved in I will utilise the following steps:

1. Conduct a feasibility study to capture an understning of:

- Who the stakeholders are

- the reason for the roject

- What the project hopes to delivery to the business (the objectives of the project)

- The business processes associated with the project (As Is)

- The IT systems and data information related to the project (if a technical project)

- Possible constraints which could hinder your work.

2.  With the background information you have start your requirements gathering excercise with the stakeholders

3. Validate requirements and develope your business requirement documents (this is where tools, techniques, concepts etc come into place such as Use Cases etc plus background information you may have already captured initially such as As Is business processes etc)

4.  Signoff documents

5. Continue to design, development etc

 

 

 
New Post 6/14/2013 3:05 AM
User is offline surreyfrog
5 posts
10th Level Poster


Re: Your steps as a BA with a new project! 

 Jayman21 wrote
 

 Regardsless of the type of project  I am involved in I will utilise the following steps:

1. Conduct a feasibility study to capture an understning of:

- Who the stakeholders are

- the reason for the roject

- What the project hopes to delivery to the business (the objectives of the project)

- The business processes associated with the project (As Is)

- The IT systems and data information related to the project (if a technical project)

- Possible constraints which could hinder your work.

2.  With the background information you have start your requirements gathering excercise with the stakeholders

3. Validate requirements and develope your business requirement documents (this is where tools, techniques, concepts etc come into place such as Use Cases etc plus background information you may have already captured initially such as As Is business processes etc)

4.  Signoff documents

5. Continue to design, development etc

 

 

 

lets say I have modelled some processes using a conventional modelling technique, lets say I break the process down to lower level activities and show their sequecnce.

t some point I will need to go from that model to a use case model. How would I identify use cases from the process model (or, rather, map them to the process model). For instance, would there be a one - to - one mapping between a use case and an activity on the process model, or would many activities combine to map onto a use case? If the latter, how do I decide what will make up a use case? And a final question, will the use cases only describe those parts of the business that involve a person using a computer or would they descroibe all aspects of the business, even those that are not computerised?

 
New Post 6/18/2013 5:27 AM
User is offline Tony Markos
493 posts
5th Level Poster


Re: Your steps as a BA with a new project! 

Surryfrog asks:  For instance, would there be a one - to - one mapping between a use case and an activity on the process model, or would many activities combine to map onto a use case?  If the latter, how do I decide what will make up a use case?

Great question Surryfrog!   What your asking about is how to partition.  And partitioning largely defines what analysis is all about (though you would never hear such reading popular BA related literature).

 There is only one formal way to do a logical, natural partitioning of a business system:   Perform an analysis of essential interfaces (the essential interfaces are data flows.)    The alternative is do a Sledge Hammer partitioning:  Just wack at it until you force a resolution to your problem.     The problem with this second approach is that while you can always partition an entity with a sledge hammer, the results are often not very useful.

 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Business Proces...  Your steps as a BA with a new project!

Community Blog - Latest Posts

A business analysis checklist helps you stay organized while you work through projects. It includes questions that will help you identify problems in your current processes, and suggest improvements for future projects. Understand the Problem Before you start writing code, you need to understand what problem you're solving. This means u...
I’ve heard “The End is Near!” for Business Analysts for almost 20 years.  Waterfall project management, with its need for formal requirements, is dead…a dinosaur…so 1990’s.  To be honest, that’s mostly true.  With the publishing of the Agile Manifesto in 2001 there was no need for a 2-inch-...
Business analysis is used to identify and articulate the need for change in how organizations work, and to facilitate that change. As business analysts, we identify and define the solutions that will maximize the value delivered by an organization to its stakeholders. We look for opportunities for new business models and new ways to work together. ...

 






 

Copyright 2006-2022 by Modern Analyst Media LLC