Name the layer your way.
Use Sprint, Event, Initiative, Job, Campaign, Project Group, or a custom term.
Group related projects without forcing a new process.
Add a flexible layer above projects for a Sprint, Event, Initiative, Job, Campaign, or whatever your team calls it. If you do not need the layer, turn it off.
Structure that fits
Organize the portfolio in your own language.
Use it only when useful.
Keep a simple project list or add the grouping layer when the work calls for it.
See the whole effort.
Track the group and the projects inside it without losing individual ownership or status.
A useful middle layer
Keep related work together.
Group-level datesGive the larger effort a start and due date.
Group statusShow whether the broader initiative is planned, active, or complete.
Connected projectsKeep each project independently owned while showing where it belongs.
Calendar visibilitySee Project Groups alongside their projects and tasks.
Project GroupFall launch
Active- Group created as an Initiative
- Research project added
- Launch project added
- Group dates added to calendar
Questions
Project Groups, explained simply.
Can we rename Project Groups?
Yes. A workspace can use a term such as Sprint, Event, Initiative, Job, or Campaign so Beck matches the way the team talks.
Do all projects have to belong to a group?
No. The grouping layer is optional, and a workspace can keep projects independent when that is simpler.
Do Project Groups appear on the calendar?
Yes. Group dates can appear with project and task dates in the shared team calendar.
Start a conversation
Let’s find out if Beck fits the way you work.
Tell us what you manage and where work gets stuck. You’ll get a personalized walkthrough and a practical path into Beck.