
doi: 10.1109/6294.939976
There is a buzz about the new lightweight software development processes. These processes are certainly capable of creating successful software systems faster. As a software developer, which one should you choose for your project? Indeed, today's software development processes bring interesting dynamics to the projects to which developers apply them. But should process drive the project or should the project determine the process? I examine one characteristic of these processes, scalability, which can help you decide what process is best for you.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 3 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
