NT Project Manual — a journey from project creation to delivery management

1 · Start here

NT Project organizes work into areas accessible from the tabs at the top of the app:

• ⚙️ Operations — the core: each operation (client/contract) contains its projects. This is where delivery is planned and managed.
• 📈 Executive — portfolio view (all operations/projects).
• 🎯 Focus Projects — a subset of the projects you follow closely.
• 🛠️ Support — demands from ongoing operations (5W1H, Eisenhower, kanban).

Access profiles

2 · Create the Operation and the Project

1. Create the Operation

   In ⚙️ Operations → + New Operation

   The operation represents the client/contract. Enter the name, the operation manager and the technical lead. Then register the teams.

   ⚠️ Required

   • Operation name (unique).

2. Register the Teams

   The operation's 👥 NT Team and 🤝 Client Team tabs

   People registered here become available as task owners. A user created with an @ntconsult.com.br e-mail is automatically added to the NT Team; any other domain goes to the Client Team (see §11).

3. Create the Project

   Inside the operation → + New Project

   Enter the name, start/end dates, PM and Scrum Master. The project dates feed the "expected by calendar" value in Health/Dashboard — without them, the system derives it from the task date range.

   Tip

   Projects can have sub-projects (project hierarchy) and can be archived (removed from the counts without losing data).

3 · Registry — the foundation of tasks

Before creating tasks, register the items that will be available in the task fields. Everything is in Projects → 📝 Registry, organized in tabs:

4 · Define the project structure

You build the structure in whatever way makes sense — and the dimensions coexist: the same task can have a wave, sprint, package, front/stage, story and hierarchy at the same time. Below are the possible arrangements (the same diagrams as in the tour):

5 · Project Setup

In Projects → ⚙️ Setup you define the rules and the workflow structure:

6 · Kanban and task creation

On the Kanban, tasks flow through lanes. Create tasks with ➕ Create new task.

Anatomy of a task

• Owner(s) — multi-select from the NT/Client Team.
• Start/end dates → duration in business days. There is a "no dates defined" flag.
• Links — Sprint (shows the Story), Wave, Package, Story, Front, Stage, Hierarchy.
• Type, Priority (High/Medium/Normal — orders the lanes), Progress (%), Focal point (⭐ lead among the owners).
• Deadline limit (optional) — tolerance beyond the end date. Between the end date and the limit the traffic light goes to attention; after the limit, late. When it differs from the end date it is highlighted (⏳) on cards, the Gantt and popups.
• Flags: 📦 Is delivery, 📍 Is milestone and ⌛ Pending issue (task originating from a project pending issue).
• 🔗 Link tasks new — with "Is delivery" or "Is milestone" checked, the button next to Progress opens the tree of the project structure (hierarchy, wave, sprint, package or front — whichever the project uses). The delivery/milestone % is then calculated from the linked tasks (duration-weighted average) and the field is locked; it recalculates automatically when a linked task is saved. Cycles cannot be created.
• "Link tasks" window new — shows each task's dates, search by name, a Linked only filter, and highlights tasks ⚠ without dates.
• Status (traffic light) — gray (not started), green (OK), yellow (attention), red (late), purple (critical).
• Sub-tasks — each with an owner, its own 🚩 Priority (High/Medium/Normal), % Progress (0/25/50/75/100 or any value from 0 to 100), start and end; they feed the task's progress. The list is shown in aligned columns (owner, dates and %).
• Attachments — files and a SharePoint link on the task.
• Green status in Backlog new — when the status of a task still in Backlog is changed to green (in the form or the grid), the system asks whether to move it to In Progress, with the same rules as dragging (required dates and future-start warning).

Status rule on completion new

When moving a task to Done (drag, 100% prompt or grid):

• Green status → completes directly.
• Gray status (Not Started) → blocks: you must choose a status or cancel. No task goes to Done while gray.
• Yellow/red/purple status → asks whether you want to change the status before completing.

Cards and filters

• On the card, the Sprint chip opens the linked Story(ies) (tabs when there is more than one); the Story chip opens its details.
• The filter bar (type/stage, sprint, wave, package, epic, story, owner) is per project — it does not carry over from another project — and only appears in the Kanban section.
• Card new — priority with a colored flag (High red · Medium yellow); the footer fits on a single line: ⧉ duplicate, sub-task counter and the view/edit/delete buttons. The % appears on the right of the deadline line. The board has a single scroll bar and the lane headers stay fixed.

7 · Dashboard — tracking

The Dashboard consolidates the project's health and progress. Main widgets:

• Project Health (gauge) and Summary Status — a single verdict (Healthy/Attention/Late/Critical) considering pace × calendar and late deliveries.
• Kanban Flow and Task / Delivery Status — counts per lane and per situation (On track, Late, Due today, Blocked, Done, Late deliveries).
• Timeline — Time × Progress — elapsed time vs actual progress (weighted by duration), with a penalty for late deliveries. The ⚖️ Pace checkbox toggles the late sub-task rule (dates only × actual<expected).
• Delayed deliveries — in the popup, clicking a delivery opens it for editing.
• Team Allocation, KPIs and complementary analyses.

