1. What is the primary purpose of timeboxing in software development?
Explanation: Timeboxing is a time management technique where a fixed time period (timebox) is allocated to complete a specific task or activity. Its primary purpose is to create constraints that promote focus and efficiency.
2. Which agile methodology commonly uses timeboxed iterations called "sprints"?
Explanation: Scrum uses fixed-length iterations called sprints, typically 1-4 weeks long, which are a form of timeboxing. The team commits to completing a set amount of work within each sprint.
3. What should happen when a timebox expires before a task is completed?
Explanation: When a timebox expires, work should stop and the team should evaluate what was accomplished and what remains. They can then decide whether to create a new timebox, adjust scope, or take other appropriate action.
4. Which of the following is NOT a benefit of timeboxing?
Explanation: While timeboxing helps improve estimation skills over time, it doesn't magically make initial estimates more accurate. In fact, one of the points of timeboxing is to acknowledge that estimates are often wrong and to work within fixed time constraints instead.
5. What is a "timeboxed meeting" in agile practices?
Explanation: Timeboxed meetings have a strict, predefined duration (e.g., daily standups timeboxed to 15 minutes) to ensure efficiency and respect for participants' time.
6. In timeboxing, what is typically done with work that isn't completed within the allocated time?
Explanation: Unfinished work is typically re-evaluated and reprioritized against other work items. It might go into the next timebox if still important, or it might be deprioritized if other work has become more valuable.
7. What is the relationship between timeboxing and the Pareto Principle (80/20 rule)?
Explanation: Timeboxing aligns well with the Pareto Principle by creating constraints that force teams to focus on the most valuable work first, often resulting in delivering most of the value in a fraction of the time.
8. Which of these activities is LEAST suitable for timeboxing?
Explanation: While most routine activities benefit from timeboxing, critical production outages typically need to be resolved as quickly as possible without artificial time constraints that might compromise the solution.
9. What is the recommended maximum duration for a Pomodoro timebox?
Explanation: The Pomodoro Technique, a personal timeboxing method, typically uses 25-minute work periods (called "Pomodoros") followed by short breaks.
10. How does timeboxing help with perfectionism in software development?
Explanation: Timeboxing helps combat perfectionism by creating constraints that force teams to make conscious decisions about when "good enough" meets requirements, preventing excessive polishing at the expense of delivery.