Of the following activities from the Systems Development Process Framework, which typically requires most of a projects calendar time and budget:

		Iterative construction/configuration.
		Project planning and implementation approach selection
		Functional and initial technical design.
		Initial visioning.
		Business analysis.

5 points

QUESTION 42

A user story:

		Defines what capability the system should provide the user.
		Generally specifies how the system should provide a feature.
		Is a technical component that needs to be created.
		Must be broken down into engineering tasks when creating the burndown chart.
		None of the given answers are true.

5 points

QUESTION 43

Regarding sprint capacity:

		Actual sprint capacity equals the number of team members times the number of days in the sprint.
		The length of each sprint may be adjusted upward to accommodate large or complex user stories or engineering tasks.
		Maximum sprint capacity equals the number of team members times the number of days in the sprint.
		None of the given answers are true.
		Maximum sprint capacity can be increased by adding in technical debt and staff absences and interruptions.

5 points

QUESTION 44

As a sprint executes, the estimated effort remaining for a sprint story or task:

		Stays the same until the scrum master okays a developers progress in the stand-up meeting.
		Should not be re-estimated until the planning for the next sprint has occurred.
		Stays level until the story or task has been unit tested.
		May go up as a developer works on the story or task, depending on actual progress.
		Will stay the same until a developer begins to work on it, at which point it will decline.

5 points

QUESTION 45

A stand-up meeting is used to conduct:

		The weekly status meeting.
		The sprint retrospective.
		The sprint review.
		The Scrum of Scrums.
		The daily meeting of project team members.