Final Part 2 Flashcards
- Explain the difference between traditional Waterfall model and Agile ?
The main difference between waterfall and agile is their approach. Waterfall follows linear sequencing of steps where one has to be done before you move onto the next one. Agile is the complete opposite as it allows you take multiple steps at one time in a series of iteration until you deliver the finished product.
Waterfall doesn’t allow you to backstep or allow change. Agile’s flexibility welcomes and change and allows the project team to make revisions to the product.
- What is Product backlog & Sprint Backlog?
A product backlog is a document that contains all the user stories that will go into the system once complete. This can be compared to a business requirement document in the waterfall environment.
A sprint backlog contains only the stories that will be used for that particular sprint. A sprint backlog is put together during the sprint planning ceremony.
- Explain the life cycle of a Sprint?
A sprint is a determined amount of time (usually 2 weeks) that an agile take to work on chosen stories and deliver a product at the end of the sprint.
A sprint begins with the planning ceremony during which the project team and product owner get together to decide on the stories to work on for that sprint. Once work is done on the stories and codes have been developed and tested, the team prepares for the sprint review session where with the product owner the review the product delivered and compare the actual results to the results they planned to achieve before the sprint. Next, would be the sprint retrospective session. In this session, the agile team looks back on the sprint and determines its shortcomings, issues they encountered, what went well and what didn’t, and what to improve on for future sprints.
** A daily stand-up meeting is conducted each day of the sprint regardless of the phase. This is a quick meeting that enables team members to update each other on status of their tasks and any issues they have encountered.
- What is a use case and when would you use it as a Business Analyst?
A use case is a diagram that describes the interaction of a user with a system to complete a task. A use must have the following components: Primary actor/actress, Supporting actor, and a System.
As a BA I have not only used use cases to describe how a user can complete a particular using a system, but to also gather requirements.
- Describe a situation where you used business analysis techniques to gather business requirements from stakeholders. Which techniques did you use and why did you choose those techniques?
As a business analyst, I have mainly used use case to gather requirements per company policy. To gather requirements using use cases, I ask questions such as who is the system being built for to determine my actors, what is the system being built for to determine the capabilities or functionalities of the system. Once I have all those information down, I can then join the actors to their functions by association lines. I used this technique because the diagram provides me with a visual representation of the system to be built and how it’s going to be used. I can then proceed to developing requirements using the use case.
Another technique I have used is to analyze documents from the planning phases to identify users and their functionalities
- What is the main or key purpose of writing test cases? How do you write test cases?
Test cases are written to verify the functionality of requirements. Their purpose is to determine if a requirement or functionality works as expected and satisfies business needs.
To write test cases, I make sure I have a test cases ID, description, the acceptance criteria, the requirement I’m testing for RTM purposes, any data available, the environment, and any dependency.
- List out the documents that are used by a BA in a Project?
As a BA, the documents I mainly use on my project are product backlog, sprint backlog, different process flow diagrams. When I’m involved in testing, I use test cases, RTM, and test summary
- Describe a situation when you were unable to deliver one of your requirements documents on time. What did you do?
On my last project we’ve had a sprint where I wasn’t able to deliver one of my requirements on time due to an existing contradictory requirement. To fix that issue I reached out to the product owner to facilitate a backlog refinement meeting. In the meeting It was determined that one of the requirements should haven’t been written and it was a result of miscommunication.
- What is version controlling system? Do you use any version controlling system to maintain change on documentation and coding?
A version controlling system is a system that records all the changes made to a file over time during the software development process. I have experience using the GIT software as it was the tool used on my last project.
- How can you handle and manage the difficult stakeholders?
As a BA, I believe being able to understand stakeholders and communicate with them is the key to establishing a good relationship. As a BA
