TT board
Get the shell of the product standing up. Guest data in, room configured, nothing seated yet.
Done · 6
| TT-2 | Project scaffold, agents and pipeline | foundation | Done | 8 |
| TT-3 | Set up the room | frontend | Done | 5 |
| TT-4 | Import a scenario | frontend | Done | 3 |
| TT-5 | Add and edit guests | frontend | Done | 8 |
| TT-6 | The guest list | frontend | Done | 5 |
| TT-7 | Design system and app shell | frontend foundation | Done | 5 |
A plan you can trust enough to send to the venue.
Ready for development · 10
| TT-17 | Keep conflicting guests apart | domain rules | Ready for development | 5 |
| TT-18 | Flag tables that need a kitchen brief | domain rules | Ready for development | 5 |
| TT-19 | Keep households together | domain rules | Ready for development | 5 |
| TT-20 | Don't seat all the children together | domain rules | Ready for development | 5 |
| TT-21 | Spread the tag groups | domain rules | Ready for development | 5 |
| TT-22 | Give every table someone sociable | domain rules | Ready for development | 5 |
| TT-45 | Partners adjacent becomes a hard rule | domain rules solver | Ready for development | 8 |
| TT-47 | Every guest has a seat | domain rules | Ready for development | 3 |
| TT-48 | Scale the score by how much of the plan is seated | domain rules | Ready for development | 3 |
| TT-49 | The top table rule counts its chances over the wrong thing | domain rules | Ready for development | 3 |
Done · 7
| TT-11 | Render the floorplan from config | frontend | Done | 5 |
| TT-12 | Place a guest by clicking | frontend | Done | 5 |
| TT-13 | Seat the top table, then fill the room | domain solver | Done | 5 |
| TT-14 | Rules engine and the first three rules | domain rules | Done | 8 |
| TT-15 | Table detail panel | frontend | Done | 3 |
| TT-16 | Score how well a plan fits | domain rules | Done | 5 |
| TT-46 | Score every rule, not only the soft ones | domain rules | Done | 5 |
Outside the MVP. On the board so the backlog reads as a product rather than an exercise.
To do · 6
| TT-23 | Fix the plan by dragging | frontend | To do | 5 |
| TT-25 | The caterer needs numbers | frontend catering | To do | — |
| TT-31 | Print a plan the venue can use | To do | — | |
| TT-32 | Compare two plans | To do | — | |
| TT-33 | Seat people who need seating | To do | — | |
| TT-34 | Share a read-only plan | To do | — |
Ready for development · 1
| TT-36 | Show a guest's details on hover | frontend | Ready for development | 5 |
Done · 4
| TT-35 | Restyle the app to the new design canvas | frontend foundation | Done | — |
| TT-37 | Clear the allocation | frontend | Done | 3 |
| TT-38 | Scroll and filter the unseated list | frontend | Done | 13 |
| TT-44 | Draw the chairs, and say more about who is in them | frontend | Done | 8 |
The app has never been anywhere but a laptop. Nobody outside the room has seen it, and a pull request is reviewed by reading a diff and trusting it.
Ready for development · 3
| TT-41 | Stand the hosting up | infra | Ready for development | 8 |
| TT-42 | Publish main to the live site | infra | Ready for development | 5 |
| TT-43 | A preview for every pull request | infra | Ready for development | 8 |
Ideas worth finding out about, rather than work that has to be delivered.
Ready for development · 2
| TT-51 | Get a guest list out of a spreadsheet | poc | Ready for development | — |
| TT-52 | Say what the plan did, in words | poc | Ready for development | — |