Agile principles as a leadership value system in the software development: are we ready to be unleashed?

S. Patil, Srikantha Rao, Preeti S. Patil
{"title":"Agile principles as a leadership value system in the software development: are we ready to be unleashed?","authors":"S. Patil, Srikantha Rao, Preeti S. Patil","doi":"10.1145/1980022.1980188","DOIUrl":null,"url":null,"abstract":"Agile methods generally promote a disciplined project management process that encourages frequent inspection and adaptation, a leadership philosophy that encourages teamwork, self-organization and accountability, a set of engineering best practices that allow for rapid delivery of high-quality software, and a business approach that aligns development with customer needs and company goals. When it is considered Agile Principles as a leadership value System in the Software Development then the question arise that are one is ready to be unleashed? As criticisms include several issues regarding the same like Agile Principles often used as a means to bleed money from customers through lack of defining a deliverable, Lack of structure and necessary documentation, Only works with senior-level developers Incorporates insufficient software design, Requires meetings at frequent intervals at enormous expense to customers, Requires too much cultural change to adopt, Can lead to more difficult contractual negotiations?, Can be very inefficient---if the requirements for one area of code change through various iterations, the same programming may need to be done several times over. Impossible to develop realistic estimates of work effort needed to provide a quote, because at the beginning of the project no one knows the entire scope/requirements and can increase the risk of scope due to the lack of detailed requirements documentation?\n Here it is observed and surveyed the various categories of Projects for different kind of group members to adopt and follow the agile principles. It proposes the strength and weaknesses of all 12 Agile Principles based on Indian scenario.","PeriodicalId":197580,"journal":{"name":"International Conference & Workshop on Emerging Trends in Technology","volume":null,"pages":null},"PeriodicalIF":0.0000,"publicationDate":"2011-02-25","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"10","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"International Conference & Workshop on Emerging Trends in Technology","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/1980022.1980188","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 10

Abstract

Agile methods generally promote a disciplined project management process that encourages frequent inspection and adaptation, a leadership philosophy that encourages teamwork, self-organization and accountability, a set of engineering best practices that allow for rapid delivery of high-quality software, and a business approach that aligns development with customer needs and company goals. When it is considered Agile Principles as a leadership value System in the Software Development then the question arise that are one is ready to be unleashed? As criticisms include several issues regarding the same like Agile Principles often used as a means to bleed money from customers through lack of defining a deliverable, Lack of structure and necessary documentation, Only works with senior-level developers Incorporates insufficient software design, Requires meetings at frequent intervals at enormous expense to customers, Requires too much cultural change to adopt, Can lead to more difficult contractual negotiations?, Can be very inefficient---if the requirements for one area of code change through various iterations, the same programming may need to be done several times over. Impossible to develop realistic estimates of work effort needed to provide a quote, because at the beginning of the project no one knows the entire scope/requirements and can increase the risk of scope due to the lack of detailed requirements documentation? Here it is observed and surveyed the various categories of Projects for different kind of group members to adopt and follow the agile principles. It proposes the strength and weaknesses of all 12 Agile Principles based on Indian scenario.
查看原文
分享 分享
微信好友 朋友圈 QQ好友 复制链接
本刊更多论文
敏捷原则作为软件开发中的领导价值体系:我们准备好被释放了吗?
敏捷方法通常促进一个鼓励频繁检查和调整的有纪律的项目管理过程,一种鼓励团队合作、自组织和责任的领导哲学,一组允许快速交付高质量软件的工程最佳实践,以及一种使开发与客户需求和公司目标保持一致的业务方法。当敏捷原则被认为是软件开发中的领导价值系统时,问题就来了,准备好释放了吗?批评包括几个问题,比如敏捷原则经常被用作从客户那里榨钱的手段,因为缺乏对可交付成果的定义,缺乏结构和必要的文档,只适用于高级开发人员,合并了不充分的软件设计,需要频繁的会议,对客户造成巨大的损失,需要太多的文化变革来采用,可能导致更困难的合同谈判?,可能非常低效——如果一个代码区域的需求通过各种迭代而改变,那么相同的编程可能需要多次重复。不可能对提供报价所需的工作量进行现实的估计,因为在项目开始时没有人知道整个范围/需求,并且由于缺乏详细的需求文档而增加了范围的风险?这里观察和调查了不同类别的项目,以便不同类型的团队成员采用和遵循敏捷原则。它根据印度的情况提出了所有12条敏捷原则的优缺点。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 去求助
来源期刊
自引率
0.00%
发文量
0
期刊最新文献
Receiver based capacity enhancement with cross-layer design approach for IEEE 802.11 ad-hoc networks Heuristics based automatic text summarization of unstructured text Mobi browser with remote video streaming Deblurring of grayscale images using inverse and Wiener filter An optimized approach to voice translation on mobile phones
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
现在去查看 取消
×
提示
确定
0
微信
客服QQ
Book学术公众号 扫码关注我们
反馈
×
意见反馈
请填写您的意见或建议
请填写您的手机或邮箱
已复制链接
已复制链接
快去分享给好友吧!
我知道了
×
扫码分享
扫码分享
Book学术官方微信
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术
文献互助 智能选刊 最新文献 互助须知 联系我们:info@booksci.cn
Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。
Copyright © 2023 Book学术 All rights reserved.
ghs 京公网安备 11010802042870号 京ICP备2023020795号-1