What are acceptance criteria?
• a list of tasks the development team needs to complete, before
marking the user story as "done"
• a list of test scripts for the QA team to run
• the mini project plan for each user story
• the conditions and scenarios that establish when the user
story is functioning as expected for the user
The BA and the project manager collaborate and share
responsibility in several key areas. What are these areas?
• creating the requirements plan, managing the budget, updating the
schedule variance, and testing the product
• scoping and planning, communicating with the team and
stakeholders, stakeholder relationship building, and risk
management
• conducting a needs assessment, creating the project schedule,
writing requirements, and facilitating requirements approval
• meetings
• creating the business case, conducting requirements workshops,
reviewing process models, and evaluating solution performance
What best describes how a business analyst works with different
levels of detail as they work?
• First, the Business Analyst meets with the Project Manager and
Technical Lead, using the Technical work breakdown structure as
a guide to structure requirements and analysis.
• First, the Business Analyst gathers all the details about the desired
solution from the business leaders and users, then documents all
the details gathered for the implementation team.
• First, the Business Analyst analyzes details of how the technical
systems work. They then identify the current state of the business
process and write a detailed spec document.
• First, the Business Analyst needs to understand the context
and big picture, then they elicit and analyze in various levels
of detail, resetting back to the big picture often to ensure
alignment and focus as they work.
You've been informed that a stakeholder has changed a
requirement. What steps should you take first?
, • Make an effort to understand the change, its significance, and
the impact it may have.
• Inform the stakeholder that this is not acceptable and they must
delay any changes until after implementation.
• Make the necessary changes to the documentation, updating the
requirements document, user story, and traceability matrix.
• Explain to the stakeholder that this change will cause delays and
cost overruns. Try to talk them out of this change.
You are interviewing a business leader about their request for a
new order status screen on their website. What is a good question
to start the interview with?
• I have reviewed your sample screen mock-up, thanks for doing
this! Do you want the user to be able to save their work before
submitting?
• To understand your request better, can you tell me about
what success looks like from your point of view?
• I see you would like a new screen on the system to show the
status of the order, which database field should we use for the
status?
• Your request makes sense to me! So, what user permissions are
needed for this screen?
When using process modeling techniques, BAs typically start with
—
• the details in an activity flow, because the big picture is usually
already known by everyone
• the system big picture flow, then the integration points of the
system data
• the details of the system first, then map to the flow of the users
• the big picture first, then delve into other areas as needed
Once a solution is implemented, what does a BA do to evaluate and
monitor the solution value?
• Evaluate metrics established, continue to observe users and
data, conduct interviews, and determine adjustments.
• Once the project is done, the BA moves on to another project, so
there are no activities unless the business submits a follow-up
request.
• Keep running the test cases each week, report the status, and
monitor the defects and resolutions.
• a list of tasks the development team needs to complete, before
marking the user story as "done"
• a list of test scripts for the QA team to run
• the mini project plan for each user story
• the conditions and scenarios that establish when the user
story is functioning as expected for the user
The BA and the project manager collaborate and share
responsibility in several key areas. What are these areas?
• creating the requirements plan, managing the budget, updating the
schedule variance, and testing the product
• scoping and planning, communicating with the team and
stakeholders, stakeholder relationship building, and risk
management
• conducting a needs assessment, creating the project schedule,
writing requirements, and facilitating requirements approval
• meetings
• creating the business case, conducting requirements workshops,
reviewing process models, and evaluating solution performance
What best describes how a business analyst works with different
levels of detail as they work?
• First, the Business Analyst meets with the Project Manager and
Technical Lead, using the Technical work breakdown structure as
a guide to structure requirements and analysis.
• First, the Business Analyst gathers all the details about the desired
solution from the business leaders and users, then documents all
the details gathered for the implementation team.
• First, the Business Analyst analyzes details of how the technical
systems work. They then identify the current state of the business
process and write a detailed spec document.
• First, the Business Analyst needs to understand the context
and big picture, then they elicit and analyze in various levels
of detail, resetting back to the big picture often to ensure
alignment and focus as they work.
You've been informed that a stakeholder has changed a
requirement. What steps should you take first?
, • Make an effort to understand the change, its significance, and
the impact it may have.
• Inform the stakeholder that this is not acceptable and they must
delay any changes until after implementation.
• Make the necessary changes to the documentation, updating the
requirements document, user story, and traceability matrix.
• Explain to the stakeholder that this change will cause delays and
cost overruns. Try to talk them out of this change.
You are interviewing a business leader about their request for a
new order status screen on their website. What is a good question
to start the interview with?
• I have reviewed your sample screen mock-up, thanks for doing
this! Do you want the user to be able to save their work before
submitting?
• To understand your request better, can you tell me about
what success looks like from your point of view?
• I see you would like a new screen on the system to show the
status of the order, which database field should we use for the
status?
• Your request makes sense to me! So, what user permissions are
needed for this screen?
When using process modeling techniques, BAs typically start with
—
• the details in an activity flow, because the big picture is usually
already known by everyone
• the system big picture flow, then the integration points of the
system data
• the details of the system first, then map to the flow of the users
• the big picture first, then delve into other areas as needed
Once a solution is implemented, what does a BA do to evaluate and
monitor the solution value?
• Evaluate metrics established, continue to observe users and
data, conduct interviews, and determine adjustments.
• Once the project is done, the BA moves on to another project, so
there are no activities unless the business submits a follow-up
request.
• Keep running the test cases each week, report the status, and
monitor the defects and resolutions.
