Team:Projectleiding

From MCH2022 wiki
Jump to navigation Jump to search
Projectleiding
  • Establish an exhaustive registration of tasks and responsibilities (i.e. roles)
  • Delegate as many responsibilities as possible to roles/teams
  • Provide information, structure and meetings for people to join orga
  • Ensure healthy financial situation/boundaries
  • Maintain a good view of the large picture (be up-to-date about what happens in teams)
  • Ensure the essential large infrastructure for the event is prepared in time
  • Provide the means to, and make sure the teams are communicating essentials with each other
  • Coach teams that are having difficulties
  • Spot vacancies (non delegated responsibilities) and find people and/or solutions for them
  • Kick-start and guide teams with new people so the team embeds in the orga
  • Maintain contacts with major third parties, such as: venue owners/managers, municipality and other governmental departments
1st line contacts: Stitch
Is an exclusive team: Yes
Contact e-mail: stitch@ifcat.org
Responsible for:



Team Members

Boekenwuurm (Christel) wanted to make a booklet for SHA2017 and ended up with a large role within team:Info. She is active with Hackalot in Eindhoven and will always make time to geek out about the physics behind printers, camera's, wearables or colors.

Coco (Maja) has a curious nature and a strong urge to understand this world. She enjoys bringing people together and organizing tech and social events. Currently she works as a software developer for a better future with solid privacy. When not behind a screen, you may find her strolling around in nature. Social contact tip: Gather her attention with food.

Halcyon (Tom) has organised events for over a decade, and started the HackZone hacker field at the yearly 11-day CampZone event in 2015. Sha2017 was his first Dutch hacker camp, and he fell in love with them immediately. He is one of the people behind badge.team: a group that makes electronic badges for a bunch of hacker events. During the day he's a firmware engineer at Ultimaker R&D, and at night he likes to hack on funky electronics. Halcyon is a firm believer in social equality and freedom of information.

Netsmurf (Jeroen) has organized events since HAL and started out there as a general volunteer. Volunteered for the NOC teams of WtH, OHM, EMF, CCC Camp and Congres for the last few times. Joined PL for SHA2017/MCH2021 and now again for MCH2022. His hobbies are diving & paragliding, working with wood and he enjoy organizing awesome events with all the nice volunteers. His day jobs are managing his companies, building/maintaining/troubleshooting large ISP networks and trading in IP addresses. Netsmurf believes in equal rights and opportunities for everyone and paying it forward.

Rizoom (Janneke) got involved with hacker events in 2017 when she met Stitch, who introduced her to the scene. It was love at first sight. At SHA2017 she was lead of the Cohesion team, a position that fits in well with her professional background as a coach and scrum master, and her experience in counseling. Janneke strongly believes in inclusivity and being excellent to each other. In the day time she switches around between technical software testing and social roles in IT teams and in her free time, she loves to pursue creative projects from sewing to tinkering.

Stitch (Elger) believes that hacker culture and knowledge sharing open the doors to a better society. Stitch co-founded Hack42 and Awesome Space, was on the projectleiding for SHA2017 and has been (contributing) to countless hacker/nerd events and organized retro gaming booths on dozens of huge festivals entertaining the many. Stitch works for a safer internet: many thousands of vulnerabilities fixed and counting. Stitch is an independent security tester and software developer for projects with a positive impact on society.


Vacancies

Currently no vacancies.


Meetings

We meet every Wednesday on the MCH jitsi.


Team status list

Todo: update this list. This is outdated and taken from MCH2021.

This overview gives an insight on the health of teams. Also see Vacancies.

Meaning of the fields:


This team is required for the event:
Meaning: without the deliverables of this team the event can not continue. For example: team:power is a requirement for lectures, recording, sanitation and so on. Counter example: a badge is a great add on to the event, but even if it fails, the event can continue safely. Crucial teams contribute to safety, essential services, hygiene, health.


Status: Team has contact information:
Meaning: a new volunteer or the existing network of volunteers can easily contact this team and ask questions or status information.


Status: Team has informative wiki page:
Meaning: the wiki page of the team details a bit of their plans, how they do it and what they provide to others. It contains who the team members are. This is a treasure trove for next events, as well as a way to streamline information to other teams.


