11
votes
Accepted
Shared Development Tasks for Agile User Stories
I shouldn't write a "Generate UI and DB" Task for each User Story. That's too much redundancy. But I don't know how to write a "Generate UI and DB" task that must be completed before any of the User ...
- 823
11
votes
Accepted
Is it agile friendly to propose equal distribution of dev tasks at the beginning of the sprint?
To answer your direct question: no, this would not be "agile friendly". Forcing a distribution of tasks to developers to meet a goal which is not delivering value to the customer is almost ...
- 25.6k
7
votes
How do I break down a feature that has complex dependencies?
I see two possible options.
First, don't break down the item. In this case, the work item (the story, ticket, whatever) represents the minimum valuable delivery of the work and can be estimated by ...
- 84.2k
7
votes
Accepted
Best algorithm to sort tasks by priorities by a human
Bucket Sort
But I'm getting ahead of myself.
Consider the use cases of listing and sorting tasks like this.
A dev completed a task and needs to know what to work on next
A Project Manager needs to ...
- 1,073
4
votes
In which order perform tasks from big backlog
One of the most important things to do with a backlog is groom it. You should go through the backlog and prioritize the tasks.
It can seem overwhelming when the backlog grows faster then it gets ...
- 115k
3
votes
In which order perform tasks from big backlog
This question seems to address tasks as if it was for the classical elevator optimization problem:
LIFO has the risk of “starving”: some tasks will wait forever for resources and will never get done. ...
- 80.6k
3
votes
Best algorithm to sort tasks by priorities by a human
For 300 tasks you'd need to ask thousands of questions. No one is going to do that, and even if they did the results wouldn't be very useful.
For situations like this I'd suggest you stick with the ...
- 202
3
votes
How do I break down a feature that has complex dependencies?
I'm going to lean towards breaking it down.
Yes what they asked for is all of it and they might not find any final use for the parts. I like to break it down anyway. Here why:
At the end of every ...
- 115k
3
votes
What are the disadvantages of performing task breakdown before story estimation?
bear in mind that story estimation is exactly what it is, just an estimate therefore it doesn't have to be 100% accurate. Defining all tasks for all stories before estimating would take forever. ...
- 51
2
votes
Shared Development Tasks for Agile User Stories
Given that you are entering each sprint with a prioritised list of stories, and each story is broken down into separate technical tasks, all the developers should be working on tasks for the highest ...
- 281
1
vote
Best algorithm to sort tasks by priorities by a human
In practice you wouldn’t sort 300 tasks just by priority.
Tasks are related or unrelated. It is usually more efficient to handle related than unrelated tasks. So you would want to perform related ...
- 47.5k
1
vote
Best algorithm to sort tasks by priorities by a human
The algorithm should reduce the number of comparisons, but also the access time: when the user discovers a task, it takes time for him to read it and recover the memory he has about that task. So when ...
1
vote
Best algorithm to sort tasks by priorities by a human
1 What is the best algorithm that reduce the number of comparison needed to sort all tasks ?
Strictly speaking, merge sort is hard to beat.
2 Do you have a better strategy to propose (or way of ...
- 115k
1
vote
What are the disadvantages of performing task breakdown before story estimation?
I would say that sequencing the breakdown before estimation defeats the main advantages of doing both estimation and breakdown.
Estimation is a coarse assessment of complexity that helps you decide a)...
Only top scored, non community-wiki answers of a minimum length are eligible