2013 Agile Conference最新文献

筛选
英文 中文
How Writers Can Thrive in Agile 作者如何在敏捷中茁壮成长
2013 Agile Conference Pub Date : 2013-08-05 DOI: 10.1109/AGILE.2013.19
Gavin Austin
{"title":"How Writers Can Thrive in Agile","authors":"Gavin Austin","doi":"10.1109/AGILE.2013.19","DOIUrl":"https://doi.org/10.1109/AGILE.2013.19","url":null,"abstract":"This presentation shows how the Documentation and User Assistance team at salesforce.com uses several strategies and best practices to help its technical writers work effectively and thrive in an Agile development environment. Combined, these strategies and practices have helped the writers at salesforce.com move past a number of frustrations typically experienced by writers working in Agile environments at other software companies.","PeriodicalId":248287,"journal":{"name":"2013 Agile Conference","volume":"128 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-08-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128109023","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 1
Continuous Delivery? Easy! Just Change Everything (Well, Maybe It Is Not That Easy) 持续交付?简单!改变一切(好吧,也许没那么容易)
2013 Agile Conference Pub Date : 2013-08-05 DOI: 10.1109/AGILE.2013.17
S. Neely, S. Stolt
{"title":"Continuous Delivery? Easy! Just Change Everything (Well, Maybe It Is Not That Easy)","authors":"S. Neely, S. Stolt","doi":"10.1109/AGILE.2013.17","DOIUrl":"https://doi.org/10.1109/AGILE.2013.17","url":null,"abstract":"Rally Software transitioned from shipping code every eight-weeks, with time-boxed Scrum sprints, to a model of continuous delivery with Kanban. The team encountered complex challenges with their build systems, automated test suites, customer enablement, and internal communication. But there was light at the end of the tunnel - greater control and flexibility over feature releases, incremental delivery of value, lower risks, fewer defects, easier on-boarding of new developers, less off-hours work, and a considerable up tick in confidence. This experience report describes the journey to continuous delivery with the aim that others can learn from our mistakes and get their teams deploying more frequently. We will describe and contrast this transition from the business (product management) and engineering perspectives.","PeriodicalId":248287,"journal":{"name":"2013 Agile Conference","volume":"232 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-08-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133550960","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 123
Transforming a Public Sector Company: From Stone Age to Agile 公共部门公司转型:从石器时代到敏捷
2013 Agile Conference Pub Date : 2013-08-05 DOI: 10.1109/AGILE.2013.30
Ardita Karaj, Jason Little
{"title":"Transforming a Public Sector Company: From Stone Age to Agile","authors":"Ardita Karaj, Jason Little","doi":"10.1109/AGILE.2013.30","DOIUrl":"https://doi.org/10.1109/AGILE.2013.30","url":null,"abstract":"On June 7, 2012, our CIO walked our Kanban board with the management team. When he saw a low priority feature being worked on, he took it off the board and told them to stop. This was the first time he'd had an organization with the transparency and flexibility that gave him this kind of control. We provided the opportunity to empower our executives as much as our workers.","PeriodicalId":248287,"journal":{"name":"2013 Agile Conference","volume":"41 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-08-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131687365","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 4
Refactoring as a Lifeline: Lessons Learned from Refactoring 作为生命线的重构:从重构中学到的教训
2013 Agile Conference Pub Date : 2013-08-05 DOI: 10.1109/AGILE.2013.18
Amr Noaman Abdel-Hamid
{"title":"Refactoring as a Lifeline: Lessons Learned from Refactoring","authors":"Amr Noaman Abdel-Hamid","doi":"10.1109/AGILE.2013.18","DOIUrl":"https://doi.org/10.1109/AGILE.2013.18","url":null,"abstract":"Refactoring legacy code can be a major impediment for teams transforming to agile due to the high cost of manual regression testing of frequent (typically 2-week) releases. Also, attempts to implement automated tests may involve technical and cost issues. In this report we present a new and more systematic approach to refactoring we have found to be successful for refactoring legacy code that has few (if any) automated tests. This report describes two experiences: one with 3 teams applying a basic and traditional refactoring approach, and another with 2 teams applying the new approach. This new approach helped achieve better results in covering code with tests, involved senior management to retain their support, and achieved better and more sustainable pace of development powered by continuous refactoring techniques.","PeriodicalId":248287,"journal":{"name":"2013 Agile Conference","volume":"52 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-08-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115785833","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 3
Big Visible Testing 大型可见测试
2013 Agile Conference Pub Date : 2013-08-05 DOI: 10.1109/AGILE.2013.15
Claire Moss
{"title":"Big Visible Testing","authors":"Claire Moss","doi":"10.1109/AGILE.2013.15","DOIUrl":"https://doi.org/10.1109/AGILE.2013.15","url":null,"abstract":"Software testing is a key part of software development, so it's important that the testers be as effective as possible. Especially in fast-feedback agile teams, software testers must respond to their teammates' need for information with readily available, easy-to-understand testing materials. The novel twist of turning user experience personas inward to focus on the product team members provides deep insights into both what decisions team members need to make and how to present testing information to them to support those decisions. Having established personas as the context for the testing work, testers are poised to spring into action, planning, estimating, and executing both exploratory testing and user-facing automation. Testers then surface the results of this work to the product team in a way that helps them to address concerns in a timely fashion. Big visible charts display testing for co-located teams in a particularly effective form. Testers experiment with a variety of big visible representations throughout the life of the team, retaining these charts only as long as they provide value for decision-making and moving on to other forms as the team learns more about satisfying their information-gathering needs through testing. User personas produce a fresh perspective on product team members to help testers to focus on the value big visible testing artifacts provide to the individuals on a software development team.","PeriodicalId":248287,"journal":{"name":"2013 Agile Conference","volume":"36 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-08-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127701902","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 4
How We Successfully Adapted Agile for a Research-Heavy Engineering Software Team 我们如何成功地将敏捷应用于研究型工程软件团队
2013 Agile Conference Pub Date : 2013-08-05 DOI: 10.1109/AGILE.2013.20
A. Lorber, K. Mish
{"title":"How We Successfully Adapted Agile for a Research-Heavy Engineering Software Team","authors":"A. Lorber, K. Mish","doi":"10.1109/AGILE.2013.20","DOIUrl":"https://doi.org/10.1109/AGILE.2013.20","url":null,"abstract":"In our development team at Sandia National Laboratories we have honed our Scrum processes to where we continually deliver high-performance engineering analysis software to our customers. We deliver despite non-ideal circumstances, including development work that can be categorized as exploratory research, regular use of part-time developers, team size that varies widely among Sprints, highly specialized technical skill sets and a broad range of deliverables. We believe our methodologies can be applied to many research-oriented environments such as those found in government laboratories, academic institutions and corporate research facilities. Our goal is to increase the adoption of Lean/Agile project management in these environments by sharing our experiences with those research-oriented development teams who are considering using Lean/Agile, or have started and are encountering problems. In this paper we discuss how we create and prioritize our product backlog, write our user stories, calculate our capacity, plan our Sprints, report our results and communicate our progress to customers. By providing guidance and evidence of success in these areas we hope to overcome real and perceived obstacles that may limit the adoption of Lean/Agile techniques in research-oriented development environments.","PeriodicalId":248287,"journal":{"name":"2013 Agile Conference","volume":"12 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-08-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128557303","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 6
Organizational Learning with Open Space 开放空间的组织学习
2013 Agile Conference Pub Date : 2013-08-05 DOI: 10.1109/AGILE.2013.33
Dan Mezick
{"title":"Organizational Learning with Open Space","authors":"Dan Mezick","doi":"10.1109/AGILE.2013.33","DOIUrl":"https://doi.org/10.1109/AGILE.2013.33","url":null,"abstract":"A successful Agile adoption requires ongoing engagement from everyone involved, including team members, managers and executive leadership. Social systems are complex adaptive systems that generate complicated and non-linear feedback. Engagement is an emergent property of social systems, and essential for effective and lasting Agile adoptions. This property does decay quickly, often resulting in poor results in Agile adoption efforts. This paper introduces Open Space as a tool that functions as a \"event\" with a \"good game\" structure for creating rapid, effective and lasting Agile adoptions. Actual experience using Open Space in Agile adoptions is discussed, including lessons learned. NOTE: It is assumed the reader is already familiar with the Open Space meeting format; if not, you may examine http://en.wikipedia.org/wiki/Open-space_technology for details and additional links.","PeriodicalId":248287,"journal":{"name":"2013 Agile Conference","volume":"2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-08-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121720833","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 0
Black Swan Farming Using Cost of Delay: Discover, Nurture and Speed Up Delivery of Value 使用延迟成本的黑天鹅养殖:发现、培育和加速价值交付
2013 Agile Conference Pub Date : 2013-08-05 DOI: 10.1109/AGILE.2013.16
J. J. Arnold, O. Yuce
{"title":"Black Swan Farming Using Cost of Delay: Discover, Nurture and Speed Up Delivery of Value","authors":"J. J. Arnold, O. Yuce","doi":"10.1109/AGILE.2013.16","DOIUrl":"https://doi.org/10.1109/AGILE.2013.16","url":null,"abstract":"Improving prioritization has become a tired concept in most IT departments, and yet it has the potential to change the conversation from one of cutting cost, to delivering valuable solutions as quick as the business needs it. This paper examines how Maersk Line applied an economic framework across a $100 million portfolio to quickly discover, nurture and speed up the delivery of value.","PeriodicalId":248287,"journal":{"name":"2013 Agile Conference","volume":"3 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-08-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130589771","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 2
Analyzing Effectiveness of Workshops for Learning Agile Development Principles 分析学习敏捷开发原则的研讨会的有效性
2013 Agile Conference Pub Date : 2013-08-05 DOI: 10.1109/AGILE.2013.12
Shota Suzuki, Ryushi Shiohama, Masashi Kadoya, Kazunori Sakamoto, H. Washizaki, Y. Fukazawa
{"title":"Analyzing Effectiveness of Workshops for Learning Agile Development Principles","authors":"Shota Suzuki, Ryushi Shiohama, Masashi Kadoya, Kazunori Sakamoto, H. Washizaki, Y. Fukazawa","doi":"10.1109/AGILE.2013.12","DOIUrl":"https://doi.org/10.1109/AGILE.2013.12","url":null,"abstract":"Workshops are sometimes known as effective ways to learn the human and social factors of software engineering. However, their effectiveness in learning agile development principles in particular has not yet been determined, despite the fact that numerous agile development workshops have been held over the years. In this paper, we analyze the effectiveness of agile development workshops through an experiment, and show that one of representative workshops is indeed effective at learning agile principles. Self-study is another commonly used method to learn something new. Therefore, we compare the effectiveness of workshops with that of self-study to better illustrate the effectiveness of agile development workshops. In our experiment, we examine 7 workshop subjects and 8 self-study subjects, and compare their scores on the agile mind check, which is a method used to measure their degree of mastery of agile principles. As a result, we demonstrate the effectiveness of agile development workshops, especially those that simulate actual experiences. We also show that one of workshops is more effective than self-study regarding the agile mind check score.","PeriodicalId":248287,"journal":{"name":"2013 Agile Conference","volume":"18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-08-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134211246","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 2
"Scrum Code Camps" “Scrum代码营”
2013 Agile Conference Pub Date : 2013-08-05 DOI: 10.1109/AGILE.2013.29
Lene Pries-Heje, J. Pries-Heje, Bent Dalgaard
{"title":"\"Scrum Code Camps\"","authors":"Lene Pries-Heje, J. Pries-Heje, Bent Dalgaard","doi":"10.1109/AGILE.2013.29","DOIUrl":"https://doi.org/10.1109/AGILE.2013.29","url":null,"abstract":"A classic way to choose a supplier is through a bidding process where tenders from competing companies are evaluated in relation to the customer's requirements. If the customer wants to hire an agile software developing team instead of buying a software product, a new approach for comparing tenders is required. In this paper we present the design of such a new approach, the Scrum Code Camp, which can be used to assess agile team capability in a transparent and consistent way. A design science research approach is used to analyze properties of two instances of the Scrum Code Camp where seven agile teams were evaluated.","PeriodicalId":248287,"journal":{"name":"2013 Agile Conference","volume":"196 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-08-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123226321","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 0
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
相关产品
×
本文献相关产品
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:604180095
Book学术官方微信