A real critical path
FS, SS, FF and SF dependencies with lag; the Gantt computes slack and flags which tasks cannot slip.
Projects
Know today whether your project will land on time and on budget.
Plan with a WBS and a critical-path Gantt, execute with sprints or Kanban and log hours per task. Earned value (CPI and SPI) is recalculated from what the team actually does, not from what someone remembers to fill in on Friday.
Without MKA
- The schedule lives in a file nobody has opened since kickoff.
- You find out about the cost overrun once the project is already over.
- Team hours are pieced together at month-end from chats and memory.
What you’ll measure
Portfolio CPI
0,97+0,05
earned value / actual cost
Portfolio SPI
0,94+0,03
earned / planned value
Approved hours
96,8 %+11 pts
timesheets on time
Team velocity
42 pts+8 pts
average of recent sprints
Sample indicators with illustrative data. In MKA they are computed live from your operation.
Try it right here
Stretch a task and watch the critical path move.
The project manager stretches tasks on the Gantt and the critical path recomputes in red; then the team moves cards on the Kanban (with the arrows or by dragging) and progress goes up on its own. Press "Watch it run" to see it end to end.
Try it right here
Log this week’s progress and watch the S-curve.
Close a week, let the team log overtime and approve it as project manager: CPI drops, EAC shows the overrun and an @mention alerts the task owner. Press "Watch it run" to see it play.
Example flow
From idea to earned-value report
Step 1/6
The project is created and activated
With team and resources; later it can be put on hold, resumed, closed or cancelled.
Benefits
Why Projects in MKA
Earned value without spreadsheets
Baseline, S-curve, CPI and SPI recalculated on actual progress and cost.
Proper Scrum and Kanban
Sprints, backlog, Product Goal, Definition of Done and velocity; boards with configurable columns and transitions.
The board drives progress
Moving a card updates project progress; there is no percentage someone has to remember to edit.
Approved hours per task
Weekly timesheet with copy-week and bulk entry, submitted, approved or rejected.
Conversation on the task
@mentions, activity feed and attachments, plus "my work items" and "my week" views.
In detail
Everything included
Planning
- WBS with phases, tasks, epics, stories, bugs and milestones
- FS, SS, FF and SF dependencies with lag
- Critical-path Gantt: forward pass, backward pass and slack
- Baselines used by the earned-value analysis
- Task import wizard
Agile
- Sprints with activation and close, backlog and Product Goal
- Definition of Done and team velocity
- Kanban with configurable columns, statuses and transitions
- Flow metrics; moving a card updates progress
Time and cost
- Hours per task and weekly timesheet
- Copy week and bulk entry
- Submit, approve and reject
- Earned value with recalculation and S-curve
Collaboration and reports
- @mentions, activity feed and attachments on every task
- "My work items" and "my week" views
- EVM, flow, hours, valuations and velocity reports
All-in-One
Connects with
Data flows between modules on its own: no integrations, no exporting or importing.
ConstructionMeasurements, progress certificates, contracts with guarantees and site order book.Notifications & collaborationFollow documents, mention your team and know instantly.Importers & migrationAbout 27 import wizards with validation before saving.Report BuilderBuild your own reports across 21 business objects, without asking IT.
FAQ
Do I have to choose between Gantt and Scrum?
No. The same project has its WBS and Gantt and can also be executed in sprints or on a Kanban board.
Is the baseline drawn on the Gantt?
The baseline feeds the earned-value analysis (S-curve, CPI and SPI); the Gantt shows the current plan with its critical path.
More in Projects & operations
See Projects with your data.
In 30 minutes we walk through your real flow: from sale to invoice, from stock to journal entry.