Team size and project iteration length

Question

Do you think the iteration length of a project is related to the size of the project team? If so, how? What other key factors do you use to recognize the correct iteration length for different projects?

Answer 1

The length of the iteration is primarily associated with the ability of the team to communicate and finish the working version of the software. More team members equals more communication channels ( Brooks Law ), which is likely to increase your iteration time.

I think that 2-week iterations, whether you deliver to the client or not, are a good goal, because it allows you to check your health very well.

, , 1 1 , .

Answer 2

//. , , . : , , - , , , . , , .

, , ... , .

- , , - - , - .

( , , . , , .)

Answer 3

, ,

, , , , (. ), .

noobs, , , (12 ). , , (4-6 ).

, , , .

Answer 4

, 2- , , , .

2- , , , - - " ".

, , / , , , , .

Answer 5

... , " ".

.

IMO:

Answer 6

There is an attitude regarding how much work can be done, but there are several other key factors, for example, what type of project they are working with, for example, a Windows application, a console application or a web application, as well as how developed the code base is with in terms of size, complexity and style, in comparison with the current team style, and what experience the team has both in terms of the methodology and in the work that they do since inexperience can be expensive in terms of getting all the skills oatsa.