How to Write Compelling Release Announcements

> Plan your release announcement during development

this little section gives me so much... dread.

on one hand, you have to be able to sell what you do; and on the other hand, if you cannot really quantify reasonable improvement to end user experience, can you really justify spending time on it?

we're basically back to figuring out how to allocate for "maintenace" that does not really translate to good "user story".

Thanks for reading!

Yeah, this is something I struggled with as well. It didn't prevent me from allocating time to maintenance, but it meant I had to plan it more carefully. If I had a maintenance-heavy release, I made sure that we were including some "delighter" features even if they were small.