Trello Sprint Board Set-Up for a Small Team
Set up a Trello sprint board for a small team, with lists, labels, card templates and a simple weekly planning rhythm.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Set up a Trello board for sprint work. Team size and sprint length: [TEAM_AND_SPRINT]. Types of work: [WORK_TYPES]. Estimation method, if any: [ESTIMATION]. Meetings we hold: [MEETINGS]. This is a light board, not a replacement for a full agile tool; say when the team should consider one. Design lists (Backlog, Sprint backlog, In progress, Review, Done and others), card fields for size and priority, labels, a sprint goal card pinned at the top, limits for work in progress, and a way to archive each sprint's Done list. Capacity example: a team of 4 with 8 working days, 1 person away for 2 days and a focus factor of 0.7 has available days = 4 x 8 - 2 = 30, times 0.7 = 21 days. Routines: sprint planning, a 10-minute daily check, and an end-of-sprint review (review the Done list, record what was finished, move unfinished cards, clear the board). Meeting lengths for a two-week sprint, such as planning 60 minutes and review 45, with total time per person per sprint and the arithmetic; they are suggestions to adjust. Rule for mid-sprint work: what is allowed in, what it replaces, and who decides. Be honest that burndown-like information may need a Power-Up or a spreadsheet [VERIFY]. Provide templates for the sprint goal card and review summary, and a friendly one-page team agreement (how we pick cards, show a blocked card, what we do when we finish early, how we handle interruptions), reviewed at the end of the second sprint.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.
See an example result (fictional data)
Invented sample: team of 4, 8 working days, 1 person away for 2 days, focus factor 0.7. Available days = 4 x 8 - 2 = 30. Effective days = 30 x 0.7 = 21. Sprint goal card: Customers can reset their own password. Limits: Review list holds at most 3 cards. Mid-sprint rule: a new card enters only if one of equal size leaves. Check: 21 effective days means the team can plan about 21 days of work, for example seven cards of three days each. Keep two days of slack and plan 19. Rule in use: the Review list limit of three cards stops work piling up; when it is full, the team reviews before starting something new. Review the limits at the end of the sprint.
Illustrative only, made-up data. Your results will differ and must be reviewed.