{"title":"利用竞争建立一个更强大的团队","authors":"Darin Cummins","doi":"10.1109/ADEVC.2004.25","DOIUrl":null,"url":null,"abstract":"In 2001 we started a new project at our company. Undermanned, short on time, and under the gun to succeed, we knew that we needed a process that would help us stay on track. Unfortunately, once the project got under way, we received a lot of negative feedback from the developers. The process took away from what developers want to do: code. This paper describes how we used competition as a tool to create a more cohesive team that worked better with management and the process.","PeriodicalId":280514,"journal":{"name":"Agile Development Conference","volume":"143 8","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2004-06-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"2","resultStr":"{\"title\":\"Using competition to build a stronger team\",\"authors\":\"Darin Cummins\",\"doi\":\"10.1109/ADEVC.2004.25\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"In 2001 we started a new project at our company. Undermanned, short on time, and under the gun to succeed, we knew that we needed a process that would help us stay on track. Unfortunately, once the project got under way, we received a lot of negative feedback from the developers. The process took away from what developers want to do: code. This paper describes how we used competition as a tool to create a more cohesive team that worked better with management and the process.\",\"PeriodicalId\":280514,\"journal\":{\"name\":\"Agile Development Conference\",\"volume\":\"143 8\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2004-06-22\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"2\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Agile Development Conference\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ADEVC.2004.25\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Agile Development Conference","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ADEVC.2004.25","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
In 2001 we started a new project at our company. Undermanned, short on time, and under the gun to succeed, we knew that we needed a process that would help us stay on track. Unfortunately, once the project got under way, we received a lot of negative feedback from the developers. The process took away from what developers want to do: code. This paper describes how we used competition as a tool to create a more cohesive team that worked better with management and the process.