A) Eliminate the use of project planning and testing
B) Only essential work products are produced
C) Process allows team to streamline tasks
D) Uses incremental product delivery strategy
A) Requirements gathering must be conducted very carefully
Risk analysis must be conducted before planning takes place
Software increments must be delivered in short time periods
Software processes must adapt to changes incrementally
Both c and d
What did you do since the last meeting?
What obstacles are you encountering?
What is the cause of the problems you are encountering?
What do you plan to accomplish be the next team meeting?
Burn Down chart
All the above
All of the above
Mutual trust and respect
All of the above
When all committed product backlog items meet their definition of done.
When Timebox expires
When all tasks are complete
Once, at the beginning of the project
Once, at the end of the project
Every release cycle
Individuals, as assigned by the scrum Master
The Scrum Master
The team owns them collectively
Individuals, as determined during the sprint planning meeting
To accelerate our understanding of the user’s real needs
To get more features out
The declining energy level of the team
The progress of the work and features completed
The number of hours worked after dark
The rate of reduction of budget for a project
The rush during the last few weeks of the project
A period of high productivity during the start of the project
A “time-boxed” period of “potentially shippable” work
It allows the team to take a welcome break from work
It gives management information to use in performance reviews
It allows learning that can be used to improve team performance
It prevents deviation from the process the team has been following
The people who are afraid to undertake the project
The project mascots
People who contribute to the project
The people who are committed to the project
Sprint retrospective meeting
Product review meeting
Sprint review meeting
Stakeholder review meeting
Teams work less well when it rains
Keeping metrics of earlier work to help with future estimates
Retrospectives should include less important topics such as the weather
Estimating is as futile as predicting the weather
Always. The product Owner should re-prioritize the Product Backlog constantly we learn more.
Sometimes. The product Owner should re-prioritize only before the elaboration stage gate.
Never. Due to the “Cost of change” curve , The product Backlog should be locked down before Sprinting begins.