Behaviour and protocol

Code Code reviews Consulting 101 Feedback Good meetings practices How to facilitate team meetings Inclusive language Values

Career

360 review Continuing education policy Engineering manager career ladder Roles Software engineer progression framework Technical skills sheet

Employee manual

Abtion's pomodoro Employee benefits Internal days & community Intro Parental leave policy Safety and security Schedule, time tracking & calendar Sickness & unplanned absence Travelling Vacation & planned time off Work from anywhere policy

Project management

Technical setup when starting a new project Client discontinuing hosting or sla Converting projects from development to maintenance mode Estimating Go live checklist Handoffs Invoicing guidelines Procedure for traffic Sla

Setup

Audio setup Create amazon bucket Database backup setup Gpg signing Pairing setup

Technical practices

Bug triaging Css How and why we do design research Kick off meeting Pair programming Tdd testdriven development Workflow

Templates

Readme.standard

Tools and services

Access and permissions Purchasing licenses and memberships Sharing sensitive information Stack and services Wordpress
=

Technical practices

Development Kickoff - Full day, Whole Team

Starting a few weeks after any needed design starts. Entire team is present, including design, client, pm. May cover up to ~3 months of work.

Come away with:

  • Solid understanding of why we are building X
  • Understand the “enough” line (when have we built enough for the client to start using and get feedback on the product?)
  • Find the landmines or “anti-goals” which keep us from reaching the goals
    • Ex: is mobile optimization an anti-goal?
  • Understand tech requirements and platforms
  • Understand users and how they flow through the app
  • Review wireframes + user research : personas, mood boards, brand guidelines, prototypes, copywriting info, styles guides. Put these in gdrive or in pinned slack notes so everyone can find them.
  • Create roadmap together with stories
  • Identify mini-releases along the way
  • Create and sign off on GDPR expectations what data will we persist and how long? Also how will it be exported or deleted?

Timeline

  • Goals - 15min
  • Business Risks/Technical Risks/Landmines - 30-60min
  • Users/Activities/Flows - 30min
  • Story Creation on note cards, mark with priority of high, medium or low- 1 hour
  • Story Creation in Asana for any note card labelled high or medium - 1 hour

Fraxx example:

Development Kickoff Agenda - Fraxx & Abtion

  • Since last time
  • New faces around the table
  • “What have we been up to” (Abtion)

  • Any updates from Fraxx? (Client)

  • Identity design
    • First take on concept, look and feel (Abtion)
  • Development kick-off
    • User stories (All, facilitated by PM)
    • Shaping MVP
    • Prioritizing features
    • Identify mini-releases
    • Find the landmines and anti-goals
  • Clarify the tech requirements (Tech team)
    • Browsers, languages, domains etc.
    • Requirements for video
    • Hosting
    • Need for tracking/statistics
    • Mails
  • Create and sign off on GDPR expectations (PM)
    • What data will we persist and how long?
    • How will data be exported or deleted?
    • SLA / Maintenance in the future

# Remember notes - This is of course with the specific project in mind

  • Hosting of videos - what about the economy vs. quality?
  • What video format do we need in order to fit both mobile, tablet and desktop?
  • Data processor agreement needed?
  • Talk about the time dev and design need to pair
  • Make sure we touch tracking like GA and SoMe
  • The content must be translated to Norwegian by Fraxx
  • What mail system do they use?