From 48ee6c2faf5e1b10cdec9f1f93f19095ec920c50 Mon Sep 17 00:00:00 2001 From: Kelly Lee <36768505+kellylee-gds@users.noreply.github.com> Date: Tue, 10 Dec 2024 10:02:30 +0000 Subject: [PATCH 1/5] Create guide for planning an event --- ...lanning-an-event-workshop-or-meetuphtml.md | 115 ++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 source/community/blueprint-for-planning-an-event-workshop-or-meetuphtml.md diff --git a/source/community/blueprint-for-planning-an-event-workshop-or-meetuphtml.md b/source/community/blueprint-for-planning-an-event-workshop-or-meetuphtml.md new file mode 100644 index 0000000..3dd5927 --- /dev/null +++ b/source/community/blueprint-for-planning-an-event-workshop-or-meetuphtml.md @@ -0,0 +1,115 @@ +--- +title: Blueprint for planning an event, workshop or meetup +weight: 5 +--- + +# Blueprint for planning an event, workshop or meetup + +This blueprint uses the MoSCoW prioritisation system: + +- Must +- Should +- Could + +## Must + +The things we must do, and should be completed first. + +### Decide the format of the event and design the agenda + +Done when: + +- Agreed the objective of the event +- Decided whether it is online, in–person or hybrid +- Decided the running time of the event, and the frequency of breaks +- Agreed the most appropriate format of the event to achieve the objective +- Agreed participant numbers +- Decisions have been documented and shared with the wider team + +### Secure somewhere to host the event + +Done when: + +- Decided whether the event can be hosted in a GDS office or an external venue is required +- Investigated venue options and choose a venue which meets the event’s needs +- Booked the venue or room(s) +- Decisions have been documented and shared with the wider team + +### Agree a date for the event + +Done when: + +- Selected an appropriate date +- Decisions have been documented and shared with the wider team + +### Estimate the budget for the event + +Done when: + +- Estimated all costed aspects of the event +- Submitted budget for approval +- Monitored the budget throughout the event planning +- Decisions have been documented and shared with the wider team + +### Decide what volunteers are required for the event and recruit into roles + +Done when: + +- Decided how the event will be facilitated and identified roles +- Recruited into roles identified +- Prepared volunteers for their roles +- Decisions have been documented and shared with the wider team + +### Create a ticketing policy + +Done when: + +- Agreed how the event will be ticketed +- Ticketing platform has been set up +- Decisions have been documented and shared with the wider team + +### Create a communications plan for the event + +Done when: + +- Agreed which communications should be released and when, and by whom +- Achieved sign off from GDS Comms +- Decisions have been documented and shared with the wider team + +### Create a process for handling support queries + +Done when: + +- Agreed a process for handling support queries about the event and identified roles +- Decisions have been documented and shared with the wider team + +### Procure any suppliers required + +Done when: + +- Investigate what can be sourced by GDS and what needs to be sourced externally +- Retrieved quotes and chosen a supplier +- Prepared the supplier for the event +- Paid invoices + +### Recruit and prepare speakers + +Done when: + +- Recruited appropriate speakers as per objective of the event +- Retrieved quotes from speakers +- Prepared speakers for the event +- Paid invoices (if required) + +## Should + +The things we should do, but only when the ‘musts’ have been completed. + +- Create merchandise + +## Could + +The things we could do, but should be less of a priority than the ‘shoulds’. + +- Plan an after-event social +- Change branding From 408a8e17620615b55504f1815f84eccde445b4a0 Mon Sep 17 00:00:00 2001 From: Kelly Lee <36768505+kellylee-gds@users.noreply.github.com> Date: Tue, 10 Dec 2024 10:31:34 +0000 Subject: [PATCH 2/5] Fix file path typo --- ...=> blueprint-for-planning-an-event-workshop-or-meetup.html.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename source/community/{blueprint-for-planning-an-event-workshop-or-meetuphtml.md => blueprint-for-planning-an-event-workshop-or-meetup.html.md} (100%) diff --git a/source/community/blueprint-for-planning-an-event-workshop-or-meetuphtml.md b/source/community/blueprint-for-planning-an-event-workshop-or-meetup.html.md similarity index 100% rename from source/community/blueprint-for-planning-an-event-workshop-or-meetuphtml.md rename to source/community/blueprint-for-planning-an-event-workshop-or-meetup.html.md From 364adf0f987d8b6b9b7cb7faf40d92f15ffcbf20 Mon Sep 17 00:00:00 2001 From: Kelly Lee <36768505+kellylee-gds@users.noreply.github.com> Date: Tue, 10 Dec 2024 10:47:46 +0000 Subject: [PATCH 3/5] Add content about why MoSCoW system is being used --- ...ueprint-for-planning-an-event-workshop-or-meetup.html.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/source/community/blueprint-for-planning-an-event-workshop-or-meetup.html.md b/source/community/blueprint-for-planning-an-event-workshop-or-meetup.html.md index 3dd5927..5323060 100644 --- a/source/community/blueprint-for-planning-an-event-workshop-or-meetup.html.md +++ b/source/community/blueprint-for-planning-an-event-workshop-or-meetup.html.md @@ -5,11 +5,7 @@ weight: 5 # Blueprint for planning an event, workshop or meetup -This blueprint uses the MoSCoW prioritisation system: - -- Must -- Should -- Could +This blueprint uses the MoSCoW prioritisation system (must, should, could) to help prioritise planning activities. ## Must From aa27a5c3d4561c6615c516a05d7f09eb8bdc72ca Mon Sep 17 00:00:00 2001 From: Kelly Lee <36768505+kellylee-gds@users.noreply.github.com> Date: Tue, 10 Dec 2024 10:50:12 +0000 Subject: [PATCH 4/5] Add to index --- source/community/index.html.md.erb | 1 + 1 file changed, 1 insertion(+) diff --git a/source/community/index.html.md.erb b/source/community/index.html.md.erb index 5255021..9879311 100644 --- a/source/community/index.html.md.erb +++ b/source/community/index.html.md.erb @@ -6,5 +6,6 @@ weight: 10 # Community - [A guide to the Design System monthly chat](./a-guide-to-the-design-system-monthly-chat/) +- [Blueprint for planning an event, workshop or meetup](./blueprint-for-planning-an-event-workshop-or-event/) - [Code of conduct for workshops](./code-of-conduct-for-workshops/) - [Community objectives](./community-objectives/) From 228308c9620c8f03098f16a1d5aa4b2a4b3ee945 Mon Sep 17 00:00:00 2001 From: Kelly Lee <36768505+kellylee-gds@users.noreply.github.com> Date: Tue, 10 Dec 2024 10:52:59 +0000 Subject: [PATCH 5/5] Fix typo in index file path to new guide --- source/community/index.html.md.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/community/index.html.md.erb b/source/community/index.html.md.erb index 9879311..03c7417 100644 --- a/source/community/index.html.md.erb +++ b/source/community/index.html.md.erb @@ -6,6 +6,6 @@ weight: 10 # Community - [A guide to the Design System monthly chat](./a-guide-to-the-design-system-monthly-chat/) -- [Blueprint for planning an event, workshop or meetup](./blueprint-for-planning-an-event-workshop-or-event/) +- [Blueprint for planning an event, workshop or meetup](./blueprint-for-planning-an-event-workshop-or-meetup/) - [Code of conduct for workshops](./code-of-conduct-for-workshops/) - [Community objectives](./community-objectives/)