Tech roles beyond coding

Stage 2 · Lesson 2 of 9

Agile, sprints, tickets and boards

Technical literacy

Most software teams work in short cycles. In , a popular way of working, each cycle is a sprint of one or two weeks. In Kanban, work flows continuously instead.

Work is split into tickets, small written tasks, in a tool such as Jira, Linear or GitHub Issues. Tickets wait in a backlog, a ranked list of work to do. The team tracks them across a board from to do to done.

Regular meetings include planning, a short daily , reviews and , where the team discusses what to improve. You will write tickets, comment on them or have your own work tracked through them. Learn to read a ticket: the problem, the (the conditions that mean it is done), linked and its status.

Common traptreating the process as the goal. Teams that follow every ceremony but never learn from users are still building the wrong thing.

A question to check yourself, an AI practice session and 1 cheat sheet entry come with the full roadmap. Unlock

Resources for this stage

Start with· follow one of these

  • VideoFree
    Crash Course Computer Science

    CrashCourse · Beginner

    Short free videos on how computers, networks and software work, pitched at beginners

  • CourseFree
    Select Star SQL

    Zi Chong Kao · Beginner

    A free interactive SQL tutorial on real data, enough for product and docs analytics

Practise

Keep handy

  • Clear reference for HTTP methods, headers and status codes

  • See how an API is described formally, which all three roles meet at work

Also worth your time

Mark this stage as not done?