Devs hiring for CYF Products

[kfklein15]

Background We have some great graduates that volunteer for CYF Products for a while but still haven't got jobs. CYF Products needs developers to be able to support and get our products developed faster However we want to ensure we do not chose people giving preferences

Things to consider

• Have a fair application/selection process that is open to the community
• Prioritise the product that needs to be developed on and most important for the organisation
• Create the smallest feature that we can create (to last no more than 1-3 months to launch)

[kfklein15]

@gbencci I created a separate ticket to track this discussion since I don't think this is only of the change board. I think our needs are far greater on the existent products.

Some of my thoughts are below:

• Can we have some rules for applicants, such as: being a graduate AND having volunteered for CYF Product for 3 months? > No, because this would class as possible employment issues
• I think our highest priority is development in Dashboard and Rainbird, not the tickets on the Change board. But maybe it isn't? I am thinking of value for the organisation.
• How do we support these people? Do we need a part-time tech lead hired?

[gbencci]

Hi Karen, I've thought about this while you were away. My thoughts:

• Our approach should be evidence-based. Three requirements: (a) Technical & PD Skills => test (b) Discipline, reliability, motivation => volunteering (c) Personal, Financial Needs => form/interview

The combination of these gives us the right answer for who we should offer an opportunity, either as Fellowship (bursary) or Contract (paid project).

In terms of support, I know it's been a challenge, but we should hope that in our community full of devs we can have TLs to work on it. We could get some mentorship if we can pull off paid projects like AI, but paying for TLs should be last resource

[kfklein15]

Description of what we need, which is what I would post online. But I think this is huge for 3 months of work of two grads tbh. What are the must have here? Where is the highest benefit? @gbencci

Manage volunteers actively

• Objective: reduce timeline between volunteers signing-up and being active in the community
• Dates: contract last from 1st May till 31st Jul 2023
• Background: we have an existing volunteer form, but we need to change the data that is being collected, update the layout and enhance the Dashboard functionalities to manage volunteers
• Mandatory requirements:
  • Add volunteer data that should be provided (i.e. which team they want to volunteer form)
  • Remove volunteer data that isn't needed (i.e. why do you want to volunteer)
  • Dashboard filtering (i.e. per team)
  • Add external data to Dashboard (i.e. community safety training and quiz done, volunteer agreement sent/signed)
  • Dashboard view of actions (i.e show new volunteers, volunteers not signed agreement)
• Submission: developers must have proven experience of at least 3 months with MERN tech stack. Send your CV to Karen.

[kfklein15]

@gbencci , if you can take a look at my last comment that would be great. Thank you.

[gbencci]

Hi Karen, I'd love to see this in the context of any other possible jobs that we could do. I don't think we have to worry about releasing a single product as part of the funding, but a collection of valuable things. I'll help you on the report. A Miro board with a list of small releases that we decide between a small group of people.

[kfklein15]

@gbencci, these are the main things we need. We can do a Miro exercise again, but we know what is required, we just need to deliver it according to our priorities.

• Dashboard Roadmap/requests
• Rainbird (fix it and make some updates)

Not prioritised

• Class Planner (not sure it is high priority yet and team is still learning)
• CYF Next (not sure if we have value on it yet)

[gbencci]

That's great Karen. Use the money for the things that are most important to the organisation. We'll write a report afterwards with what we did

[kfklein15]

Closing this since it will be part of the #122 , which is the one budget we have.