Scrum: task dependency and task for architecture design [duplicate]

This question already has an answer here: Closed 11 years ago.

Possible Duplicate:

Scrum: task dependency and task for architecture design

I have some Scrum problems:

1. Task dependency: Most books 开发者_如何转开发I read seem like treating the tasks as independent from each other. One programmer tasks doesn't affect the other's one, thus can be run in parallel. How to deal with task which is depend on another one?

2. Task is based on story/feature/function: There are a lot of ground works needed to set up up the project, e.g. design the architecture, learning the architecture, framework etc. And most functional tasks are depend on this architecture work to be completed. That's Q1 problem. At this time, there will be only one programmer working on the architecture design, what about the rest of the team members? What should they do?

Please tell me how to tackle this problem. Thanks

---

For some tasks you must take dependencies into account.

You can complete some tasks independent of other tasks of others if you base completion of the task on the passing of unit tests.

When you are manning a project start with the architecture team, then a small team that builds a vertical to prove the architecture. When that is complete you add members to the team.