Page Comparison

...

Retrospectives are for everyone, not just the team lead! Please consider prompts as a group but also individually
Note which members of your rosters are leaving and be sure and invite them to participate in the Retrospective and record any insights they may have, especially the memory of why the subteam works the way it does.
- See screenshots below for how to determine this information
Document ideas/potential plans for next term – even if a lot of the same people are still returning, you may have forgotten the intention or why you thought it was a good idea
Document pain points so that they can potentially be addressed next year (e.g., meetings were hard to facilitate without a note taker, so next year we want to designate one)
Take some time (individually, as a group) to identify what worked well, and make a plan to keep doing those things. Consider too what didn’t work well, or what doesn’t need to be done anymore (make sure to document why).
Are there any completed tasks/projects that will require maintenance by next term’s subteam? Document what needs to happen, how often it needs to happen, who should do it, and what that person needs to know in order to do it.
Do not stress if you didn’t finish tasks, but ask how you can set achievable goals? Consider making your goals smaller or increment them from term to term
Check in with your Vice Lead and subteam generally and ask: Are there things you don’t understand that we were doing? What you believe is obvious may not be and may require documentation.
Remember to distinguish between ongoing tasks (things that will always be true) and new projects. Both should be assessed.
Remember that leadership has been around for awhile, but every team has new members. Explore motivations anew.
Where to find contextual information you may wish to refer to during this time, according to the ArchivesSpace Councils Wiki Organization

...

Versions Compared

Old Version 6

New Version Current

Key