Defining the Correct Roles
I have been chosen to be responsible for rolling out Scrum in my small 5 man software development team. I am also a developer at the same time.
This is an inherent conflict of interest. The Scrum Master role is a core role that is deliberately distinct from being a member of the Team. In my personal experience, agile projects that do not make this distinction often flounder.
Clarifying Goals and Objectives
My boss has just emailed me and said he wants me to fully document the whole Scrum process for him and the team - this is something that doesn't sound needed or useful.
In the spirit of Scrum, you need to clarify the objective. My personal interpretation is that you are being asked to provide the team with some training on the Scrum process and its associated roles. However, you will only discover the true objective of the task by opening a dialog with your boss.
It may be useful (and certainly very agile!) to create a user story for this particular task. For example:
As a functional manager,
I would like a developer to provide some initial Scrum training to the Team
so that we have a starting point for adapting the methodology to our environment.
A user story like this will make the manager's goal clear to the team, and provide some scope to the information that should be conveyed in the training. It may also help explain why the manager feels the training is needed in the first place.
Most important of all, the user story will start a conversation about what Scrum means to both the manager and the team. A two-way dialog is an essential part of Scrum; without that dialog, the team will miss out on the core value proposition of the Scrum process.