We should target for 2 types of users:
a) simple usage (maybe home planning) with tasks, dependencies only + the 
possibility to add resource assignments and to see overallocation of resources
b) the professional user
Easy access to both user types should be provided, so not to frighten the 
simple user too much nor to make it too complicated for the professional user 
to access his routine functions.

Or how about these two:

a) Entry level user. Default mode, intended for projects that need more than a
simple one page to do list in a spreadsheet.

Typically less than 100 tasks, less than 10 people, weekly project meeting with
status of current tasks, and Gantt Chart or similar upward reporting.

User is a professional (lead programmer, systems analyst, engineer, or middle
manager), not a professional project manager.

b) Professional project manager.  1,000+ tasks, $5mm+ contracts.  Requires data
management and reporting suitable for government contracts; construction
industry; senior executives.  Track documents such as goals; objectives; scope
of work; contract; change of work orders; punch lists; site inspections;
acceptance letters (to subcontractors, from customer); cash flow overall and per
subcontractor; the list goes on.

Since the professional project manager needs everything the entry level user
does, prototypes should focus on the entry level user first, with the intent of
adding features for the professional incrementally.

KISS, when applied to the actual implementation incl. its overall architecture
and design most often leads to either bloated software a/o software that needs
to be rewritten from scratch multiple times. And we actually do not have a
requirement for that.

When it comes to usability and so on, we should definitely go that way.

This KISS approach can be significantly influenced when each row in a task 
table represents one task performed by one person in one time frame with at 
least one predecessor and one successor.  This 'syntax' could dramatically 
simplify what can and should be done to / for each task row.

Reset assignee on issues not touched by assignee in more than 1000 days.

obsolete