Final part 1

Question 1

1. How will you define a good quality requirement as a business analyst?

Answer 1

As a business analyst, I look for a good requirement to be complete, consistent, unique, bounded, and testable. A good requirement should also always be unambiguous. Two or more people reading the same requirement should come to the same deduction about its meaning.

Question 2

2. What is Backlog grooming on Agile? What is the main purpose of backlog grooming?

Answer 2

Backlog grooming is a session taken by the project team and product owner to review and groom the product backlog. Grooming in the beginning in the project can be a session where the BA and product owner work on prioritizing and ranking requirements. A grooming session in the middle of the project can take place to rank the user stories for a specific print.

In short, the main purpose of backlog grooming is to decide the stories to work on and in what order.

Question 3

3. If you were provided a requirements document and software design document, what would be the first task you would complete?

Answer 3

I would analyze the documents to make sure they comply the good documentation process before we move any further into the project.

Question 4

4. If you found a defect in the code you were testing and had to report a defect, what details would you provide?

Answer 4

To report a defect found during testing I would provide a visual representation of the defect (screenshots) and where it was found. I would also document the defect with the following information in detail: Defect ID, Defect Name, Defect Description, Defect priority.

Question 5

5. What are the roles and responsibilities of a Business Analyst on Agile environment?

Answer 5

As a BA working in the agile environment, I’m mostly responsible for documenting all aspect of the software development life cycle and analyzing business needs to provide the appropriate solutions. This includes gathering and developing requirements, creating and maintaining the product backlog, documenting processes with the use diagrams. I also liaise with the stakeholders to ensure smooth communication between the technical and business team.

Question 6

6. How do you handle changes to requirements?

Answer 6

Whenever I have received a change request to requirements, the first I have done was to facilitate a joint application development session. In this session, the project team and product owner and stakeholders get together to determine the feasibility of the change to the requirement. If determined feasible, my job would be to document the change and send it through the chain of approval. Once we get a sign off on it from stakeholders, I proceed to updating the product backlog with a new version of the requirement. If determine not feasible, I liaise with the stakeholders to propose alternate solutions.

Question 7

7. Do you think a business analyst should be involved in testing?

Answer 7

I believe it is good for a business analyst to be involved in testing. If you have a solid understanding of how requirements are tested as a BA, it would give you a better understanding of what components to look for in your requirements in order for them to be testable and pass testing. Also being able to wear multiple hats on a project could be very beneficial to both the individual and the project team.

Question 8

8. Write a unix command to find location information of working directory

Answer 8

To find location information, the command to use would be ls

Question 9

9. What command do you use to find files details information in a Directory?

Answer 9

Look up

Question 10

10. What command do you use to change a directory

Answer 10

To change a directory, the command to use will be cd dirname