Project Management

The Agile Enterprise

by
This blog will explore agility at the enterprise level, examining how agile principles can be implemented throughout the organization—and in departments other than IT.

About this Blog

RSS

Recent Posts

Transparency in Backlog Prioritisation for AI Features

Balancing Model Complexity vs Interpretability, Finding the Sweet Spot in Machine Learning

Fairness vs Performance Trade-Offs in Agile Delivery

Communicating AI Decisions to Stakeholders

Detecting and Mitigating Bias in AI Models During Sprints

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

Date

Metric Integrity, Semiquantitative Traps & Ethics: The Fallacy of Velocity as a Performance Metric

Categories: Agile, Ethics, Estimating

linkedin twitter facebook Request to reuse this  
Introduction
In the fast-paced world of Agile software development, metrics like story points and velocity are commonly used to estimate, plan, and track progress. However, when organizations and leaders start treating these metrics as absolute measures of productivity, they fall into a dangerous trap—one that not only undermines the integrity of the data but can also violate fundamental ethical principles, particularly the pillar of Honesty in data reporting. This blog post delves into the nuances of metric integrity, the pitfalls of semiquantitative metrics, and the ethical responsibilities that come with reporting and interpreting team performance.



Understanding Metric Integrity
Metric integrity refers to the accuracy, consistency, and appropriate use of quantitative and qualitative indicators within an organization. High-integrity metrics serve as reliable guides for decision-making, while low-integrity metrics can mislead, distort, and erode trust. In Agile environments, story points and velocity are designed as tools for internal estimation and forecasting—not for external comparison or performance evaluation.
Yet, the pressure to deliver, combined with a desire for accountability and transparency, often leads to these semiquantitative metrics being misused as hard measures of productivity. The result is a distortion of their intended purpose and the risk of unethical practices—either intentional or accidental.



The Semiquantitative Trap: Story Points and Velocity
Story Points & Velocity: Designed for Relative Measurement
Story points are a relative measure of effort, complexity, and uncertainty that a team assigns to pieces of work (user stories). Velocity, typically calculated as the sum of story points completed in a sprint, is meant to help teams forecast what they can accomplish in the future based on their own historical performance.
Key characteristics:

  • Team-specific: Each team calibrates story points differently. What’s a “3” for one team might be a “5” for another.
  • Non-absolute: Story points have no universal or external meaning.
  • For planning, not judging: Velocity is meant for a team’s internal use, not for comparing teams or individuals.
The Trap: Treating Velocity as an Objective Productivity Metric
When organizations start treating velocity as an absolute, quantitative performance indicator, several problems arise:
  1. False Comparisons: Comparing velocities across teams or over time without context leads to misleading conclusions.
  2. Metric Gaming: Teams may inflate story point estimates to appear more productive, undermining the very value of the metric.
  3. Loss of Trust: Stakeholders lose faith in the metrics when they see them manipulated or misunderstood.
  4. Distorted Incentives: Teams focus on increasing velocity rather than delivering customer value.
This is the essence of the semiquantitative trap: using internally calibrated, context-dependent metrics as if they were objective, external measures.



Ethics in Data Reporting: The Pillar of Honesty
Honesty is a foundational ethical principle in any form of reporting, including data and metrics. Most Codes of Ethics states that professionals should be "honest and trustworthy" and "avoid harm" in their work. Misrepresenting or misunderstanding metrics like velocity can violate this principle in several ways:
1. Misrepresentation
Presenting velocity as a literal measure of productivity—especially to external stakeholders or executives—misrepresents what the metric means. This can lead to flawed decisions and unfair judgments about team performance.
2. Omission of Context
Failing to clarify that story points and velocity are team-relative, not absolute, is a form of dishonesty by omission. Ethical reporting requires transparency about the limitations and appropriate interpretations of data.
3. Encouraging Unethical Behaviour
When teams are pressured to "improve" their velocity, they may consciously or unconsciously inflate estimates or manipulate the process, further eroding integrity and trust.
4. Data Integrity Violations
The misuse of semiquantitative metrics can result in data that does not reflect reality, violating both the letter and spirit of honest reporting.



