Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 3 additions & 8 deletions common-content/en/module/launch/launch-prep/team/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,15 +19,10 @@ This exercise will explain your team formation and give tips on what you should
Your team will have:

- 2-4 Developers: these will be other trainees you might know.
- 1 [Tech Lead](https://docs.codeyourfuture.io/volunteers/teams-1/cyf-products-final-projects/roles/tech-lead-1): a volunteer who will support your team with the architecture and design of your product
- 1 [Product Manager](https://docs.codeyourfuture.io/volunteers/teams-1/cyf-products-final-projects/roles/product-owner-cyf-product-or-product-manager-final-projects-1): a volunteer who will work with you to detail the scope and define the user stories
- 1 [Tech Consultant](/launch/volunteer-roles/tech-consultant/): a volunteer who will support your team with the architecture and design of your product
- 1 [Product Manager](/launch/volunteer-roles/product-manager/): a volunteer who will work with you to detail the scope and define the user stories

You might also have the following members if a trainee focuses on this career.

- QA (Tester)
- [UI/UX Designer](https://docs.codeyourfuture.io/volunteers/teams-1/cyf-products-final-projects/roles/ui-ux-designer)

You might have a [Business Owner](https://docs.codeyourfuture.io/volunteers/teams-1/cyf-products-final-projects/roles/business-owner-final-projects) representing the charity or organisation you are doing this briefing for. They will give your team insight into the users' needs and the value the product will deliver.
You might have a [Business Owner](https://curriculum.codeyourfuture.io/launch/volunteer-roles/business-owner/) representing the charity or organisation you are doing this briefing for. They will give your team insight into the users' needs and the value the product will deliver.

## What do you need to do?

Expand Down
Comment thread
illicitonion marked this conversation as resolved.
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ Jane has recently completed the part time Super Coders Software Development prog

Jane is very passionate about programming. She taught herself the Python programming language before starting the course.

Her portfolio includes many full stack applications. This includes projects she has built with other students, as well as some solo projects. She’s especially proud of a project called Pin the Mood. This project stores book recommendations until the user has time to read the books. The project used React, Express, Node.js and PostgresSQL. The project team was an agile team made up of two trainees, a scrum master and a tech lead.
Her portfolio includes many full stack applications. This includes projects she has built with other students, as well as some solo projects. She’s especially proud of a project called Pin the Mood. This project stores book recommendations until the user has time to read the books. The project used React, Express, Node.js and PostgresSQL. The project team was an agile team made up of two trainees, a product manager and a tech consultant.

After leaving school seven years ago, she joined Lawyers 4U as a call handler. She has developed excellent interpersonal skills and has gained experience working under pressure.

Expand Down
2 changes: 1 addition & 1 deletion org-cyf/content/launch/overview/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,6 @@ title = "Course overview"

The Launch is an opportunity to work in a group on a real greenfield project which will have real users when complete.

Across four sprints, trainees will work with an advisory tech lead and product manager to build an MVP, from scratch. The goal is to consolidate all of the knowledge build up across the CYF courses and apply them in a real-world setting. At the end of The Launch, trainees should have an impressive product to show off, and real experience to discuss in interviews.
Across four sprints, trainees will work with an advisory tech consultant and product manager to build an MVP, from scratch. The goal is to consolidate all of the knowledge build up across the CYF courses and apply them in a real-world setting. At the end of The Launch, trainees should have an impressive product to show off, and real experience to discuss in interviews.

The be eligible to participate in The Launch, a trainee must have completed the [Software Development Course](/sdc/). Upon successful completion of The Launch, CYF considers trainees ready to apply for jobs in software.
19 changes: 9 additions & 10 deletions org-cyf/content/launch/volunteer-roles/feedback/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ This is not an exhaustive list. If you observe anything (good or bad) which you

The frequency of feedback is just as important as what it contains. If a trainee doesn't get feedback early in the project then their work won't improve.

You should aim to give every trainee some feedback every week. It doesn't have to be exhaustive, but any issues need to be highlighted early. It's just as important to celebrate success and let trainees know they're doing a good job.
You should aim to give every trainee some feedback every week. It doesn't have to be exhaustive, but any issues need to be highlighted early. It's just as important to celebrate success and let trainees know they're doing a good job.

Each trainee will receive a summary of their feedback at the end of the Launch (see "Assessment Criteria" below). Nothing in this document should come as a surprise to them, and it won't if they are getting regular feedback from their mentors.

Expand All @@ -49,16 +49,16 @@ Each trainee will receive a summary of their feedback at the end of the Launch (
At the end of the module we ask all volunteers to write an assessment of each trainee in their group. This should be done as a team and include feedback from each volunteer. The assessment should include three things:

1. An overall recommendation for the trainee's next steps. This should be one of the following options:
- **A** - The trainee is ready for employment. Someone in this category has been an effective team member and has shown strong technical aptitude.
- **B** - The trainee is nearly ready for employment but would benefit from an additional project with the CYF Tech Products team. A trainee in this category may need further exposure to a professional group dynamic or experience working with an unfamiliar tech stack.
- **C** - The trainee is not ready for employment and needs to work on further projects with the CYF Tech Products team. A trainee in this category has demonstrated some technical aptitude but found the group environment challenging. They need time to practice working in a team before applying for jobs.
- **D** - The trainee is not ready for group work. They have not demonstrated a sufficient level of technical understanding and need to develop their coding skills before joining another team.

- **A** - The trainee is ready for employment. Someone in this category has been an effective team member and has shown strong technical aptitude.
- **B** - The trainee is nearly ready for employment but would benefit from an additional project with the CYF Tech Products team. A trainee in this category may need further exposure to a professional group dynamic or experience working with an unfamiliar tech stack.
- **C** - The trainee is not ready for employment and needs to work on further projects with the CYF Tech Products team. A trainee in this category has demonstrated some technical aptitude but found the group environment challenging. They need time to practice working in a team before applying for jobs.
- **D** - The trainee is not ready for group work. They have not demonstrated a sufficient level of technical understanding and need to develop their coding skills before joining another team.

2. An explanation of the recommendation. This should highlight the trainee's strengths and any areas for improvement. It should cover two categories:

- Technical skills
- Soft skills
- Technical skills
- Soft skills

3. The assessors' names and roles in the team

Expand All @@ -72,5 +72,4 @@ At the end of the module we ask all volunteers to write an assessment of each tr

**Soft Skills**: Pedrita displayed initiative by suggesting improvements whenever she identified opportunities. Namely, she did a very good job improving the look-and-feel of our front-end. She occasionally missed team responsibilities, such as writing standup notes, or communicating with the team about problems attending meetings. She needs to enhance her attention to detail, as I often had to repeat instructions multiple times, particularly during code reviews.

**Assessors**: Karen Klein (Product Manager), Colin Farquhar (Tech Lead)

**Assessors**: Karen Klein (Product Manager), Colin Farquhar (Tech Consultant)
Original file line number Diff line number Diff line change
Expand Up @@ -23,4 +23,4 @@ You can see [The Launch schedule and content](/) to get familiar with what will
* Incentivising the team to be self-organised and accountable.
* Working with the team members on any conflicts.
* Giving the trainees honest and constructive feedback: if you wouldn't hire them, tell them why so they can work on it.
* Write an assessment of every trainee in your team. This must be done with the other volunteers in your team. The assessment criteria can be found on the [feedback page](/volunteer-roles/feedback/).
* Write an assessment of every trainee in your team. This must be done with the other volunteers in your team. The assessment criteria can be found on the [feedback page](/launch/volunteer-roles/feedback/).
48 changes: 48 additions & 0 deletions org-cyf/content/launch/volunteer-roles/tech-consultant/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,48 @@
+++
title = "Tech Consultant"
weight = 2
+++

The Tech Consultant will be part of an Agile Scrum Team supporting the developers on their daily dev work to deliver value to the users and organisation. You are not expected to write any code in this role.

The **time commitment is 2-4 hours per week plus Saturday all day**. It is a 5-week long commitment.

You can see [The Launch schedule and content](/launch) to get familiar with what will be expected.

## Who are you?

- **Developers with at least two years of experience in a mid-level that want to take the next step in their career** or **experienced Tech Lead**.
- Excellent problem-solving skills to break down the delivery and architecture/design of software.

## Your responsibilities

- **Write an assessment of every trainee in your team**. This must be done with the other volunteers in your team. The assessment criteria can be found on the [feedback page](/launch/volunteer-roles/feedback/).
- **Being part of the Product Team motivating team members and creating a space where they can ask questions and voice their concerns.**
- The team own their solutions, and it should be them writing all the code but you are there to support them with suggested approaches when they get stuck.
- **Being transparent with the team about challenges, failures, and successes.**
- Giving the trainees honest and constructive feedback: if you wouldn't hire them, tell them why so they can work on it.
- Make sure everyone contributes: the team has to contribute evenly, which will be measured.
- **Supporting the team to understand the requirements and approving the technical implementation solutions the teams come up with.**
- Help with breaking tasks down into tickets.
- Take teams through the agile workflow: Assigning themselves to tickets, creating PRs, getting reviews, merging and deploying code.
- Participate in code review but, importantly, ensure it is a shared responsibility across the team. Code review is not solely your responsibility, it's the job of the team too.
- **Oversee and define the architecture of the application.**
- Help the team avoid getting stuck when building the solutions. They are juniors, and your experience will help them clarify how things should fit together, especially when integrating 3rd party APIs or setting up authentication.
- Identifying risks that could jeopardise delivery.
- **Support the team as a consultant**
Comment thread
Poonam-raj marked this conversation as resolved.
- You should not be writing or committing code, but you can pair or mob with the students on tasks where they've got stuck to help unblock them.
- Incentivising the team to pair programme.
- Help teams with merge conflicts.
- Encourage teams to help each other as much as possible.
- Actively participating in the Agile/Scrum ceremonies.
- **Ensuring the team is developing using software development best practices.** We are flexible around technology choices, but our trainees tend to know and use:
- Front End Experience: JavaScript, HTML, CSS.
- Back End Experience: NodeJS, Python.
- Databases: Some exposure to PostgreSQL, but little schema design experience.
- Version Control: Git, GitHub.
- Deployment Platforms: Netlify, Coolify.
- RESTful Services & APIs.
- **Ensure the application is ready for production deployment**. Your team will have limited experience of a deployment workflow without many of the steps typically involved in an industry setting.
- Support the team in their research of CYF's production stack.
- We don't expect applications to be fully ready for production-grade deployment at the end of the project, but they should be deployed, and should be designed with production-grade deployment in mind and any remaining steps should be clearly documented.
- A production-ready MVP is the preferred outcome compared to a feature-complete application which would need changes before deployment.
47 changes: 0 additions & 47 deletions org-cyf/content/launch/volunteer-roles/tech-lead/index.md

This file was deleted.

Loading