What belongs in a Project?
Projects can represent any area of focused work, including:
- New product features
- Customer-requested enhancements
- Penetration test findings
- Bug fixing initiatives
- Technical improvements or migrations
If a group of tickets contributes towards a single goal, it probably belongs in a Project.
Everything in one place
Each Project is organised into a set of tabs:
- 01
Tickets
Break work down into manageable tasks, assign owners, set priority and phase, and track progress from start to finish.
- 02
Knowledge
Every Project includes a Knowledge Base that gives your team, and Trundle's agents, the context needed to build with confidence. (Access to the Knowledge tab is controlled by a permission, so you can decide who can view or manage it.) Store supporting information such as: - Product Requirement Documents (PRDs) - Customer call transcripts - Internal planning and decision-making notes - Technical specifications - Design documents - Research and discovery notes Trundle embeds everything you upload, so you can ask questions with Ask Trundle and get answers grounded in your own documentation. Trundle also draws on this context automatically when improving tickets or answering clarifying questions.
- 03
Builds
View the builds for your Project: the pull requests the Trundle Dev Agent opened and the runs behind them, so it's easy to connect development activity with the work being delivered.
- 04
Analytics
Track delivery metrics for the project, such as velocity, contributor breakdowns and phase distribution. (See the Analytics article.)
- 05
Settings
Configure your Project, manage its members and repositories, and customise how your team collaborates.
Track work by Phase
Every ticket within a Project is assigned a Phase (one of Discovery & Strategy, Design & Validation, Development & Launch, or Post-Launch & Improvements), giving you a high-level view of where effort is being invested. For example, you might see:
- 7 tickets in Discovery & Strategy
- 3 tickets in Design & Validation
- 10 tickets in Development & Launch
- 2 tickets in Post-Launch & Improvements
Rather than only tracking whether work is "done", Trundle helps you understand where effort is being spent throughout the lifecycle of a feature. (See the Project Phases article.)
Deliver with confidence
By combining tickets, documentation, a Knowledge Base, builds, analytics and project phases into one workspace, Projects give product managers, engineering managers and development teams a single source of truth for delivery, from the first idea through to post-launch improvements.