Scrum主测试

You are a Scrum Master in an organization that is transitioning to Scrum. You have multiple Scrum Teams working on different parts of a large software product. Each team is working on different features, but those features have dependencies on one another. For example, Team A is working on a feature that cannot be completed until Team B completes another feature.

During the Sprint Planning, Team A chose a user story from its backlog that depends on the completion of a user story from Team B’s backlog. However, Team B can't guarantee that their user story will be done in the next sprint.

What should be the Scrum Master's approach to handle this scenario following Scrum principles?

A: Have Team A start working on the dependent user story with the hope that Team B finishes their part within the sprint.
B: Ask Team A to choose a different user story for this sprint that doesn't depend on Team B's work.
C: Arrange a joint session between Team A and Team B to revise their sprint plans, ensuring dependent user stories are completed in the same sprint.
D: Merge Team A and Team B for the next sprint to ensure they work together on the dependent user stories.
E: Delay the start of Team A’s sprint until Team B completes their user story.

Here’s a sprint burndown chart for team A at SpaceY Inc:

Here’s a sprint burndown chart for team B at SpaceY Inc:

We know the following about the graphs:

- Red line is the the ideal line: projected slope that depicts how the team progress would look like
- Black line is the actual effort line
- Story points are represented on Y-axis
- And time in weeks is represented on X-axis

Which of the following statements are true about SpaceY teams:

P: Team A started slowly and was moving behind schedule. Yet, they managed to finish the sprint in time
Q: Team A is working hard towards meeting the deadline but isn’t updating the burndown chart throughout the process, only at the end.
R: Team A’s next sprint’s capacity should be burned down or decreased so that the team can have to complete tasks/story points from the previous sprint
S: Team B started slowly but eventually caught up
T: Team B might have overestimated the project’s timeline

Emily is a product owner for a new application being built at Whalesforce Inc. To maintain visibility into project status, Emily has cut the project into chunks which different teams will be responsible for:

- DevOps team (DoT) will set up the servers. They have no dependencies and will take 4 weeks to set things up.
- Design team (DT) will design the screens for the application, have no dependencies and need 3 weeks to wrap up.
- Front-end team (FT) will need the designs to start the work, and will take 5 weeks to create the front-end components.
- Backend team (BT) will need input from DoT and DT to start designing the backend system, and will take 3 weeks to release the backend APIs.
- Security team (ST) will require server details from DoT, and will need 3 weeks to give a go-ahead.
- Integration team (IT) will require the front-end components and backend API to set up the integration. They will launch the application in 3 weeks.

The project is marked for internal release once IT and ST teams give a go-ahead.

Emily wants to communicate the best-case estimate for the internal release of the project to the major stakeholders. Can you help her with the estimate?

Seloitte hires PopTal for developing a new mobile application. PopTal team follows Agile methodology for development and estimates the whole project to take up to 1000 points. In the first sprint the team commits to work on the following stories:

Story 1 - 6 points
Story 2 - 10 points
Story 3 - 16 points

The team completes Story 1 and 3 but only completes eighty percent of Story 2. Pick the correct statements:

A: The average velocity of the first sprint is 22 points
B: The average velocity of the first sprint is 30 points
C: Based on the average velocity, the product owner can notify the stakeholders that the project will take roughly 45 sprints to finish (assuming team size and members remain the same)
D: Based on the average velocity, the product owner can notify the stakeholders that the project will take roughly 33 sprints to finish (assuming team size and members remain the same)