Compiled Learning Objectives

At the end of the sprint, you should be able to do the following things. Make sure to check you can do them all, and if not, go back and keep practicing until you can.

Gathering requirements (Prep)

• Define product, MVP, feature, user story

Reacting to user input (Prep)

• Explain how JavaScript can react to user input from a search input

Break down the problem (Prep)

• Identify and sequence sub tasks

Identifying state (Prep)

• Identify the state in a given problem

Refactoring to state+render (Prep)

• Structure code to use state and render
• Define refactoring
• Refactor code

Rendering based on state (Prep)

• Filter films based on search terms
• Render a filtered list

Capturing the user event (Prep)

• Add an event listener to a user input

Re-rendering (Prep)

• Re-render a page based on user input
• Debug why a page isn’t re-rendering as expected

Actually re-rendering (Prep)

• Group UI components by whether they need to re-render
• Control which UI components are re-rendered

Book Library (Backlog)

• Fix known bugs in an application
• Use an application’s specification to find any unknown bugs

Linkedin Social Selling Index (Backlog)

• Create an active presence on LinkedIn

Mandatory Sprint 2 Codewars Katas (Backlog)

• Practice applying concepts related to the sprint’s prep material in a kata.
• Problem solve a new coding challenge.

Prepare a demo for Q&A workshop (Backlog)

• Have a demo ready to give at the workshop on Saturday

Your LinkedIn tips (Backlog)

• Write 100 words explaining three tips for using LinkedIn

Your SWOT analysis (Backlog)

• Conduct a personal SWOT analysis

Review your Development Plan (Backlog)

• Review your development plan
• Identify the format of a SMART goal
• Revise one short, medium, and long term SMART goal in your plan

Mentored pair programming (Backlog)

• Talk aloud when thinking about a problem.
• Write code in front of someone else.
• Analyse your strategies for solving problems in code.

Demo Questions & Answers (Day Plan)

• Think of a good question to ask after a demo
• Explain what makes a question meaningful
• Give a relevant answer to a question
• Engage an audience in discussion through a Q&A session after a demo

Teamwork Project Sprint 2 (Day Plan)

• Identify users and user needs for a product
• Explain the functionality of a product