Project Management Software With a Standup Drafted From Your Work: Meet nex-orbit

This post introduces nex-orbit, Nexcubator's project management software: boards, sprints, goals and the daily Standup. For the whole picture, read What Is Nexcubator?

Does your board say one thing and your morning standup another? Is there a task that has sat in Doing for three weeks, and nobody has said a word?

Nobody is careless. The work, the plan and the daily update just live in different places, carried between them from memory. Good project management software should close that gap, and good task management should mean writing a task once, not typing it again for every tool and every meeting.

The solution: project management software that keeps the board, the sprint and the standup in step

• A kanban board that stays true. A task needs an estimate to leave To plan, and it is then fixed. Waiting and dropping need a reason, and a task stuck in one stage says so.
• Workflows you can read. Who may move a task where, and what needs approval, is a flowchart you can test before it goes live.
• Agile sprints when a project wants them: sprint planning from a backlog with a goal, story points, a burndown chart, velocity and a review.
• A daily standup drafted from your own work. You check it and press Share. Nothing goes anywhere until you do.
• Task management that travels. One task feeds your sprint, your Standup, nex-cal's Plan my week and nex-track's timesheet draft.

About the visuals: there are no screenshots in this post. The diagrams are illustrations drawn to explain the ideas, not product screens, and the screens themselves may change. The company, people, projects and figures in them are invented.

Why project tracking drifts, and what it costs

It is half past nine. Five people stand round a screen and take turns remembering what they did yesterday. The big job's estimate was quietly changed to match what it took, so the plan looks perfect and teaches nobody anything.

A board is only as true as the last time somebody moved a card, and a standup is only as true as somebody's memory.

The people and figures in our examples are made up. The pattern is not unusual.

A week at Harbour Works: an illustrative case study

Harbour Works is an invented design and build studio. Nora Byrne, David Wilson, Emily Hart, Liam Farrell and Aoife Byrne are invented people, and every figure here is illustrative.

David leads the Harbour app project. Its header sums it up: open, done, overdue, hours estimated and progress, and the goal it serves, Launch the online shop. Under it is the kanban board, one column per stage, each with its count and total estimate.

On Monday Emily drags Plan the beta into Doing. The board asks first: how long will it take? She picks an hour, and that estimate is now fixed. Payment provider keys cannot move until the provider replies, so she drags it into Waiting, and the board asks what it is waiting on.

Nora has drawn the studio's workflow, Delivery with QA: only somebody with the QA role moves a task to Done, and the lead approves it. Before publishing she presses Try a move as Aoife, who is not in QA, and watches it end at Refused, with the words Nora wrote: "Only QA closes tasks here." The rule is checked before anyone meets it for real.

The Northwind Bakery fit-out runs in two-week sprints. Liam planned Sprint 1 from the backlog with a goal, "Ovens and counters in, staff trained", and 19 points committed. The Sprints tab shows its progress and a burndown against the ideal line.

At the end, Complete sprint shows 8 points done against 19 committed, and the two tasks not done. Liam sends them to a new sprint on the cadence, writes "Counters arrived late from the supplier." as the review note, and posts it as the project's status update, At risk. Velocity adds the sprint to the team's history.

On the Gantt, a task called Hero copy shows why a plan needs comparing with what happened. The light bar is the plan. The line under it is blue while the work ran inside the plan, then red where it ran past it, and the task reads 7.5 h booked of 10 h. Its finish date slipped though the hours did not, which is worth knowing next time. Payment provider keys has an amber stretch: the time it sat waiting on the payment provider, not on anyone in the studio.

On Thursday morning Emily opens Standup. Her update is already drafted from her own work: yesterday's Checkout copy, today's tasks, and a support ticket she picked up. Checkout copy carries on, so she presses Continue in Today and gives a reason the team will see: "Legal asked for one more change." Beside it, a panel only she can see suggests three things to focus on and lists what changed on her work while she was away.

Harbour Works has set a daily minimum, so when she presses Share, Standup first asks for her last working day: "Log Wednesday, 7 Oct first." Wednesday is already drafted from her calendar and her tasks: any meetings come with their hours, and she gives the hours for the task she worked on. She presses Log & share, and the hours go into her week in nex-track while her update goes out. Each item goes only to its own project's standup, so the app team hears about the app and the support desk about the ticket.

Why there are other project management tools, and what they miss

Teams buy other tools for good reasons. A task board is quick to start and easy to read at a glance. A spreadsheet plan is flexible, and everybody already has one. A standup bot in chat saves a meeting. A separate timesheet app gives payroll and billing the hours they need, and a goals document gives leadership one place to say what matters.

Each of them does its own job well. What they miss is the space between them, and that space gets filled from memory:

• A task board shows where a card is, not whether it is true. Cards sit in a column for weeks, and an estimate is quietly changed to match the actual. nex-orbit asks at the moment a task moves: an estimate to leave To plan, then fixed; what a waiting task waits on; and after eight working days in one stage, the task says it is stuck.
• A spreadsheet plan is made at the start and rarely compared with what happened. On nex-orbit's Gantt, the line under every bar shows the outcome, with the hours booked in nex-track beside it.
• A standup bot in chat asks everybody to type yesterday from memory. nex-orbit's Standup drafts it from your own tasks, tickets, to-dos and notes. Only you see the draft, and nothing is shared until you press Share.
• A separate timesheet app asks for the same work again on Friday. Standup drafts your last working day's time from your calendar and tasks, with hours where your focus time or your own actions say how long. You glance and confirm, and nothing goes in your week until you press.
• A goals document lives apart from the projects. In nex-orbit every project serves a goal, or is flagged until somebody decides, and a goal closes as Met, Missed or Abandoned with a written verdict.