Real-World Consequences
The consequences of violating honesty in metric reporting are not abstract. Teams and organizations have experienced:

  • Erosion of psychological safety: Team members feel pressured to meet arbitrary targets, stifling innovation and open communication.
  • Decision-making based on flawed data: Leaders make resourcing or performance decisions that are not grounded in reality.
  • Loss of credibility: Once stakeholders discover that metrics have been gamed or misrepresented, trust is difficult to rebuild.



Best Practices: Upholding Metric Integrity & Ethical Reporting

  1. Educate Stakeholders: Ensure everyone—from team members to executives—understands what story points and velocity are (and are not).
  2. Use Metrics for Their Intended Purpose: Keep story points and velocity as internal planning tools, not external performance measures.
  3. Report with Transparency: Always include context, limitations, and appropriate caveats when presenting semiquantitative data.
  4. Watch for Unintended Incentives: Regularly review how metrics are used and ensure they are not creating perverse incentives.
  5. Promote a Culture of Honesty: Encourage open discussions about metrics, limitations, and the importance of data integrity.



The bottom line
Metrics are powerful tools, but with great power comes great responsibility. The fallacy of treating velocity as an absolute measure of productivity is more than just a technical error—it is an ethical one. By understanding the limits of semiquantitative metrics, committing to transparency, and upholding the ethical pillar of honesty, organizations can foster trust, make better decisions, and ultimately deliver more value to their customers.
Let velocity remain what it was meant to be: a guide for teams, not a yardstick for judgment.
How have you seen velocity or story points used (or misused) in your organization, and what impact did it have on team morale, transparency, or trust?
Share your experiences and perspectives below.

Posted on: June 15, 2026 01:14 AM | Permalink | Comments (1)

Goodhart's Law in Agile Delivery: When Metrics Become Targets

Categories: Agile, Ethics, Estimating

linkedin twitter facebook Request to reuse this  
Introduction
In the pursuit of productivity and predictability, organizations often turn to metrics to track progress and drive improvement. In Agile software delivery, measures like story points and velocity have become ubiquitous tools for estimation and forecasting. Yet, as the British economist Charles Goodhart famously observed, “When a measure becomes a target, it ceases to be a good measure.” This principle—known as Goodhart’s Law—captures a dangerous dynamic: when management fixates on metrics as ends in themselves, teams adapt their behaviour to meet the numbers, often at the expense of genuine progress and transparency. This blog post explores how Goodhart’s Law manifests in Agile delivery, why it leads teams to inflate point sizing, and what organizations can do to foster healthier measurement cultures.



Understanding Goodhart’s Law
Goodhart’s Law originated in the context of economic policy, but its implications are universal. The law warns that when a metric is singled out as a performance target, people will inevitably find ways to game the system. The measure stops reflecting the underlying reality and instead becomes a distorted proxy, undermining its original intent.
In Agile software development, common metrics like story points, velocity, and burndown charts are intended to provide insight into team capacity, help with forecasting, and support continuous improvement. But when these metrics become management’s primary focus—tied to rewards, recognition, or even job security—they lose their power as objective indicators.



The Role of Metrics in Agile Delivery
Agile methodologies encourage self-organizing teams to estimate and plan their own work. Story points are assigned to user stories to reflect relative complexity, effort, and uncertainty. Velocity tracks how many points a team completes per iteration, informing future planning.
These metrics were created for internal use only:

  • Story points: Calibrated by and for the team, not meant for external comparison.
  • Velocity: A tool for the team to understand its own rhythm, not a performance metric.
Problems arise when organizations treat these measures as performance targets, comparing teams or setting arbitrary expectations—"all teams should deliver 30 points per sprint"—without regard for context or underlying differences.



How Goodhart’s Law Plays Out: Inflating Point Sizing
The Pressure to Perform
When management starts using story points or velocity as benchmarks for productivity, teams feel pressure to “keep up.” This is especially acute when:

  • Velocity is shared in dashboards visible to leadership or clients.
  • Team performance is compared across organisation(s).
  • Rewards, bonuses, or advancement are tied to hitting certain metrics.
