--- title: "Project software for development teams" description: "A developer speaks freely for 50 seconds — Toolyte turns it into 5 modules with 40 fields and 3 reminders for quarters, milestones, tasks and demos." url: "https://toolyte.com/en/real-trades/software-for-development-teams/" language: "en" last_updated: "2026-09-04" alternate: "https://toolyte.com/de/echte-gewerke/software-fuer-entwicklungsteams/index.md" --- > Index: https://toolyte.com/en/real-trades/software-for-development-teams/llms.txt · Full content: https://toolyte.com/en/real-trades/software-for-development-teams/llms-full.txt Software for development teams & in-house projects # Quarterly planning, milestones and demos in one project software A developer describes in a single voice message how their team works: quarters are planned in advance, broken down into milestones and tasks, scrum meetings run regularly, and internal stakeholders get to see demos. **That one recording produced five modules with 40 fields** — including the links between Project, Quarter, Milestone, Task and Meeting, and three reminders tied to status fields. What the recording produced 1. Project 6 fields 2. Quarter 6 fields 3. Milestone 8 fields 4. Task 9 fields 5. Meeting 11 fields 40 fields 3 reminders 5 links [Set up your own project model](https://app.toolyte.com/signup) [Read the transcript](https://toolyte.com/en/real-trades/software-for-development-teams/#aufnahme) Starting point ## Four things that cost attention in a developer’s week Not the programming, but everything around it: planning, keeping the overview, preparing, reporting status. That is exactly what the recording is about. - ### Plan quarters up front Every quarter is planned and broken down into milestones and tasks. That breakdown has to live somewhere binding. - ### Keep milestones in view The overview of milestones and tasks is the basis for the next round of planning, not just a status display. - ### Prepare scrum meetings Regular meetings check whether the path still holds. A reminder beforehand turns the meeting into a prepared session. - ### Keep stakeholders informed Internal stakeholders want to know where the team stands and what comes next. That is what demos are for — as video on the milestone. The recording ## Told freely, once: how the team works No form, no template, no consulting: a developer speaks into their phone the first time they open Toolyte. These 50 seconds are the entire input. I am a software developer and I work with several people on an in-house project. Every quarter is planned in advance, and what gets planned is broken down into milestones and tasks. Being able to keep a good overview of those milestones and tasks matters to me. It also helps with the planning. On top of that we hold regular scrum meetings to check whether we are still on the right path. Here too it would be good to get reminders beforehand, so we can prepare properly. In agile software development, changes and adjustments to the plan happen again and again. Our internal stakeholders always want to know where we stand and what the next step is. That is what we prepare regular demos for. I would like to attach those demos to the milestones, so they stay available as video. - Every quarter is planned in advance. Quarter module with start, end and status - … broken down into milestones and tasks. Milestone and Task, linked to each other - Regular scrum meetings … reminders beforehand. Meeting module with recurrence and reminder - Attach demos … to the milestones, as video. Video recording on Meeting, Meeting on Milestone The result ## Five modules that point at each other Project, Quarter, Milestone, Task, Meeting. Every module knows the one above it: a task hangs off its milestone, the milestone off its quarter, the quarter off the project. Pick a module to see its fields. 1 Project 6 fields 2 Quarter 6 fields 3 Milestone 8 fields 4 Task 9 fields 5 Meeting 11 fields ### Project 6 fields · Title: Name #### Master data - Name Required Text - Description Long text - Objective Long text - Status Required Choice Planned, In progress, Paused, Completed #### People - Project lead Required Team member - Stakeholders Team member multiple ### Quarter 6 fields · Title: Label · Year #### Planning period - Label Required Text - Year Required Number - Start Required Date - End Required Date - Status Required Choice Planned, Being planned, Running, Completed #### Assignment - Project Required Link → Project ### Milestone 8 fields · Title: Name #### Overview - Name Required Text - Description Long text - Status Required Choice Planned, In progress, Completed, Blocked - Target date Required Date - Priority Choice Low, Medium, High, Critical #### Planning - Quarter Required Link → Quarter - Person responsible Required Team member - Success criteria Long text 7 days before "Target date" The team should be able to react to delays well before the target date. Not when Status = Completed ### Task 9 fields · Title: Title #### Task overview - Title Required Text - Description Long text - Status Required Choice Open, In progress, Blocked, Completed - Priority Choice Low, Medium, High, Critical - Due date Date #### Assignment - Milestone Required Link → Milestone - Assignee Required Team member - Effort (hours) Number - Dependencies Link → Task (multiple) 2 days before "Due date" The assignee should be alerted to open work before it falls due. Not when Status = Completed ### Meeting 11 fields · Title: Title · Date #### Meeting details - Title Required Text - Kind Required Choice Scrum meeting, Demo, Other meeting - Date Required Date - Time Text - Status Required Choice Planned, Confirmed, Held, Cancelled - Recurrence Required Choice Once, Weekly, Every two weeks, Monthly, Quarterly #### Content - Agenda Long text - Next step Long text - Attendees Team member multiple - Milestone Link → Milestone - Video recording File 1 day before "Date", repeating as set in "Recurrence" The team should have time to prepare for recurring scrum meetings and demos. Not when Status = Cancelled or Held ### Links in the model 1. Task 2. Milestone 3. Quarter 4. Project On top of that: Meeting → Milestone (so the demo hangs off the milestone), Task → Task for dependencies, and people fields for project lead, stakeholders, owners and attendees. Reminders ## Three reminders that read the status along the way Toolyte spots the date fields in the model and proposes the reminder together with its condition. Anything completed or cancelled stops reminding. - Module · Milestone 7 days before "Target date" The team should be able to react to delays well before the target date. Not when Status = Completed - Module · Task 2 days before "Due date" The assignee should be alerted to open work before it falls due. Not when Status = Completed - Module · Meeting 1 day before "Date", repeating as set in "Recurrence" The team should have time to prepare for recurring scrum meetings and demos. Not when Status = Cancelled or Held Agile means it changes ## The model stays editable, even mid-quarter Adjusting the plan is part of agile development. That is why the result of the voice message is a proposal, not a fixed schema. ### Add fields Story points, a repository link or a reviewer join in as soon as the team needs them. ### Rename terms If you say sprint instead of quarter or epic instead of milestone, it gets renamed — no migration. ### Tune reminders Two days before the due date too tight? Lead time and condition change in the module itself. Frequently asked ## Project software for development teams, briefly explained The most common questions about the initial setup by voice message. - **How does the project model come out of a voice message?:** You describe once, freely, how your team plans and works. Toolyte identifies the objects, their fields and their relationships and creates them as a proposal. In the documented example that is five modules with 40 fields from 50 seconds of audio. - **Do I have to configure boards, templates or workflows?:** No. There is no fixed template you adapt to your team. The structure comes out of your description, which is why it looks different for a scrum team than for a team with fixed quarterly goals. - **How are milestones, tasks and quarters connected?:** Through link fields: the task points at its milestone, the milestone at its quarter, the quarter at the project. Tasks can additionally be linked to each other as dependencies. - **How do demo videos sit on the milestone?:** The meeting has a file field for the video recording and a link to the milestone. That makes every demo findable directly on the matching milestone, without searching through folders. - **Can I change modules and fields later?:** Yes. Fields get added, renamed or removed, and so do modules. The same goes for the reminders and their conditions — any time, without technical knowledge. - **What does Toolyte cost?:** You test it free for 14 days, no credit card. After that Toolyte starts at €28 per user and month. ## How does your team work? Tell it once in a voice message: quarters, milestones, tasks, meetings. The first structure is there within minutes — with your terms, your deadlines, your links. [Start onboarding now](https://app.toolyte.com/signup)