Project management template
Lanework
For a small software team that works in two-week sprints. Slate grays and teal highlights, dense issue cards and a planning bar that adds up the points.
Opens the prompt in Crisp so you can change it before the build starts.
The look: Slate Pro.
Focused and precise: slate grays, teal highlights, dense tables. Headings in IBM Plex Sans, text in IBM Plex Sans.
- background
- surface
- foreground
- primary
- accent
- Opening
- split: a sharp promise beside a dense, real preview of the product (a table or chart with data)
- Sections
- a logo-free row of three facts, a feature grid in hairline-bordered cells, a pricing table
- Motion
- reveal on sections
- Texture
- a faint grid faintly behind the hero
The screens.
- 01Board
- 02Backlog
- 03Issue
- 04Sprint report
- 05My work
- 06Project settings
- 07People
Build a work tracker for my software team of eight called Lanework: a kanban board with two-week sprints. Data: projects (name, short key such as WEB), sprints (project, name, start date, end date, goal, state: planned, active, closed), issues (key and number, title, description, type: story, bug or task, status: backlog, to do, in progress, in review, done, assignee, estimate in points, priority, sprint, labels), comments (issue, author, text) and activity (issue, who, what changed, when). Screens in order. The board: a page header with the active sprint name and a one-line summary, stat cards for points done of committed, issues in review, open bugs and days left, then a column per status with issue cards you drag between them. The backlog: issues not in a sprint, ordered by priority, with drag into the next sprint and a planning bar that adds up the points. An issue page with the description, comments and activity. Sprint report: a burndown chart and the lists of what was finished and what carried over. My work, for whoever is signed in. Then project settings and people. Starting and closing a sprint are explicit actions; closing moves unfinished issues to the backlog or the next sprint. Roles: admin and member. Seed one project with three closed sprints, an active one halfway through, and sixty issues.Use this template
What Crisp builds from it
- A drag and drop board with a column per status
- A backlog with sprint planning and point totals
- Issue pages with comments and an activity log
- Start and close sprint actions with carry-over
- A burndown chart for each sprint
Change the name, the town and the details to yours before you start. How a build works.
More project management templates.
- Deskline
Every client project, its health and its hours, on one page
- Plumbline Builders
Jobs, site logs, variations and snags for a building firm
- Proofline
What publishes when, what is stuck, and who is writing it