None of this needs a plug-in or a connector between tools. The board, the sprint, the Standup and nex-track already read the same tasks.

The rest of this post explains the ideas underneath.

Concept 1: A kanban board that stays true

The idea: a few small questions, asked at the moment a task moves, keep the board honest without anybody policing it.

Each project names its own stages, and every stage counts as To plan, Ready, In progress, Waiting, Done or Dropped.

• An estimate before leaving To plan, then fixed: "Record what it really took instead." With nex-track on, Actual sits beside it, as a total, never split by person.
• A reason to wait, and the longest wait shows first.
• A reason to drop. Nothing is deleted; each dropped task keeps its reason.
• Stuck is visible. More than eight working days in one stage, and the task says so.

Concept 2: Workflows you can read

The idea: who may move what, and what needs approval, should be a picture anybody can read.

A workflow is a flowchart that runs every time somebody moves a task, whether by dragging, Ask Genie or the Planner. Condition diamonds ask which stage it is moving to, who moves it, its type or priority, or whether it has an estimate. It ends at Allow or Refuse, and on the way it can give the task to somebody or wait for a person to approve.

A refused move goes back, and the person sees the workflow's own words. Changes are drafts until published, and Administration can always move a task, so nobody is ever stuck. A project can also choose no workflow at all, so anybody may move tasks anywhere: useful in project management for small teams, where a rule nobody needs is just a rule in the way.

Concept 3: Agile sprints and sprint planning, when a project wants them

The idea: sprints suit some projects and not others, so they are a choice per project.

Sprints are off until a project turns them on. Then you choose a length of one to four weeks, a start day, and story points or a simple task count. You plan each sprint with a goal, drag tasks in from the backlog and press Start sprint; what is in it then is what was committed, and the project is told.

While it runs, the board shows the sprint with its goal, days left and points done, and the burndown chart shows what is left each day against the ideal line. Completing it asks where unfinished work goes and invites a review note, and velocity shows committed against done, sprint by sprint. Burndown and velocity are the team's numbers, never one person's.

Concept 4: Plan against outcome, and against goals

The idea: a plan is only useful if you can see afterwards how reality differed from it.

On the Gantt you drag bars to replan, and tasks waiting on a moved one are pushed along. The line under each bar shows what happened: blue within the plan, amber waiting at somebody else's desk, red past the plan, with the hours booked from nex-track.

Above projects sit goals on four rungs, Leadership, Manager, Team and Individual, each serving one goal a rung up. A project with no goal is "Allowed — and flagged, so nobody forgets to decide what they are for." A goal closes as Met, Missed or Abandoned with a written verdict, and its page shows the hours that went to it, by project, never by person.

Concept 5: A daily standup drafted from your work

The idea: your daily update should start from what you actually did, and you decide every word that is shared.

Your update covers tasks, tickets, to-dos and notes. It arrives as a draft, built from your own work by rules, or proposed by AI where your organisation uses it, and then labelled: "it can make mistakes, so check it." Only you can see a draft. You move items between Yesterday, Today and Blocked, carry work forward with a reason, add a note or ask for help. Nothing is shared until you press Share, and Take it back withdraws it.

The morning panel is private: things to focus on, suggested changes to your own tasks that you approve or skip, and what changed while you were away. Nobody else can open it, not even an administrator, and it is deleted after 14 days. On the team page, Needs attention lists blocked, late or quiet work, "counted by the app … no AI, and never about a person."

With a daily minimum set, Standup asks for the last working day's hours before you share. Where your organisation allows it, you can share with a short reason instead, such as "half day", or it is only a reminder.

Concept 6: Task management that travels: one task, five places

The idea: write a task once, and let it help you everywhere.

The task lives on the board. From there, the same task turns up wherever you need it:

• In the sprint, with its story points counted on the burndown.
• In your Standup draft, in Yesterday, Today or Blocked, for you to check and share.
• In nex-cal, Plan my week reads the tasks assigned to you on every board and finds them time around your meetings. Tasks waiting on someone are shown, never planned.
• In nex-track, Draft my week offers your work on tasks as timesheet lines you complete with the hours, and focus time booked for a task as certain. It never invents hours.

The principle underneath: the work is visible, people are not scored

• Questions, not policing. The board asks for an estimate or a reason when it matters, then gets out of the way.
• AI drafts, a person decides. Genie's draft tasks, suggested changes and proposed update are labelled, and nothing is made, changed or shared until a person presses the button.
• Numbers about work, never about people. Burndown, velocity, actual hours and Needs attention describe tasks, sprints and goals. Before Standup is switched on, an administrator confirms it will not be used to assess people.

You can see the whole picture on the Projects and work page and how it fits the rest of Nexcubator in How it works.

Frequently asked questions

Related reading

• What Is Nexcubator?: the ideas behind Nexcubator and all its apps.
• Projects and work: the nex-orbit feature page.
• Forgot Your Timesheet Again?: how nex-track drafts your week from your tasks and meetings.
• The Calendar That Understands You: how nex-cal plans your tasks around your meetings.

Where it stands

nex-orbit is Nexcubator's project management software, and is available in the beta now, alongside nex-cal for planning your week and nex-track for time.

If your board is a week behind and your standup is a memory test, start there. That is exactly the conversation we want to have.

---

Nexcubator is business software by Aitina Tech. Request early access and tell us how your team keeps track of its work.