TechAppForce

Projects and work

Project and work management

Projects, tasks, sprints and time, with the views each team needs.

Book a demoSee how it runs
  1. Backlog
  2. To do
  3. In progress
  4. In reviewApproval
  5. DoneDone
PassedWaits for a personEvery move is kept in the record's history

The problem

What goes wrong today

Today
Generic project tools do not know how your business delivers work, so client codes, billing rules and approvals end up in spreadsheets beside them. Timesheets are chased every Friday and nobody trusts the utilisation numbers.
Who feels it: Delivery teams, project managers and the people who approve timesheets

How it runs on TechAppForce

A day with it, step by step

Amber steps wait in a person's work inbox; everything else moves on its own.

  1. We use it ourselvesWe run our own project management on TechAppForce. Here is the same pattern at an illustrative consultancy.
  2. Monday planningThe project manager plans the sprint on the kanban and checks the Gantt chart to confirm the milestone date still holds.
  3. During the weekPeople move their work items across the board and log hours against them. A reviewer is @mentioned on a work item and gets a notification.
  4. Friday timesheetsApprove or returnAnyone who has not submitted by Friday afternoon gets a reminder. Managers approve timesheets from their inbox.
  5. Month endFinance receives the billable-hours report by client and raises invoices from it.
Illustration. The organisation and people are invented.

What gets configured

Settings you can read, change and release

No code for any of this, unless a rule truly needs it.

Records 5

  • Project5 fields + history, files, comments
  • Work item5 fields + history, files, comments
  • Sprint5 fields + history, files, comments
  • Time entry5 fields + history, files, comments
  • Timesheet4 fields + history, files, comments

Stages 5

  1. Backlog
  2. To do
  3. In progress
  4. In reviewdecides
  5. Done

Automatic 3

  • NotifyAssignees are notified in-app when work is assigned or a comment mentions them
  • ScheduleA Friday scheduled workflow reminds anyone who has not submitted a timesheet
  • WorkflowClosing a sprint moves unfinished work items back to the backlog

Screens and reports 6

  • Kanban board of work items by status
  • Gantt chart of project plans and milestones
  • Scheduler of people and bookings
  • Timesheet grid for the week
  • Billable hours by client and project, in Excel, for invoicing each month
  • Project status report as a PDF for the client
Who approves, in detail

Weekly timesheets go to each person’s reporting manager. Timesheets with overtime also need the delivery head. A reminder goes out on Monday morning for anything still waiting.

When the rules change

Bring your version of this.

A change a few months in is a reviewed release, not a rebuild. We will configure your version with you in a demo.

Book a demoAll use cases

Release: Entity: work item

Types
Unchanged: Task · Bug · Story
Added: + Change request
Fields
Added: + Client approval reference
  1. Developmentmake the change
  2. QAreview the diff, test it
  3. Productionpromote the release
Illustration.