🧑🏾💻 prep
Check your backlog and come to class with questions.
Overcoming Blockers
Reading
Why are we doing this?
In class we will talk about Iteration and Blockers. Read over the day plan. What does iteration mean? What are Blockers? Write down your answers.
Learn about Slack
🤙🏽 FeedbackLearning Objectives
Preparation
Introduction
What is Slack?
🎯 Goal: Understand how Slack works (25 minutes)
- Research Slack and its benefits
- This link talks about interesting tips on how to use Slack
- Watch this video about Slack Etiquette for our community
- Read this text about replying in a thread
- Learn how to organise your sidebar
- Make a list of any questions you have so that you can discuss them with your team members
Code.org
Learning Objectives
Code.org is a block based programming tool. We will use something similar to build our course project. Go to the Code.org website and work through the first two exercises
Exercise
Go to Course Three, Lesson 2: The Maze
- Inspect the interface
- Complete exercise one and two
CYF Blocks
Learning Objectives
For the majority of this course, we will use a custom application called CYF Blocks. It uses the same visual programming editor, Block.ly, as Code.org, but you will use it to create JavaScript for real websites you can show others.
{{<our-name>}} Blocks
- Inspect the interface
- Read the introduction
- Complete all steps in the first exercise
Backlog
Learning Objectives
In software development, we break down complex projects into smaller, manageable parts, which we work on for a week or two. These periods are called “sprints.”
A sprint backlog is like a to-do list. It lists what the team has decided to work on this sprint. It’s chosen from a larger list, usually called the “product backlog,” which holds the entire project to-do list.
For your course, the mandatory work has been scheduled already. You will add any other tickets you want to work on to your backlog and schedule them according to your own goals and capacity. Use your planning board to do this.
You will find your backlog in the Backlog view on every sprint.
Copy the tickets you are working on to your own backlog. Organise your tickets on your board and move them to the right column as you work through them. It’s a flowchart:
Backlog (30 minutes)
- Find the sprint backlog
- Copy your tickets to your own backlog
- Organise your tickets on your board