Status: Team has meetings are planned until the event:
Meaning: the team is in control and regular meetings / gatherings to check progress, todo's, questions and whatever is relevant to the team. Meetings do not always need to be formal or documented in order to set this checkmark of course.


Status: Team has enough orga-volunteers to function:
Meaning: there are enough dedicated people on the team that everyone on the team can enjoy at least two days at the camp without doing anything for this team. The stress level is relatively low because work is shared among team members. Angels are excluded in this metric: note that angels often need training, which also takes time which must be allocated. Examples of what this being unchecked can mean: people are not exclusive to this team and thus cannot guarantee time before and during the event, there are tons of plans but no actual work is planned, performed or managed, people are out of reach, there is no backup for crucial team roles, there is no time allocated to instruct and guide angels. There is no tracking of progress.


Status: Team has drafted a budget:
Meaning: there is a table of expected expenses and projected income. This consists of listing of items, with their price. This does not need to be public, but team:finance must know. If there is no budget, the finance team / board will try to determine one: better to be in control yourself, so allocate, estimate and write it down.


Status: Team has informed team:volunteers:
Meaning: if there are any angel requirements, or orga-volunteers needed, team:volunteers is aware of their numbers and needed capabilities. Yes you can search yourself, and you can also get more searching capacity if these numbers and skills are shared.



Team Contactperson Team is essential to event Team has contact info Team has info on wiki Team has planned meetings Team has enough people Team has drafted budget Team has informed volunteer team
Team:Info Boekenwuurm Important
Team:Huisstijl Boekenwuurm Flavour 〰️
Team:Promo Boekenwuurm Important
Team:Villages Boekenwuurm Substance
Team:Press Boekenwuurm Substance
Team:Volunteers Boekenwuurm Important
Team:Family Boekenwuurm Substance
Team:Speaker Desk Coco Substance 〰️
Team:Ticket & Entrance Coco Show-stopper 〰️
Team:Heralds Coco Substance 〰️
Team:Finance Coco Show-stopper
Team:ROC Halcyon New and improved
Team:Badge Halcyon New and improved
Team:Sponsors Halcyon Important 〰️
Team:Safe Harbour Netsmurf New and improved
Team:Security Netsmurf Show-stopper 〰️
Team:ColourMyMCH Netsmurf New and improved
Team:Moebelhaus Netsmurf New and improved
Team:Fire Netsmurf Show-stopper
Team:First-AID Netsmurf Show-stopper 〰️ 〰️ 〰️
Team:Partytent Netsmurf Substance 〰️
Team:NOC Netsmurf Important 〰️ 〰️ 〰️
Team:Lighting Netsmurf New and improved
Team:Horeca Netsmurf Important
Team:Clothing production Netsmurf Substance 〰️ 〰️
Team:Deco Rizoom Flavour
Team:Cohesion Rizoom New and improved
Team:Music Rizoom Flavour
Team:Content Rizoom Substance
Team:Productiehuis Stitch Substance
Team:Terrain Stitch Show-stopper
Team:Off-site transportation Stitch Important
Team:Shuttle Stitch Flavour
Team:POC Stitch Important
Team:Sysadmin Stitch Important
Team:Permits Stitch Show-stopper 〰️ 〰️ 〰️ 〰️
Team:POC/Fieldphone Stitch New and improved
Team:Board Stitch New and improved
Team:Accessibility Stitch New and improved 〰️
Team:On-site transportation Stitch Important
Team:Power Stitch Important
Team:Warehouse Stitch Important


Roles

  • Kick-start van teams (?)
  • Establish an exhaustive registration of tasks and responsibilities (i.e. these lists!)
  • Delegate as many responsibilities as possible to roles/teams
  • Provide information, structure and meetings for people to join orga
  • Ensure healthy financial situation/boundaries
  • Maintain a good view of the large picture (be up-to-date about what happens in teams)
  • Ensure the essential large infrastructure for the event is prepared in time
  • Provide the means to, and make sure the teams are communicating essentials with each other
  • Coach teams that are having difficulties
  • Spot vacancies (non delegated responsibilities) and find people and/or solutions for them
  • Maintain contacts with major third parties, such as:
  1. venue owners/managers
  2. municipality and other governmental departments


How do the clusters look like

A visual overview of the orga organigram
Cluster organigram