⌛ Pending issues

The project's slide-out panel. The side counter only counts pending issues whose situation is Open or In progress.

• Each pending issue has an owner (EC/NT), situation, criticality (C1–C5), blocker/attention, status, impact and Impacted deliveries — shown with their path in the project structure (e.g. Phase 1 › Production deploy), under the delivery's current name and in structure order. Deleted deliveries appear struck through.
• They become tasks automatically: every open pending issue has a task on the Kanban with the ⌛ Pending issue flag (no duplicates). Completed → task in Done at 100%; cancelled/deleted → task archived. With no resolution date, the task has no end date ("NOT DEFINED" on the Gantt).
• Deadline limit new (optional) — same rule as the task (tolerance after the resolution date). A pending issue past its deadline limit is shown as the delay reason on the Dashboard, the One Page and the Overall Status (AI).
• The client profile does not see the Pending issues panel.

📄 One Page Status new

One Page Status button on the Dashboard: a one-page report for the client, exportable as PNG/PDF.

• Header with operation, project, health and the STATUS AS OF badge (date/time of the status) highlighted.
• Schedule — the same Gantt as in Projects (read-only, fitted to the width): Group by Front/Stage, Package or Hierarchy; Show all tasks or only deliveries & milestones; Period full or late & upcoming; show/hide the table. The customization is saved for the next time it is opened.
• Project pending issues (open, by criticality, with the impacted deliveries), Client-origin Risks and What we did · are doing · will do.
• Collapsible sections new (What we have already done, Pending issues, Risks): click the title to collapse; a collapsed section is left out of the PNG/PDF. The PPF shows 5 items per column, with "show more".

8 · Other project views

9 · Governance and tracking

• Risks (with a required Name) and Definitions/On the radar — mapped per project and reflected in the Summary Status; an open risk with medium/high probability puts the project at least in Attention.
• Baselines — snapshots of the plan (weekly automatic + manual) to compare deviations.
• 💾 Plan backup new (Registry › Plan backup) — saves and restores the complete plan: tasks (with Front/Stage, dependencies and sub-tasks), waves, sprints, packages, epics, stories, deliverables, risks, definitions, pending issues, calendar and the attachment references. Restoring a baseline first creates an automatic backup. The 🧭 Reapply Fronts/Stages button fills only the empty Fronts/Stages from a backup, without changing anything else.
• Overall Status (AI) — executive narrative and objective summary, respecting the configured delay criticality.
• Notifications (🔔) and concurrency control — per-task edit locks and a warning when another user changes the project.
• Interface — clean look (pastel tones) as the default for everyone and automatic data refresh when switching screens.
• Audit — all relevant actions are logged.

10 · Executive · Focus

11 · Support 🛠️ module

The 🛠️ Support tab (top of the app) is for ongoing operations: tracking maintenance/evolution demands for client environments, prioritizing them and following them up. Access is restricted to the admin profile (with per-user permission).

How the journey works

1. Register the Support Client

   In 🛠️ Support → + New Client

   Each client is its own workspace, with a segment, SLA, contact and the team (NT and Client professionals) who will own the demands.

2. Log the Demand (5W1H plan)

   Inside the client → new demand

   Describe the demand using 5W1H: What, Why, Where, When, Who and How. Enter the dates (start/end), owner, urgency and impact.

3. Prioritize (Eisenhower + RICE)

   🎯 Matrix view

   Based on urgency × impact, the demand falls into an Eisenhower quadrant: Do (urgent+important), Schedule, Delegate or Eliminate. A RICE-lite score = (Reach × Impact × Confidence) ÷ Effort helps order what to tackle first.

4. Execute on the Kanban + progress tasks

   📋 Kanban view

   Demands flow through lanes (the same as the Operations Kanban: Backlog → In Progress → … → Done), with drag-and-drop. Each demand has progress tasks with their own progress; demands past their deadline get the ⏰ Late badge.

Two views

12 · Users, profiles and security

In 👤 Users (admin). Each user is assigned a profile and the operations/projects they can access.

• Automatic team registration new — when creating/editing a user with selected operations, they are added as a person of the operation: @ntconsult.com.br e-mail → NT Team; any other domain → Client Team. An external e-mail also forces the client profile.
• Scope — anyone who is not admin/global can only manage users within their own operations.
• First access — password change is mandatory; the guided tour is offered automatically (with a "don't show again" option, saved per account).
• Client — opens directly on the Dashboard of the granted projects; no management navigation.

13 · Quick reference

Task status traffic light

Task icons (Kanban · Gantt · One Page)

Required fields (summary)

Recommended work order

1. Create the Operation + Teams.
2. Create the Project (with dates).
3. Registry: waves, epics/stories, sprints, packages, deliverables.
4. Define the structure and the Setup (fronts/stages, hierarchy, calendar, criticality).
5. Create tasks on the Kanban and execute.
6. Track through the Dashboard and generate the Overall Status.