Documentation
Learn how DevGob organizes work, governs changes on their way to production, and keeps each organization's information separate. Start with the basics, then go to the area you need.
Three steps from no account to a project you can plan work in.
Every organization gets its own workspace at your-team.devgob.com, with its own users, projects and data. Request one from the public form; an administrator reviews it before it is activated.
Request a workspaceSign in at your organization's own address. If you only know the workspace name, the sign-in page will find it for you and send you to the right place.
Go to sign inA workspace holds projects; a project holds teams, a backlog, sprints and deployments. The work-item types, states and transitions are configured per workspace, so the process can match how your organization already works.
Each area below describes what the product does, not what it plans to do.
The unit of work, and the hierarchy that organizes it.
Order the work, then watch it move.
Plan an iteration against the hours you really have.
The part that makes this more than a task tracker: a change goes to production through a governed, evidenced workflow.
What is happening, without asking anyone.
Who can do what, decided by role rather than by person.
Everything a workspace administrator controls.
How one workspace's information stays that workspace's information.
Usable by the whole team, not just part of it.
Every area explained in depth, in reading order. Start at the top or jump to what you need.
If something here does not answer what you need, ask us directly — a person reads every message.
