Matches in SemOpenAlex for { <https://semopenalex.org/work/W1527720785> ?p ?o ?g. }
Showing items 1 to 73 of
73
with 100 items per page.
- W1527720785 endingPage "280" @default.
- W1527720785 startingPage "279" @default.
- W1527720785 abstract "One saying is that, if you have a hundred people on a development team, get rid of at least eighty of them and keep the top twenty (or less). As a result the chances for project success will raise significantly. But maybe you don’t have even twenty top ones and/or the company just have these hundred people sitting around. It seems like the only places where large projects with huge teams seem to really work are projects where everything is formalized, the requirements are fixed and, most importantly, they don’t change over time. A detailed plan can be set up and every successive action will stupidly follow the plan. Example are defense projects or projects with a similar structure, such as in airlines or nuclear power plants. We as software-engineers tend to question software engineering in the large not only because most of the agile processes claim to work only for small teams, also because most of the failed projects are really large ones. (Well, maybe nobody talks about failed small projects.) However, there are more than enough projects that are large in some sense. So, the question arises, how to use aspects of agile software development in large projects. We don’t want to focus on every aspect of agile processes, but on those who we encountered to be mainly different in large projects. The differences might be that some things have to be implemented differently, because at a specific size of the project things don’t work out the normal way anymore. Other differences are based on problems, which pop up especially in large teams, or rather which won’t be problems at all in small teams. This tutorial is based on our experience coordinating — so far successfully — a large (currently 160 people) project. Although we are still in the process of learning we would like to share our experiences about how agile processes can serve large projects. And besides — chances are high, that at the time XP Agile Universe 2002 is held, we have made even more valuable experiences." @default.
- W1527720785 created "2016-06-24" @default.
- W1527720785 creator A5024622297 @default.
- W1527720785 date "2002-01-01" @default.
- W1527720785 modified "2023-10-17" @default.
- W1527720785 title "Scaling Agile Processes: Agile Software Development in Large Projects" @default.
- W1527720785 doi "https://doi.org/10.1007/3-540-45672-4_44" @default.
- W1527720785 hasPublicationYear "2002" @default.
- W1527720785 type Work @default.
- W1527720785 sameAs 1527720785 @default.
- W1527720785 citedByCount "3" @default.
- W1527720785 countsByYear W15277207852012 @default.
- W1527720785 crossrefType "book-chapter" @default.
- W1527720785 hasAuthorship W1527720785A5024622297 @default.
- W1527720785 hasConcept C110354214 @default.
- W1527720785 hasConcept C115903868 @default.
- W1527720785 hasConcept C127413603 @default.
- W1527720785 hasConcept C14185376 @default.
- W1527720785 hasConcept C15952604 @default.
- W1527720785 hasConcept C166957645 @default.
- W1527720785 hasConcept C177264268 @default.
- W1527720785 hasConcept C180152950 @default.
- W1527720785 hasConcept C18762648 @default.
- W1527720785 hasConcept C195094911 @default.
- W1527720785 hasConcept C199360897 @default.
- W1527720785 hasConcept C201995342 @default.
- W1527720785 hasConcept C2776505523 @default.
- W1527720785 hasConcept C2777904410 @default.
- W1527720785 hasConcept C36914074 @default.
- W1527720785 hasConcept C38652104 @default.
- W1527720785 hasConcept C41008148 @default.
- W1527720785 hasConcept C529173508 @default.
- W1527720785 hasConcept C78519656 @default.
- W1527720785 hasConcept C95457728 @default.
- W1527720785 hasConceptScore W1527720785C110354214 @default.
- W1527720785 hasConceptScore W1527720785C115903868 @default.
- W1527720785 hasConceptScore W1527720785C127413603 @default.
- W1527720785 hasConceptScore W1527720785C14185376 @default.
- W1527720785 hasConceptScore W1527720785C15952604 @default.
- W1527720785 hasConceptScore W1527720785C166957645 @default.
- W1527720785 hasConceptScore W1527720785C177264268 @default.
- W1527720785 hasConceptScore W1527720785C180152950 @default.
- W1527720785 hasConceptScore W1527720785C18762648 @default.
- W1527720785 hasConceptScore W1527720785C195094911 @default.
- W1527720785 hasConceptScore W1527720785C199360897 @default.
- W1527720785 hasConceptScore W1527720785C201995342 @default.
- W1527720785 hasConceptScore W1527720785C2776505523 @default.
- W1527720785 hasConceptScore W1527720785C2777904410 @default.
- W1527720785 hasConceptScore W1527720785C36914074 @default.
- W1527720785 hasConceptScore W1527720785C38652104 @default.
- W1527720785 hasConceptScore W1527720785C41008148 @default.
- W1527720785 hasConceptScore W1527720785C529173508 @default.
- W1527720785 hasConceptScore W1527720785C78519656 @default.
- W1527720785 hasConceptScore W1527720785C95457728 @default.
- W1527720785 hasLocation W15277207851 @default.
- W1527720785 hasOpenAccess W1527720785 @default.
- W1527720785 hasPrimaryLocation W15277207851 @default.
- W1527720785 hasRelatedWork W1858964979 @default.
- W1527720785 hasRelatedWork W2119651961 @default.
- W1527720785 hasRelatedWork W2145240044 @default.
- W1527720785 hasRelatedWork W2361851620 @default.
- W1527720785 hasRelatedWork W2538589471 @default.
- W1527720785 hasRelatedWork W2557370069 @default.
- W1527720785 hasRelatedWork W2622119898 @default.
- W1527720785 hasRelatedWork W2797778376 @default.
- W1527720785 hasRelatedWork W2993771368 @default.
- W1527720785 hasRelatedWork W3148242549 @default.
- W1527720785 isParatext "false" @default.
- W1527720785 isRetracted "false" @default.
- W1527720785 magId "1527720785" @default.
- W1527720785 workType "book-chapter" @default.