Is there a report type to document a (Agile) project journey?

Question

My main goals are to

1. document our current methodology,
2. share our team's story of changing and adapting, and
3. share evaluations of our improvement.

Ideally, I'd like to share this report with our team so they can see the journey we've been on and learn a thing or two about what we do.

At first, I thought a case study would work. I think this handles the idea behind documenting our strategies, but it doesn't touch on the story of getting to where we are. Another option I saw was a progress report. This does a better job, in my opinion, of documenting our team's story, but it lacks some of the documentation on our methodology.

Is there a report format that organizes this? I've tried writing this on my own, and I can go back to that if need be, but I always feel a pre-determined report type is easier both to write and understand. I'm still pretty new to Agile and PM as a whole, so please let me know if I'm misunderstanding a report type!

Edit based on feedback so far:

I think I'm leaning to write a couple of separate docs rather than one large nightmare. I could document the current methodology as an ongoing document, thinking this would be most useful when adding new team members. A presentation is a really great idea for the story part -- we're a remote team spread across nearly 20 hours of time zones, but it brings up a lot of ideas. This would help me tell the higher up guys where we started, why the project was failing, and why we're here now. The evaluations of improvement I'm referencing are much more concrete/numerical, so maybe that can be expressed in a case study.

The presentation seems to be the way to go, I upvoted that answer and will accept after working through it a little more.

Answer 1

You might be looking for a Project Charter. This kind of documents varies a lot from project to project.

With regards to tools and techniques, I share a part of the linked article.

The Agile community has appropriated a number of different techniques or notations that have proven useful to capture high-level project information. For instance the “rich picture” approach of SSM (Soft Systems); the “context diagram” from structured analysis; or Lean manufacturing’s A3 (which derives its name precisely from the paper format).

Answer 2

We conduct risk assessments during our projects. The resulting risk register enables us to share evaluations of our improvement and tells our team's story of changing and adapting.

Answer 3

document our current methodology

How quickly will this become out of date? Will the document be continually updated? Will enough people read the document to ensure its value? Agile teams tend to shy away from documentation unless they are sure of their value.

share our team's story of changing and adapting

One of the Agile values is Individuals and interactions over processes and tools. This means we favour talking to each other. Perhaps a presentation would be a good format to achieve the sharing of the team's story?

share evaluations of our improvement

Rather than doing this as a one-off, why not ask the team if they mind regularly sharing their retrospective output? For example, you could have an area of wall space allocated to act as an information radiator for adaptions the team has made.