The Response: Gaming the System
Rather than working faster or delivering more value, teams may unconsciously or deliberately inflate story point estimates to make their velocity appear higher. The logic is simple: if a 3-point story is now estimated as a 5, the same work results in a higher velocity. Over time, the relative calibration that made story points useful is lost.
The Consequences
  1. Loss of Predictive Value: Inflated points mean that velocity no longer reflects capacity. Forecasts become unreliable.
  2. Broken Trust: Stakeholders realize the numbers are being gamed, eroding confidence in both the process and the people.
  3. Misaligned Incentives: Teams focus on maximizing metrics, not customer value or quality.
  4. Metric Fatigue: Teams become cynical about measurement, seeing it as a hoop to jump through rather than a tool for improvement.



Real-World Examples
Consider a software organization where leadership sets a target: "Every team must increase its velocity by 20% this quarter." Teams, facing pressure and knowing that points are subjective, simply start assigning higher numbers to similar user stories. Management sees rising velocity, but actual delivery speed and product value remain unchanged—or even decline as teams cut corners to hit the numbers.
In another case, two teams are compared on velocity. One team, with more senior members, estimates conservatively; the other inflates points to look productive. Leadership, unaware of the calibration differences, rewards the second team, sending a clear signal that gaming the numbers is more valuable than honest reporting.



Breaking the Cycle: Healthy Metric Cultures
1. Metrics as Tools, Not Targets
Reframe metrics as aids for learning and planning, not as goals to achieve. Use them to spark conversations, not drive competition.
2. Focus on Outcomes, Not Outputs
Prioritize customer value, quality, and team health over raw throughput. Ask: Are we building the right thing? Are we improving?
3. Educate Stakeholders
Train managers, clients, and teams on what metrics can and cannot tell you. Demystify story points and velocity—make it clear they are metrics for the team, not universal currencies. Remind managers that story points originated from “ideal” days and should not be used as an obfuscation of time/cost estimation.
4. Guard Against Comparisons
Avoid comparing teams by their story points or velocity. Every team’s calibration is unique. Recognize and respect those differences.
5. Encourage Transparency
Promote psychological safety so teams can be honest about their estimates, blockers, and progress—without fear of punishment for “low” numbers.



The bottom line
Goodhart’s Law offers a cautionary tale for all organizations seeking to improve through measurement. In Agile delivery, turning metrics like story points and velocity into targets invites gaming and undermines the very insights those measures were meant to provide. To avoid falling into this trap, leaders must foster a culture where metrics are used for learning, not judgment, and where the ultimate focus remains on customer value, sustainable pace, and team trust.



Question for Readers:
Have you witnessed or experienced the effects of Goodhart’s Law in Agile delivery—such as point inflation or metric gaming—in your own teams or organizations? How did it impact trust, planning, or outcomes? Share your stories and insights in the comments below.

Posted on: June 15, 2026 01:05 AM | Permalink | Comments (1)

Aligning Agile Practices with the PMI Code of Ethics: Intersecting Responsibility, Respect, Fairness, and Honesty with the Agile Manifesto

linkedin twitter facebook Request to reuse this  
Introduction
After the publication of the Manifesto for Agile Software Development in 2001 Agile frameworks have transformed how teams deliver value, fostering collaboration, adaptability, and customer-centricity. The Project Management Institute (PMI) Code of Ethics and Professional Conduct provide a global benchmark for project teams for ethical behaviour, built on the pillars of Responsibility, Respect, Fairness, and Honesty. Aligning Agile practices with these pillars not only strengthens ethical delivery but also ensures that Agile values are more than just aspirations—they become lived realities. This blog post explores the overlap between the PMI Code of Ethics and the values of the Agile Manifesto, examining how each pillar interconnects with Agile principles, and offers actionable insights for cultivating ethical, high-performing Agile teams.



The PMI Code of Ethics: The Four Pillars
The PMI Code of Ethics and Professional Conduct set out four foundational pillars for all project professionals:

  1. Responsibility: Accepting accountability for decisions and actions.
  2. Respect: Honouring people, their rights, and their dignity.
  3. Fairness: Making decisions impartially and objectively, free from favouritism or discrimination.
  4. Honesty: Being truthful in all communications and actions.
These pillars are not just guidelines—they are imperatives for building trust and fostering sustainable success.



The Agile Manifesto: Core Values and Principles
The Agile Manifesto, published in 2001, emphasizes:

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan
Supporting these values are twelve principles that prioritize transparency, continuous improvement, and delivering value to customers.



