Listeners and plugins are a central component of Quartz.Net and here is why:

• Applications can catch scheduling events to monitor or control job/trigger behavior by implementing one or more listener interfaces
• The plugin mechanism can be used to add functionality to Quartz, such as keeping a history of job executions, or loading job and trigger definitions from a file
• Quartz ships with several factory built plugins and listeners

As you can see, there are many positive benefits to using Quartz, but one that I forgot to mention is stability. The best scheduler is kind of like the best logging tool: the best one is the one that you never realize is working. That sums up Quartz.NET perfectly; it just keeps on ticking.