帕金森定律
工作会膨胀，直到填满可用于完成它的全部时间。
显示原始英文内容
Parkinson's Law
Work expands to fill the time available for its completion.
Takeaways
- If you give a task an overly long timeline, people tend to use all of it (or procrastinate until the last minute), so the task takes as long as the deadline allows.
- Giving more time, teams often do polishing (gold-plating) or add minor improvements that aren't strictly necessary, just to use the whole time allotted for the task.
- A bit stronger (but realistic) deadlines can counteract Parkinson's Law by having a sense of urgency (called deadline-driven development).
Overview
This law shows a common problem with time management among developers. If a developer is given two weeks to complete a task that could be done in two days, the work will usually slow down, consuming most of that time. People might spend more time planning, bikeshedding minor details, or simply delaying the start of the work with the understanding that they have enough time.
Parkinson's Law is often used to warn that loose deadlines reduce productivity, so teams should set clear, realistic time limits. However, managers must use it judiciously, combining Parkinson's insight with realistic scheduling. If you compress timelines too much, you risk running into Hofstadter's Law, which reminds us that work often still takes longer than expected, even with buffers.
Examples
A developer should write a module and is told, "Take as long as you need, maybe a month or two." In many cases, the developer will not rush to finish it, perhaps experimenting with multiple implementations or polishing noncritical items. The same task, if given a one-week deadline, might have been completed in a week.
Agile teams sometimes apply Parkinson's Law by time-boxing tasks. The fixed, short time box encourages everyone to focus on completing tasks before the sprint ends.
Similarly, if a meeting is scheduled to last all day, it often will. If the same activity were given a two-hour window, participants would likely focus and complete it within that time.
Origins
Parkinson's Law was first described in an essay by Cyril Parkinson, published in The Economist in 1955, which initially described how bureaucracies expand over time. The phrase has since entered the lexicon of project management.
It's not specific to software, but software teams often see it in action during projects.
核心含义
时间更充裕并不自动带来更高质量。没有清晰范围和截止条件时，任务会吸收额外讨论、修改和等待，最后仍然在临近截止时完成。
合理的时间盒、可交付的中间结果和明确的完成定义，可以减少工作无边界扩张。
实践例子
原本一周可以完成的内部工具，因为预留了一个月，逐渐加入配置中心、权限体系和多个未验证的扩展点，最后既没有更早交付，也变得更难维护。
来源与边界
英国学者 Cyril Northcote Parkinson 在组织管理语境中提出这条观察。复杂任务确实需要缓冲时间，关键是让缓冲用于应对不确定性，而不是默认扩大范围。