{"title":"Inkubook体验:五个过程的故事","authors":"Eric R. Willeke","doi":"10.1109/AGILE.2009.34","DOIUrl":null,"url":null,"abstract":"Inkubook.com came into existence in March 2008 when an existing software development and marketing organization received a new CEO who immediately tasked the team with building an entirely different product. This paper describes the sources of pain that led to an evolution from the existing Scrum process through four major changes as the team's process shifted to meet the team's goals and management's demands. Then, the ramifications and further changes of the resulting kanban approach are explored.","PeriodicalId":280848,"journal":{"name":"2009 Agile Conference","volume":"81 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2009-08-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"11","resultStr":"{\"title\":\"The Inkubook Experience: A Tale of Five Processes\",\"authors\":\"Eric R. Willeke\",\"doi\":\"10.1109/AGILE.2009.34\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Inkubook.com came into existence in March 2008 when an existing software development and marketing organization received a new CEO who immediately tasked the team with building an entirely different product. This paper describes the sources of pain that led to an evolution from the existing Scrum process through four major changes as the team's process shifted to meet the team's goals and management's demands. Then, the ramifications and further changes of the resulting kanban approach are explored.\",\"PeriodicalId\":280848,\"journal\":{\"name\":\"2009 Agile Conference\",\"volume\":\"81 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2009-08-24\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"11\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2009 Agile Conference\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/AGILE.2009.34\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2009 Agile Conference","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/AGILE.2009.34","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Inkubook.com came into existence in March 2008 when an existing software development and marketing organization received a new CEO who immediately tasked the team with building an entirely different product. This paper describes the sources of pain that led to an evolution from the existing Scrum process through four major changes as the team's process shifted to meet the team's goals and management's demands. Then, the ramifications and further changes of the resulting kanban approach are explored.
求助内容：
应助结果提醒方式：
京公网安备 11010802042870号
