Answer: Total cost (23500 hours predicted ) = $ 484625
Explanation:
The question is incomplete the high and low methods requires us to use high and low level of activity together with the corresponding total costs at each level to determine the variable cost per unit. we will provide assumed total costs and nursing hours in order to show how high and low method is used to predict total costs for the next period.
Assume the following were total costs and corresponding nursing hours for the previous 3 months
Total cost Hours
$560000 30000 hours
$400000 220000 hours
$225000 10000 hours
calculating Variable cost using high and low method
Variable cost per unit = (high cost - low cost)/high hour - low hours)
Variable Cost Per unit = (840000 - 225000)/ (30000 - 10000) = 16.75
Variable cost per unit = $ 16.75
Fixed costs = 560000 - (28000 x 16.75) = 560000 - 469000
Fixed costs = $91000
Total cost (23500 hours predicted ) =Total Fixed cost + Total Variable costs
Total cost (23500 hours predicted ) = $91000 + (23500 x $16.75)
Total cost (23500 hours predicted ) == $91000 + $393625
Total cost (23500 hours predicted ) = $ 484625
Answer: <em><u>The Assembly Process</u></em>
Explanation: I hope it helps you!
Answer:
i dont get it, is there a question?
Explanation:
Answer: ScrumMaster should ask the Product Owner which other User Story they would like to give up in exchange for the one they want to add for this upcoming Sprint.
Explanation:
The options to the question are:
a. ScrumMaster should replan the Product Backlog and propose better user stories to address in the Sprint.
b. ScrumMaster should ask the Product Owner which other User Story they would like to give up in exchange for the one they want to add for this upcoming Sprint.
c. Stay out of the way as this is not the ScrumMaster's job to resolve.
d. ScrumMaster should ask the team to take the story on and work overtime.
From the question, we are informed that a team has prepared an estimate for what it can get accomplished in a Sprint and that the Product Owner has wanted more to get accomplished in the upcoming Sprint and therefore wants the team to take on an additional user story.
The best way to tackle this conflict is for the ScrumMaster should ask the Product Owner which other User Story they would like to give up in exchange for the one they want to add for this upcoming Sprint. Since an estimate has already been prepared, taking an additional user story will bring about an overestimation. Therefore, to being the right track, the thing to do is to actually give up a user story for the new one to be added.
