🖼️ Refining Tickets Workflow

• 🔥 How important is this task? Prioritise 🤔
• 🐋 How long will this take? Estimate ⚖️
• 📆 Does this task have a deadline? Schedule 📆
• 🗃️ What type of work is this? Sort 📐
• 😶‍🌫️ What would someone else need to know to complete this task? Explain 🎨 (or Ask)

A ticket is fully refined when anyone in your team could pick it up. If you can validate a ticket in the Backlog as Ready, move it to Ready now.

Only tickets In Progress can belong to any particular team member, so don’t claim tickets now.

🎫 Refine some tickets

Read over your team backlog. Validate the tickets against the checklist given above. If there are any tickets that are Ready, promote them from the Backlog.

Now select a ticket from the Backlog to refine. Use the refining tickets workflow. Don’t promote your own ticket to Ready - leave that to a team-mate to validate.

You can do this asynchronously or in a call with your team. Whichever helps you to make progress.

Link to the coursework

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews

Why are we doing this?

You must set aside a part of your development time to review the work of your team. In technical interviews, you may to asked to discuss a feature written by someone else in your team, so you will need to read and understand it.

How to review

• Use the GitHub PR interface, either on GitHub or via VSCode
• Checkout the PR locally gh pr checkout 123 and run the code to make sure it works
• Test the code using the acceptance criteria on the ticket
• Ask clarifying questions to make sure you understand the code
• Offer any fixes or improvements you can see

Maximum time in hours

2

How to get help

Volunteers and other team members can help you with code review. You may choose to spend some time in class doing this together.

How to submit

Submit your review directly on your teammates PR.

Link to the coursework

https://curriculum.codeyourfuture.io/guides/getting-help/asking-questions/

Why are we doing this?

When you hit a blocker, write up your blocker as a technical question. You can write this directly in Slack or on a ticket on your board and then link it in Slack. The process of writing out your blocker is key to resolving it.

Now, write up your mental model using this format:

What I did What I expected What actually happened

How to submit

Post your question in Slack

How to review

Before asking a question check in with yourself and make sure you have done the following:

I have…

• Done some research myself
• Explained what I’ve already tried to solve my problem
• Stated what I expected, why I expected it, and the actual results
• Formatted my code
• Checked my spelling and grammar
• Pasted the exact, complete error message, if there is one
• Read my whole question carefully to make sure it makes sense and contains enough information for someone coming to it without any of the context that I already know?

After you’ve asked your question

I have checked…

• Are you monitoring your questions and replying to people giving their time to help you?
• Have you been asked for a Minimum Reproducible Example?
• Have you posted an easy to understand answer to your questions that includes everything you learnt

Coursework content

Final Demo

• What? Demo Day is when you will present your final MVP Product to your cohort
• Why? It’s an excellent exercise on how to sell yourself and your teamwork and to celebrate your achievement
• How? Present your product in 10 minutes using a combination of presentations, live demonstrations and videos. Make sure everyone in the team is speaking.
• What? Tell the story of how and why you built this product. Use the below inputs - Explain what they’ve achieved - What have you learned, personally and as a team? This can be related to technology, product, process,… - Which parts did you find most enjoyable and/or interesting? - Has that impacted what you’re thinking about in terms of careers or next steps? How? - How did you find collaborating as a team? What was made easier or harder by working with others compared to working largely on your own - How happy are you with where you got to? - What did the users think? - What part of the product would you build next if you had more time?

Presentation tips:

• Have a script for the demo and practice it!
• Practice switching between demo and slides so that you don’t waste too much time on it
• Use tabs to pre-fill forms - we don’t need to see you type out stuff, especially if you don’t explain it
• Use Incognito mode to prevent logging into/out. With incognito mode, you can be logged into multiple accounts at once
• Consider recording a (silent) video of the demo - what if there’s no internet? Or the app goes down?
• Get someone to hold the mic if you’re typing/demoing - then you have two hands!
• Make the font bigger so people can see it at the back of the room. (Ctrl-+ on Windows/Linux or Cmd-+ on Mac)

Common questions after the demo It’s a good idea to prepare answers to these questions:

• What was your biggest challenge?
• If you were starting from scratch, would you change anything?
• How did you test your app?
• How does your app work on mobile devices? Did you think about accessibility?

Estimated time in hours

4

What is the purpose of this assignment?

Have a presentation ready for you and your team to demo your final MVP Have your codebase finalised

• make sure your README is filled out and presents your project.
• make sure your repo is linked on your deployed site and your deployed site is linked on your repo.
• fork your group project to your personal Github and pin it to your profile

How to submit

Add a link to your repository Add a link to the final presentation and repository for this issue

Coursework content

Practising interviews means you get more used to identifying good examples to sell yourself and gaining confidence in these situations.

Estimated time in hours

60

What is the purpose of this assignment?

The purpose is to practice behavioural interviews.

1. Find someone in the community that can interview you. They should think about “Would I hire this trainee?” when interviewing you.
2. Agree on a time/date for the interview. You should NOT know which questions they will ask beforehand.
3. Do the interview. Use the STAR model in your answers.
4. Ask for feedback to understand what was missing and be better prepared next time.

How to submit

Write a comment on this issue that describes:

• What questions were asked
• What answers did you give
• Feedback received
• What will you do differently

The text should have no grammatical errors.

Anything else?

N/A

Coursework content

Your team must send this form weekly. This link is just an example. Your cohort form should have been shared on your Slack channel; if not, ask for it. Every week, this form must be sent by a different trainee, so talk to your peers and make a rota.

Estimated time in hours

0.5

What is the purpose of this assignment?

Ensure your team’s progress is being updated

How to submit

• Fill in the information that is requested
• Add the newest presentation
• Let your team know that this has been done

Anything else?

N/A

Coursework content

Go to your weekly catch-up and reflect on it

Estimated time in hours

1

What is the purpose of this assignment?

• Participate in the weekly catch-up.
• Reflect on how the meeting went for you. For example: Could you have said something differently? Should you have asked any other questions? What did you like and not like most in it? What have you learned?

How to submit

1. Add a short 50-100-word reflection as a comment on this GitHub issue.
2. Make sure it is reviewed with Grammarly or similar. You should have no grammar mistakes.

Anything else?

N/A