Abstract
It is always better to modify the process if there is a need to do so. Rules are defined for a particular purpose. However, rules are not perfectly applied in every situation. It is necessary to break the rules if traditional conventions thwart your projects to succeed. The courage to adapt to changes is not explicitly defined in any agile practice but it is a facet of agile courage value. The requirement of agility is its adaptability and a learning process. Excess of anything is just wastage of recourses. If the task is certain to fall flat, one needs to realize that as quickly as possible. The project in which investment has not proved any value to the customer and is waste in the form of time, cost, and opportunity. Find out the approaches and its corresponding data that will enlighten regarding the project’s probability of failure. If you can anticipate in advance the time duration for which the project will take to complete, recognize the risk that may or may not occur and if you can fully eliminate all the surprises that may come during software development lifecycle, this means you do not require agility, any other methodology can work efficiently. But in case you do not know, agility is your answer.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
References
Adanza, F. (2015). Best practices for scaling software agility in large enterprises. Available https://www.getzephyr.com/insights/best-practices-scaling-software-agility-large-enterprises. Accessed 11.11.2018.
Cockburn, A. (2006). Agile software development: The cooperative game. London: Pearson Education.
Leffingwell, D. (2007). Scaling software agility: Best practices for large enterprises. London: Pearson Education.
DeMarco, T., & Lister, T. (2013). Waltzing with bears: Managing risk on software projects. Boston, MA: Addison-Wesley.
Layton, M. C., & Ostermiller, S. J. (2017). Agile project management for dummies. New York, NY: Wiley.
Rigby, D. K., Sutherland, J., & Noble, A. (2018). Agile at scale, Harvard business review. Available https://hbr.org/2018/05/agile-at-scale. Accessed 20.02.2019.
Barton, D., Carey, D., & Charan, R. (2018). One bank’s agile team experiment. HBR. Available https://hbr.org/2018/03/the-new-rules-of-talent-management#one-banks-agile-team-experiment. Accessed 01.01.2019.
Cockburn, A. (2017). Origin of the term information radiator. Available https://staging.cockburn.us/origin-of-the-term-information-radiator/. Accessed 5.11.2018.
Rigby, D. K., Sutherland, J., & Hirotaka, T. (2016). Embracing agile—Harvard business review. Available https://hbr.org/2016/05/embracing-agile. Accessed 22.12.2018.
The Standish Group Chaos Chronicles Version II, 2001.
Cappelli, P., & Tavis, A. (2018). HR goes agile, HBR, March–April 2018. Available https://hbr.org/2018/03/the-new-rules-of-talent-management. Accessed 21.12.2018.
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
Copyright information
© 2020 Springer Nature Switzerland AG
About this chapter
Cite this chapter
Zykov, S., Singh, A. (2020). Mastering Agility. In: Agile Enterprise Engineering: Smart Application of Human Factors. Smart Innovation, Systems and Technologies, vol 175. Springer, Cham. https://doi.org/10.1007/978-3-030-40989-0_5
Download citation
DOI: https://doi.org/10.1007/978-3-030-40989-0_5
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-030-40988-3
Online ISBN: 978-3-030-40989-0
eBook Packages: Intelligent Technologies and RoboticsIntelligent Technologies and Robotics (R0)