Tasks\\bugs in the project management system?


Warning: count(): Parameter must be an array or an object that implements Countable in /home/styllloz/code-flow.club/qa-theme/donut-theme/qa-donut-layer.php on line 274
0 like 0 dislike
4 views
How necessary is it for value priority and the progress (a value from 0% to 100%) for task (taska) in the PM system?


In the "classical" systems, they are used in basecamp from 37signals is nothing like that.
by | 4 views

3 Answers

0 like 0 dislike
progress for atomic jobs — a fiction, for aggregate is needed only for reporting and is only necessary for any thread glubokovodnykh splits that do not cover eyes. Or if a lot of them. In General, progress is addressing some external to the workflow problem.
\r
the priority for tasks is needed only at the stage of planning/replanning, although probably important for the dynamic methodologies. But in General, minor — is more important to have dependencies.
For bugs we need not the priority and severity, although whatever you call it... but it is rather in the direction of the display with the SLA tracking.
by
0 like 0 dislike
Priorities are needed, but what is a very interesting question.
Example — there are two projects to do by any one. If one of them has a higher priority (for example platform dependent debt payments/RFP), the question of what to do will not.
Progress is also needed in a similar situation if you have a project with 99% — it is better to deal with it, not sprayed on it and another which has only 5% ready.
by
0 like 0 dislike
We do not use any priority or progress. We have one field — the urgency. Moreover, it is set in the form of numbers from minus infinity to plus infinity — thus, at any given time, you can create a more urgent task
by

Related questions

110,608 questions
257,186 answers
0 comments
23,119 users