Overlapping Ethics and Agile: Pillar by Pillar
1. Responsibility
PMI: “We make decisions and take actions based on the best interests of society, public safety, and the environment.”
Agile Alignment:

  • Agile teams take collective ownership of outcomes and commitments.
  • Scrum and Kanban ceremonies (e.g., retrospectives) foster accountability and learning from mistakes.
  • Prioritizing customer value aligns with the responsible delivery of what matters most.
Actionable Insight: Empower teams to self-organize and hold each other accountable through transparent backlogs, clear goals, and regular reviews.
2. Respect
PMI: “We respect the rights, dignity, and worth of all people.”
Agile Alignment:
  • Agile favours face-to-face communication and values every team member’s contribution.
  • Feedback loops (standups, reviews, retrospectives) encourage listening and constructive dialogue.
  • Psychological safety is essential for raising risks and sharing ideas.
Actionable Insight: Foster an environment where all voices are heard, dissent is valued, and collaboration is prioritized over hierarchy.
3. Fairness
PMI: “We make decisions impartially and objectively.”
Agile Alignment:
  • Agile estimation and planning (e.g., Planning Poker) rely on consensus, reducing bias.
  • Transparent workflows and clear definitions of done reduce favouritism and ambiguity.
  • Work is prioritized based on customer value, not politics or personal agendas.
Actionable Insight: Use objective, transparent criteria for prioritization and role assignments, and rotate responsibilities to ensure equity.
4. Honesty
PMI: “We are truthful in our communications and conduct.”
Agile Alignment:
  • Agile teams surface impediments, estimation errors, and risks as soon as they are known.
  • Velocity, burndown charts, and sprint reviews provide visible, honest progress reports.
  • Agile’s emphasis on transparency ensures stakeholders are never misled by false optimism.
Actionable Insight: Encourage radical candour—reward teams for surfacing bad news early and ensure that metrics and status updates are always grounded in reality.



Benefits of Ethical Alignment

  • Trust and Credibility: Teams and stakeholders can rely on information and commitments.
  • Team Cohesion: Psychological safety and mutual respect drive engagement and retention.
  • Resilience: Ethical teams respond to setbacks with learning, not blame.
  • Value Delivery: Honest, fair, and responsible teams consistently deliver what matters most to customers.



Practical Steps for Leaders

  1. Explicitly Connect Values: Make the link between PMI ethics and Agile principles visible in training, onboarding, and team charters.
  2. Model Ethical Behaviour: Leaders should embody both sets of values in decision-making and interactions.
  3. Create Ethical Feedback Loops: Use retrospectives to reflect on not just delivery, but also ethical dilemmas and how they were handled.
  4. Review Metrics and Rewards: Align KPIs and recognition with ethical behaviour, not just output.



The bottom line
Aligning Agile practices with the PMI Code of Ethics is not just possible—it’s powerful. The pillars of Responsibility, Respect, Fairness, and Honesty are deeply embedded in the Agile Manifesto’s values and principles. By making these connections explicit and actionable, organizations build teams that are not only adaptive and high-performing, but also trustworthy and principled.



Question for Readers:
How do you see the pillars of Responsibility, Respect, Fairness, and Honesty reflected (or lacking) in your Agile teams? What challenges or successes have you experienced in aligning ethics with Agile values? Share your insights in the comments below.

Posted on: June 14, 2026 07:36 PM | Permalink | Comments (1)

Fabricating Estimates Under Executive Pressure: Navigating the Ethics of Adjusting to Fit the Budget

Categories: Agile, Ethics, Estimating

linkedin twitter facebook Request to reuse this  



Introduction
In the world of project management and software delivery, estimates are more than just numbers—they are perceived as commitments, foundations for trust, and often the basis for critical business decisions. Yet, anyone who has worked in an organization with aggressive growth targets or ambitious transformation agendas knows the following scenario all too well: leadership arrives with a predefined budget or timeline, and suddenly, the estimation process becomes less about honest forecasting and more about making the numbers fit. This blog post explores the ethical dilemma of "adjusting" estimation models under executive pressure, the consequences for teams and organizations, and how to handle these situations with integrity.



