14-02-2022

1003 words 6 minutes

Meta Stuff

config, updates, installs, software, etc

Today's Foci

Focus 1

  1. What/How?
  2. Measure

Topic

Code Review

Great code! This person had fantastic hygeine - small regular commits

There code ( and tests met SRP )

It looked like good Ruby code!

Teamwork

This week is about building teamwork skills

It is not about the end product - it is about working in a team

Bring everyone up with you

Important things this week

today - get into teams and run through the project

"Can we build an app as a team, using only a spec?"

build a clone of airbnb

Teamwork

What are everyone's strengths?

DOes everyone understand?

This might be a stupid question but?

Just to check my understanding { here's what's going on }?

XP programming

Simplicity

Communication

Feedback

Respect

Courage

XP values

branch review merge

coverage high whilst building new features

Agile workflow

Product backlog - list of features; giant todo list

Sprint backlog - time dependent - aims within a deadline

Sprint - daily standups - Product Increment

Sprint planning

prioritising and estimation

estimation stage

groom the user stories as tickets

which tickets to tackle first how long? usually add x2 possibly x2.5

list of tickets to work on today

Daily stand ups

  1. What did I do?

  2. What will I do?

  3. Blockers?

Git workflow

most value as team-member

Work in code-isolation on your branch - pairs

keep changes seperate to the

only ever merge to the main branch

await approval on PR, then merge to main

MVP minimum viable product

Most minimum allegory for the case - air b'n'b

In this case aim for MVP lunchtime on wednesday

standups / retros

checkins

planning

knowledgd sharing

badstuff

working overtime

exclusion

rushing to implement features

sidelining testing

ergo

create mvp

set rules

  1. everything is tested

  2. SRP

  3. agree on features plan and MVP with everyone

Team Success

defined process for flagging problems

sharing accountability and leadership

enjoy the process and have fun

communicating honestly

GOALS

by 1230

slack-channel January21-{teamname}

create a trello to track the user stories, pin to channel; invite Roi

define working practices

setup the repo

Decide on working practices

working hours

breaks

cycle of stand ups and retros

frustation or change; how?

personal learning objectives?

Rails

diagram

good git workflow

Questions

software dev goals

examples of EPA projects? ( and successful vs unsucessful )

consistenly produce software "of standard"? ( does that make sense? ) for those standards, is there an official document

list of contacts for apprenticeship provider and the employer?

can we find that apprenticeship standard anywhere?

Overview of Apprenticeship standard

Software dev 1.1

Program overview

Portfolio & placement milestons

occupational duties

EPA

First steps in Placement

Line Manager Support

Placement sessions structure

Safeguarding, well-being, ofsted

wider learning

what does the placement look like

shared more once in the placement

12 week bootcamp

placement 9 - 14 months

  • Makers coach, IT assessment team

  • portfolio build

  • 2x assessment reviews - IT assessment team ( who? ) - send work to the IT team for review. Feedback on work.

  • Devise EPA project.

  • For the assessors ( accelerate people ) do they have a specification

Portfolio

STAR, report with visual evidence

Introduction, Body, Conclusion.

  • What you did
  • How you did it
  • Whom with?
  • business impact

Placement Milestones

5 instances for a submission across the 9-14 months

How are these graded?

KSB specific assessment criteria? expect from placement coach, should be about 50

work with RDBMS, clear structured code

release 0 - IT assessment feedback - approve, or constructive feedback - kind of like PhD viva voce

Occupational duties

linked to KSB's - 21?

EPA 2 - 6 months

  • Project and practical

project brief - 500 words

report 4.5k words.

GRADING pass merit distinction fail if fail, redo EPA

First steps in placement

Arrange meeting with line manager

  • Occupational Duties vs KSBs 20% for apprenticeship - 1 day per week.
  • Drive the conversation

Personal

  • Read through the resources

  • Keep a Placement diary

  • Log your CPD/OTJ

  • weekly tickets, problems, who did you work with, how did you work with them?

  • Monthly self assessment

  • How much of the criteria has been covered

Line Manager Support

  • Time
  • Exposure
  • Project Scope
  • Final Approval

Progress Check Format

  • Emotional Check in

  • In work activity duties

  • OTJ/CPD

  • Functional Skills ifrequired

  • Portfolio Feedback

  • Goals for next session

  • Wider Learning

  • Presentation on topics via bud

Safeguarding

  • Makers have a formal duty of care
  • can put apprenticeship on hold

Ofsted

Useful tools

  • Dash - meeting notes access from placement
  • Self Assessment - specific criteria
  • Bud - all tasks

Post-Lunch

Standup-Plan

Headline specifications

Any signed-up user can list a new space.
Users can list multiple spaces.
Users should be able to name their space, provide a short description of the space, and a price per night.
Users should be able to offer a range of dates where their space is available.
Any signed-up user can request to hire any space for one night, and this should be approved by the user that owns that space.
Nights for which a space has already been booked should not be available for users to book that space.
Until a user has confirmed a booking request, that space can still be booked for that night.

Nice-to-haves

Users should receive an email whenever one of the following happens:
They sign up
They create a space
They update a space
A user requests to book their space
They confirm a request
They request to book a space
Their request to book a space is confirmed
Their request to book a space is denied
Users should receive a text message to a provided number whenever one of the following happens:
A user requests to book their space
Their request to book a space is confirmed
Their request to book a space is denied
A ‘chat’ functionality once a space has been booked, allowing users whose space-booking request has been confirmed to chat with the user that owns that space
Basic payment implementation though Stripe.

My instinct is to take the 'headline specs'

user stories

formulate those into diagrams

formulate back into stories/tickets?

build the tickets?