M
metiu
I guess someone else has my problem...
Here at work we start from rough requirements, then we talk about them
and explode each requirement into smaller steps.
Then we give each requirement a time cost, and sum them.
Then we categorize them, giving priorities.
Based on the deadline we have, we cut the lower priority requirements
that don't fit in the schedule.
Afterwards, we need to add details to each requirement we chose to
implement, plus tests that validate them.
In the end, we should provide printed evidence of the work done.
I tried to find some app that helps in doing that, but each has some
shortcomings:
- a spreadsheet is too flat, but has the ability of filtering and
calculating
- tree note editors (treepad, keynote) can keep the structure, but
can't do "easy" math, like totaling, and filter
- web based requirement tools are usually hard to setup, clumsy and
much more sophisticated than we need
Do you have any hint?
Thanks
Here at work we start from rough requirements, then we talk about them
and explode each requirement into smaller steps.
Then we give each requirement a time cost, and sum them.
Then we categorize them, giving priorities.
Based on the deadline we have, we cut the lower priority requirements
that don't fit in the schedule.
Afterwards, we need to add details to each requirement we chose to
implement, plus tests that validate them.
In the end, we should provide printed evidence of the work done.
I tried to find some app that helps in doing that, but each has some
shortcomings:
- a spreadsheet is too flat, but has the ability of filtering and
calculating
- tree note editors (treepad, keynote) can keep the structure, but
can't do "easy" math, like totaling, and filter
- web based requirement tools are usually hard to setup, clumsy and
much more sophisticated than we need
Do you have any hint?
Thanks