Does size of project and duration add any constraints to use or not to use the Agile methodology?
Example: My project has about 400 developers, complex application and duration of about 4 years. Declan Whelan: Typical Scrum/XP teams should not be greater than 10 or 12 people. So for a program with 400 developers you need to divide and conquer with multiple agile teams. There is a Scrum of Scrums methodology for scaling agile practices up through a hierarchy of Scrum teams. You may also want to look as Crystal Orange from Alistair Cockburn that is targeted for teams of about 40. Also you may want to check out the work of Jutta Eckstein who wrote a book called Agile Software Development in the Large. 2. On an Agile project, how do you explain the value of fixing defects to developers for each iteration instead of solely focusing on development of the next set of new features? Declan Whelan: As the team starts they should have a project charter that sets common goals around code quality and that bar should be set high. I like to use a goal like we will ensure that the number of defect
