Project Management

The Ethics of Over-Allocation in Sprints. Debating Whether Pushing Teams Beyond Sustainable Velocity Breaches the Ethical Mandate for Respect Toward Human Capital

From the The Agile Enterprise Blog
by
"The Agile Enterprise" explores Agility at the Enterprise level, examining how Agile principles can be implemented throughout the organization beyond IT. The blog is inspired by the concept of an Agile Enterprise, introduced by the Agile Manufacturing Forum (1991) and the Manifesto for Agile Software Development (2001). Agility is examined from a Project Management perspective with a focus on areas not covered by frameworks that emerged from the work of small software development teams, such as Risk Management, Ethics, Organisational Change Management and Financial Management.

About this Blog

RSS

Recent Posts

The Ethics of Externalising Risk: Rethinking “Fail Fast” and MVP in Product Development

Quantum Physics for Year 3: Agile success as a foundation for AI. An Ethical reflection

The Tribe Agile Coach role and the spirit and values of the Agile Manifesto. An ethical reflection

AI Ethics and Agile Delivery: Navigating Bias, Privacy, Fairness, and Transparency in a Fast-Moving World

Navigating the Ethical Landscape of Project Management: Insights and Recommendations

Categories

Agile, Artificial Intelligence, Benefits Realization, Change Management, Communications Management, Complexity, Consulting, Decision Making, Disciplined Agile, Diversity, Earned Value Management, Estimating, Ethics, General, Governance, History, Innovation, Knowledge Management, Leadership, Lessons Learned, Metrics, Organizational Culture, Product Management, Risk Management, Scope Management, Scrum, Social Impact, Stakeholder Management, Teams, Testing/Test Management, Using PMI Standards

Date

linkedin twitter facebook Request to reuse this  

Categories: Agile, Ethics, Leadership


Introduction

In the fast-paced world of software development and Agile project management, the concept of the “Sprint”, also called “Iteration”, has revolutionised how product development and sometimes even project work is planned and delivered. Sprints promise rapid, incremental progress and iterative adaptation to user needs. In principle, they also foster a sense of urgency and achievement. However, as the management demands faster results and more output, a troubling trend has emerged: the over-allocation of tasks and responsibilities during Sprints, often pushing teams beyond their sustainable capacity to deliver. This practice raises an important ethical question—does repeatedly demanding more than what is sustainable breach the fundamental Agile value of Respect for human capital?

This blog post analyses the ethical considerations surrounding over-allocation in Sprints, examining the challenges it poses and exploring recommendations for ethical project management. It is a discussion on how organisations can balance ambition with respect for their most valuable asset: people.

Challenges

The Temptation of Over-Allocation

Managers, Product Owners included, often feel pressure to maximise productivity, especially under tight deadlines or when stakeholders demand quick wins. This pressure can manifest as over-committing teams to more work than they have historically demonstrated they can complete within a Sprint—their “sustainable velocity.” Their rationale is simple: if a team did 30 story points last sprint, why not push for 35 or 40 this time?

The Human Cost

While the intention might be to “stretch” teams to achieve more, sustained over-allocation erodes morale and trust. Team members may begin to experience chronic stress, burnout, and a sense of being undervalued. High turnover, diminished quality of work, and disengagement are often the consequences. Furthermore, over-allocation contradicts the Manifesto for Agile Software Development’s call to “build projects around motivated individuals” and “give them the environment and support they need.”

The Ethical Dilemma

At its core, the Agile principle of Respect is about honouring the capacity, skills, and well-being of each team member. When leaders knowingly exceed a team’s sustainable velocity, they risk treating people as mere resources rather than as humans with limits, needs, and intrinsic motivation. This raises the ethical question: Is it acceptable to sacrifice human well-being for perceived short-term gains?

Organisational Culture and Systemic Issues

