Read the technical brief → · PDF
1. What it does
GoalGetter owns projects and methodology views. It does not own tasks. Structure nodes — for example a WBS element, a Kanban card, or a Gantt bar’s place in the plan — are GoalGetter records; each may point at one TaskMaster task. GoalGetter owns the hierarchy of nodes. If the work itself decomposes, TaskMaster holds parent and child tasks. A WBS element is not itself a task. Milestones are TaskMaster records, linked from GoalGetter structures.
2. Main features
- Projects
- Methodology views: WBS, Kanban, Scrum, PERT and Gantt
- Sprints and boards as GoalGetter structure
- Structure nodes that may each point at one TaskMaster task
- Links from project structures to TaskMaster milestones
- Time may be logged against a GoalGetter subject in TimeTracker, with the task id optional
- Files stored in the shared files application and linked, not in a second file store
3. How it works with other applications
GoalGetter does not own tasks. Structure nodes may each point at one TaskMaster task. If the work itself decomposes, TaskMaster holds parent and child tasks. Milestones are TaskMaster records, linked from GoalGetter structures. Time may be logged against a GoalGetter subject in TimeTracker, with the task id optional. Files are stored in the shared files application and linked, not in a second file store.
← More Operations & workforce apps · All application briefs · How the framework works