Who should write the changelog of a task? Developer or tester?

Question

I work at a software company that maintains some products.

We use a "bugtracker" to manage all tasks related to the products in question.

We work with Scrum, and the company's routine is basically the following:

1. The customer comes in contact with the support and requests to solving a problem or implementing a feature.
2. The owners of the product group the tasks in order of priority and directs them to a Sprint.
3. Developers finalize the task and ultimately are required to fill out a kind of "changelog".
4. The testers ensure that the coding of the developers was done correctly and end the call.

Here is my problem:

Developers do not like to fill the "changelog", and usually forget to do it.

Here is my question:

Who should complete the "changelog"? The developers and testers?

This "changelog" is sent to end customers at the end of each Sprint, and basically serve to explain in nontechnical what has been resolved or implemented in software.

And then, who should do it? Developers and testers?

Answer 1

This isn't a Scrum question, it reads like a process question. Can I also state that Scrum doesn't really lend itself well to maintenance work and that you may be better trying Kanban in that situation?

That said, although Scrum does not include any reference to changelog artifacts, I'd say that it's a team responsibility to ensure that the changelog is updated (as opposed to any one developer or tester). To act as a reminder, The team may want to consider adding this requirement in to their 'Definition of Done'.

Hope that helps.