Over-allocation is rarely an isolated incident. It often reflects deeper systemic issues—such as unrealistic stakeholder expectations, lack of psychological safety, and a culture that values output over outcomes. Teams may feel unable to speak up about unsustainable workloads, and leaders may ignore warning signs to avoid difficult conversations with upper management.

Recommendations

Embrace Transparency

Organisations should foster an environment where teams can honestly communicate their sustainable pace (aka ‘velocity’) and any impediments they face. Transparency ensures that Sprint planning is grounded in reality, not wishful thinking.

Prioritise Psychological Safety

Leaders must create a culture where team members feel safe to express concerns about workload without fear of reprisal. Psychological safety is foundational to ethical decision-making and healthy team dynamics.

Respect Sustainable Pace

Sustainable pace is not merely a metric—it’s a reflection of a team’s collective capacity and well-being. Honour this metric by resisting the urge to over-commit. Instead, focus on removing impediments and supporting continuous improvement.

Empower Teams in Planning

Involve teams directly in estimating and committing to Sprint goals. Empower the team to take ownership and deliver high-quality work. Top-down allocation undermines trust and motivation.

Educate Stakeholders

Stakeholders may not always understand the implications of over-allocation. Invest in education and set realistic expectations about what can be achieved sustainably. Highlight the long-term costs of burnout and turnover versus the benefits of a healthy, motivated team.

Lead by Example

Leaders, Product Owner and Scrum Master included, should model respect for human capital by setting boundaries, encouraging work-life balance, and acknowledging the effort behind every sprint. Recognise and reward sustainable practices, not just heroic efforts during crunch times.

The Bottom Line

Over-allocation in Sprints is more than a productivity challenge—it’s an ethical issue that tests an organisation’s values and culture. Pushing teams beyond a sustainable pace may yield short-term results, but it undermines trust, well-being, and long-term success. The ethical principle of Respect is not optional; it is a mandate to treat people as the essential, irreplaceable assets they are. Organisations that honour this mandate will not only achieve better outcomes but will also foster loyalty, innovation, and resilience in their teams.

Questions for Readers

  1. Have you experienced or witnessed over-allocation in Agile Sprints? How did it impact team morale and outcomes?
  2. What strategies have you found effective in balancing stakeholder demands with the ethical imperative to respect sustainable pace?
  3. How can leaders better model respect for human capital in fast-paced, high-pressure environments?


Posted on: July 14, 2026 06:37 PM | Permalink

Comments (2)

Please login or join to subscribe to this item
avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal
An important perspective, Stelian. I agree that repeatedly expecting teams to deliver beyond a sustainable pace raises important ethical questions.

I wonder, however, whether the discussion begins even earlier. In Scrum, Sprint Planning is intended to produce a collaborative commitment, not a top-down allocation of work. When teams no longer have meaningful authority to determine what they can realistically commit to, the issue is no longer simply over-allocation. It becomes a governance problem because responsibility for delivery remains with the team while authority over the commitment has shifted elsewhere.

I also think the ethical argument can go further. Respecting people should not depend primarily on the productivity, innovation or retention they generate. Those outcomes matter, but they are consequences, not the ethical foundation. People deserve respect because they are people, not because they are productive assets or forms of human capital.

Perhaps sustainable performance comes less from asking people to do more than from designing organizations where autonomy, sound judgment and continuous improvement allow people to contribute at their best. When performance depends primarily on increasing demands rather than improving the conditions under which people succeed, the ethical problem begins long before Sprint Planning.

avatar
Stelian ROMAN Project Manager| MicroSafety Carlingford, New South Wales, Australia
Luis, I agree. The discussion must start much earlier. At the time of considering Scrum/Agile as an option. When the Scrum Master is a re-labelled project manager, paid less, who assigns tasks, monitors progress and prepares weekly reports, that's not Scrum and pretending that what the team does is Scrum is unethical.

Please Login/Register to leave a comment.

ADVERTISEMENTS
ADVERTISEMENT

Sponsors