This is the test intended for those who have completed the Scrum brief for new members (18/9/2014)
A complete methodology (phương pháp) that defines how to develop software
A cookbook that defines best practices for software development
A framework with built-in reality checks, within which complex products are developed
A defined and predictive process that conforms to the principles of Scientific Management
Add it to the current Sprint
Add it to the current Sprint while swapping out committed work of equal size
Add it to the following Sprint
Inform the Product Owner so he can work with the CEO
Every Sprint
Every release cycle
Once, at the beginning of the project
Once, at the end of the project
Individuals, as determined during the Sprint Planning Meeting
The team owns them collectively
The ScrumMaster
Individuals, as assigned by the ScrumMaster
Build a thin slice of potentially-shippable (có khả năng chuyển giao) functionality
Nail down the architecture
Develop a detailed plan for the rest of the project
Test the product
Large items at the top to small items at the bottom
Safer items at the top to riskier items at the bottom
Most important items from customer perspective (triển vọng/quan điểm) at the top to least important items at the bottom
Items are randomly arranged
Into categories P1, P2, P3, etc
Planning how to meet a Sprint goal
Monitoring and optimizing the work to meet the Sprint goal at least daily
Monitoring and increasing productivity and learning
Removing impediments
Selecting the Product Owner
Resolving internal conflicts
The Product Owner with input from the Team
The Team after clarifying the requirement
The ScrumMaster
The most senior people in the organization, including architects and subject matter experts
Coding
Testing
Software architecture/design
Business/requirements analysis
User-interface design, user experience, information architecture, etc
Technical writing
Database
True
False
Live demonstration (thuyết minh, trình bày) of a potentially-shippable (properly tested) product increment
Feedback from stakeholders resulting in additional items added to the product backlog
A report about what happened during the Sprint.
A PowerPoint presentation about hypothetical (giả thuyết) things
Applause (tán thưởng).
True
False
Sometimes
Collective opinion of the Team using whatever information they need
Available team hours minus task hours
(available team hours x load factor) - task hours
(available team hours x (load factor + contingency (dự phòng)factor)) - task hours
Only at the end of a release
At the end of each Sprint, before the Sprint Review Meeting
At the end of each Sprint, after the Sprint Review Meeting
Only at the end of a project
Every now and then when the Team wants to improve
Always. The Product Owner should re-prioritize the Product Backlog constantly, as we learn more
Sometimes. The Product Owner should re-prioritize only before the elaboration (xây dựng)stage gate
Never. The Product Backlog should be locked down before Sprinting begins
True
False
The Stakeholders
The Team
The ScrumMaster
The Product Owner
The Business Owner
The CEO
Prior to the Sprint Planning Meeting
During the Sprint Planning Meeting Part Two
During the Sprint
During the Sprint Planning Meeting Part One
At the beginning of the project
Scrum has a few rules. Appendix A in the "Agile Project Management With Scrum"-book by Ken Schwaber is called "Rules."
Scrum has guidelines, not rules
Listen to their communications
Act as a go-between for them
Teach the team to talk in terms of business needs and objectives.
Teach the Product Owner about technologies employed during the Sprints
Monitor the Sprint Burndown Chart to ensure individuals are contributing
Help resolve Team-reported impediments and improve the organization
Organize performance appraisals
Coordinate activities between Scrum teams
Monitor the Daily Scrum meetings and reward team players
Every Sprint
Once per week
Once per day/night
Every time the code changes (potentially many times per day)
As soon as the QA person is available
The Team
The ScrumMaster
The Product Owner
The software architecture department
The team lead appointed by the ScrumMaster
2 times 4 hours for a 4-week Sprint, proportionately(tỷ lệ tương ứng) less for shorter Sprints
At the end of every Sprint
15 minutes
How ever long is needed
As soon as possible after they are identified, assuming they don't reflect a scope change in the Sprint goals or committed Product Backlog Items
When the Product Owner identifies a new task
When the ScrumMaster identifies a new task
When the ScrumMaster approves them
Never. The Sprint Backlog is fixed and decided during Sprint Planning
Wait!
Here's an interesting quiz for you.