Skip to main content

Get Started as an Administrator

As an administrator, you can configure projects, schedules, and team access to enable agile planning and tracking.

Obtaining administrator access: Your Digital.ai Agility System Administrator assigns administrator privileges when creating your member account or by updating your member profile. Contact your System Administrator to request administrator access.

A minimal configuration approach helps teams focus on what matters most. Many administrators disable features and limit fields initially, adding complexity as teams mature and identify needs.

Step 1: Create a project​

Set up a project to capture your team's backlog and work items. Projects are the foundation for planning, tracking, and reporting in Agility.

Essential fields to complete:

  • Title: The project name as it appears in the planning level tree (required)
  • Parent Project: Where this project sits in your hierarchy (usually System (All Projects) for your first project)
  • Begin Date: When the project starts (required)
  • Iteration Schedule: Links the project to your sprint schedule so you can create sprints

For complete step-by-step instructions and all field descriptions, see Creating a Project or Increment.

Step 2: Set up sprint schedule and team access​

Configure the sprint (iteration) schedule and add team members to your project. This ensures your team can plan and execute work in timeboxed periods.

Step 3: Add stories to the project​

Populate your project backlog with stories, defects, and other work items. You can import from Excel or create items directly in the backlog.

Step 4: Assign stories to the sprint​

Move backlog items into sprints and break them down into tasks and tests. This enables your team to plan and track work during each sprint.

Step 5: Track work and progress​

Monitor your team's progress using boards, TeamRoom views, and dashboards. These tools help you visualize work in progress and identify blockers.

Common Use Cases​

First-time project setup​

Set up a single team with a new project, sprint schedule, and backlog. See Creating a Project or Increment and Adding or Assigning a Member to a Project.

Scale from one team to three teams​

Expand your project hierarchy to support multiple teams, each with their own sprint schedule and permissions. See Planning Level Hierarchy.

Avoid common project hierarchy mistakes​

Always create projects under System (All Projects) to enable future scaling and cross-project reporting. See System (All Projects).

Frequently Asked Questions​

Why should I create projects under System (All Projects) instead of at the top level?

Creating projects under System (All Projects) preserves flexibility for future scaling and reorganization. This structure allows you to add portfolio-level planning, implement SAFe, or reorganize project hierarchies without recreating projects. Top-level projects outside System (All Projects) cannot be easily moved or restructured later.

What is the difference between Planning Level and Project?

Planning Level is an attribute you assign to a project to indicate its purpose in the hierarchy (Enterprise, Portfolio, Program, Product, Increment). Project is the actual container for work items. Planning Level helps organize and filter projects in large hierarchies, especially when implementing SAFe or portfolio management.

Can I change the sprint schedule after assigning it to a project?

Yes, you can change the Iteration Schedule field on the project details page at any time. However, changing schedules mid-sprint may cause confusion for teams and affect sprint burndown calculations. Plan schedule changes between sprints when possible.

What happens if I create a project without assigning a sprint schedule?

You can still create stories and work items, but you cannot create sprints or use sprint-based planning features. Teams cannot assign work to sprints, and sprint burndown reports will not function. Assign a schedule to enable sprint-based agile workflows.

How many team members can I add to a single project?

There is no hard limit on team members per project. However, teams larger than 10-12 members may benefit from splitting into multiple sub-projects or teams for better agility and communication. Consider your team's ability to collaborate effectively when determining project membership.

Can team members be part of multiple projects?

Yes, members can be assigned to multiple projects with different roles in each. This is common for specialists who support multiple teams or team members who work across product lines. Members see work from all their projects in My Room and can filter by project as needed.

What permissions does a Project Lead have compared to Project Administrator?

Project Administrators have full control over project configuration, including adding/removing members, changing settings, and managing schedules. Project Leads can manage work items, assign tasks, and facilitate team activities but have limited administrative capabilities. See project role documentation for complete permission details.