The Anatomy of Estimation
Estimation, whether in hours, story points, or financial terms, is fundamentally an exercise in professional judgment. Its purpose is to inform planning, resource allocation, and risk management. Good estimates:

  • Reflect reality as closely as possible
  • Are based on historical data and experience
  • Include assumptions and uncertainty
However, estimates are always probabilistic, not guarantees. Responsible estimation requires both rigor and humility.



Executive Pressure: When Numbers Become Political
The Scenario
A new strategic initiative is announced. Executives declare, “We have $500,000 and three months to deliver this project.” The team’s initial estimates, based on sound engineering judgment, suggest the work will take six months and $1 million. Leadership asks for the numbers to be “revisited.” The message is clear: adjust the model until it fits the budget, or the project won’t get approved.
Why Does This Happen?

  • Budget-Driven Planning: Organizations often set budgets based on business needs, not technical reality.
  • Optimism Bias: Leaders may believe teams can "do more with less" if sufficiently motivated.
  • Political Incentives: Middle managers may fear pushback or lost opportunities if they surface the real risks.
  • Short-Term Wins: There is pressure to show quick ROI or meet shareholder expectations.



The Ethical Dilemma
The Temptation to “Adjust”
“Adjusting” estimation models under pressure can take many forms:

  • Redefining scope without clear communication
  • Compressing schedules and quietly assuming overtime
  • Reclassifying work to less visible categories
  • Omitting risk factors or historical overruns
These actions may appease leadership in the short term but come at a cost.
Why Is This Unethical?
  • Erosion of Trust: Stakeholders make decisions based on unreliable data. When reality catches up, blame—and mistrust—follow.
  • Moral Distress: Team members and managers caught in the middle suffer stress, disengagement, and a sense of complicity.
  • Downstream Harm: Projects fail, quality suffers, and customer value is compromised.
  • Violation of Professional Codes: Most engineering and project management codes of ethics mandate honesty, transparency, and duty to report risks.



Real-World Consequences

  • Project Failure: The most common result of fabricated estimates is missed deadlines, cost overruns, and failed deliveries.
  • Team Burnout: Unrealistic expectations lead to excessive overtime, low morale, and attrition.
  • Blame and Cover-Ups: When the truth surfaces, the focus shifts to blame rather than learning.
  • Reputational Damage: Organizations with a pattern of "magical thinking" lose credibility with clients, investors, and employees.



Navigating the Pressure: Acting with Integrity

  1. Document Assumptions: Be explicit about what is and isn’t included in the estimate. Make risks and uncertainties visible.
  2. Communicate Early and Often: Don’t wait until the project is in crisis to reveal the gap between estimates and budgets. Share concerns with leadership as early as possible.
  3. Offer Alternatives: Instead of simply adjusting numbers, propose options: “With this budget, we can deliver X features by this date. For full scope, we need Y.”
  4. Use Ranges and confidence levels: Instead of $500,000 use between 400,000 and 600,000 and instead of 6 months say between 5 and 8 months. Indicate how confident the team is in the estimations provided.
  5. Stand by Professional Principles: Reference industry codes of ethics and best practices to support your position. This frames honesty as a professional responsibility, not a personal disagreement.
  6. Escalate When Necessary: If ethical concerns are ignored, use formal escalation channels or seek guidance from mentors, professional organizations, or HR.



Building a Culture of Honest Estimation

  • Leadership Accountability: Executives must set the tone by rewarding honesty and realism, not just optimism.
  • Safe Environments: Teams should feel safe surfacing risks and bad news without fear of retribution.
  • Continuous Learning: Treat estimate overruns as learning opportunities, not failures to be punished or hidden.
  • Transparency in Reporting: Regularly review actuals versus estimates and discuss gaps openly.



The bottom line
Fabricating estimates to fit a predefined budget may feel like an expedient solution, but it is a breach of professional ethics with real consequences. The path to sustainable, successful delivery is paved with honesty, transparency, and the courage to speak truth to power. By holding the line on ethical estimation, teams and organizations can build trust, deliver better outcomes, and foster a culture where reality is respected—not adjusted away.



Question for Readers:
Have you been asked to "adjust" estimates to fit a budget or timeline? How did you handle the ethical dilemma, and what impact did it have on your team or organization? Share your stories and insights in the comments below.

