How to use

How to use Gtdagenda for Software Development

Gtdagenda has the following structure: Goals > Projects > Tasks

So each task maps to a project, and each project maps to a higher goal. This structure fits perfectly to how most software is developed.

Insert the software product you are working on as a Goal in Gtdagenda.

Each feature the final product will have, will be inserted as a Project in the respective goal.

The work items or tasks that are needed to make each feature, will be Tasks.

Priorities Make Things Happen
These ordered lists have one important line dividing them into two pieces. The top part is priority 1: things we must do and cannot possibly succeed without. These are the core features of the application. The second part is everything else. Priorities 2 and 3 exist but are understood to be entirely different kinds of things from priority 1.

For example, when developing Gdtagenda, the only priority 1 items things were Goals, Projects, Tasks, Schedules, Checklists and Calendar. These are the main features and they also form the top menu bar. Priority 2 and 3 were the e-mail exporting, printing, iCal feed, sharing of projects, due dates, notes, etc. They are important, but they are not core features. Gtdagenda could still function without them.

Clarity is how you make things happen on projects. You must have a strong sense of what you are doing, why you are doing it, and how it relates to other things you are doing.

Use Gtdagenda to manage your projects:

Gtdagenda Features

How to use Gtdagenda

Use Gtdagenda to implement Getting Things Done (GTD) by David Allen
Make Gtdagenda a part of your 7 Habits for becoming Highly Effective
How to implement Zen To Done (ZTD) with Gtdagenda
Manage your Sales Calls with Gtdagenda
How to use Gtdagenda for the Gym
How to use Gtdagenda for School
• How to use Gtdagenda for Software Development