Posted on: June 14, 2026 07:27 PM | Permalink | Comments (1)

Risk Management in Agile vs. Traditional Approaches—A Code of Ethics Perspective

linkedin twitter facebook Request to reuse this  
Risk management is critical in every project, but the way risks are identified, assessed, and communicated can differ greatly between Agile and traditional methodologies. When viewed through the lens of the Project Management Institute’s (PMI) Code of Ethics and Professional Conduct, these differences become even more pronounced. Let’s explore the impact of Agile practices on risk management, how a real Agile implementation compares with a traditional approach, and what this means from an ethical standpoint.
Agile Risk Management Practices
  1. Continuous Risk Identification
  2. Risks are surfaced frequently—during daily stand-ups, sprint planning, reviews, and retrospectives. This ongoing dialogue ensures risks are never ignored or sidelined.
  3. Shared Ownership and Collaboration
  4. The Agile philosophy encourages the entire team to participate in risk identification and mitigation, rather than assigning sole responsibility to one individual.
  5. Iterative Response and Adaptation
  6. Risks are addressed incrementally, with strategies evolving each sprint. This enables rapid adaptation to new threats and opportunities.
  7. Transparent Communication
  8. Agile teams foster open discussions about risks, making it easier to escalate concerns and enact mitigation strategies swiftly.
Traditional Risk Management Approach
Although there is no guidance or a prescriptive approach to risk management, traditional project management methodologies follow a similar pattern:
  1. Formalised, Upfront Planning
  2. Risk identification and analysis are largely front-loaded at project initiation, with updates at major milestones.
  3. Centralised Accountability
  4. Typically, a project manager or risk officer owns the risk management plan, with responsibility concentrated rather than shared.
  5. Structured Documentation and Reporting
  6. Risks are logged, classified, and tracked in formal registers. Communication occurs through scheduled reports and review meetings.
  7. Periodic Review
  8. Risk management activities are revisited at defined intervals, which may delay the recognition and response to new risks.
PMI Code of Ethics: A Comparative Lens
The PMI Code of Ethics and Professional Conduct is built on four foundational values: Responsibility, Respect, Fairness, and Honesty. Here’s how these values can play out differently in Agile and traditional risk management:
  • Responsibility: Agile promotes proactive responsibility from all team members. Traditional methods can sometimes lead to ethical lapses if risk management is perceived as a responsibility of the project manager only.
  • Respect: Agile fosters respect for diverse perspectives in risk discussions, while some traditional approaches may limit input because of a hierarchical and conservative organisational structure, potentially missing important viewpoints.
  • Fairness: Agile openness helps ensure that risks affecting all stakeholders are considered, aligning with PMI’s fairness principle. Centralised traditional models may unintentionally sideline minority or less vocal interests.
  • Honesty: Agile promotes a culture of transparency that encourages honest, real-time sharing of issues, while the formality of traditional methods can sometimes create pressure to delay or soften risk disclosures.
Bottom line
Core Agile values are naturally aligned with PMI’s ethical values by emphasising transparency, shared responsibility, and inclusivity. Traditional methods offer structure and control but may introduce ethical challenges related to communication and accountability. By adopting collaborative and ethical risk management techniques, teams can better serve both their projects and their professional obligations.
In principle, a collaborative Agile delivery should manage risk better than a command-and-control approach, but achieving Agile maturity takes time, and very few teams can become self-organised. The challenge of being Agile and effectively managing risk is more obvious when Agile is ‘scaled’ using old practices. Lean, although it may provide cost savings and a faster delivery, requires a standardised process that is contrary to Agile values.
Teams transitioning from traditional to Agile or scaling Agile practices beyond a small team of software developers must keep in mind that Agile is empirical, it embraces and needs change and is more dependent on context than traditional project delivery methods. In my opinion, the concept of ‘best practices’ may not exist in Agile.
Question for Readers:
How does your team ensure that risk management practices align with PMI’s Code of Ethics, and have you observed ethical challenges when shifting between Agile and traditional approaches to risk management?
Posted on: May 22, 2026 02:02 AM | Permalink | Comments (3)
ADVERTISEMENTS

"There is nothing more difficult than talking about music."

- Camille Saint-Saens

ADVERTISEMENT

Sponsors