Advertisement

Mastering Agility

  • Sergey V. ZykovEmail author
  • Amitoj Singh
Chapter
  • 32 Downloads
Part of the Smart Innovation, Systems and Technologies book series (SIST, volume 175)

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.

References

  1. 1.
    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.
  2. 2.
    Cockburn, A. (2006). Agile software development: The cooperative game. London: Pearson Education.Google Scholar
  3. 3.
    Leffingwell, D. (2007). Scaling software agility: Best practices for large enterprises. London: Pearson Education.Google Scholar
  4. 4.
    DeMarco, T., & Lister, T. (2013). Waltzing with bears: Managing risk on software projects. Boston, MA: Addison-Wesley.Google Scholar
  5. 5.
    Layton, M. C., & Ostermiller, S. J. (2017). Agile project management for dummies. New York, NY: Wiley.Google Scholar
  6. 6.
    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.
  7. 7.
    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.
  8. 8.
    Cockburn, A. (2017). Origin of the term information radiator. Available https://staging.cockburn.us/origin-of-the-term-information-radiator/. Accessed 5.11.2018.
  9. 9.
    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.
  10. 10.
    The Standish Group Chaos Chronicles Version II, 2001.Google Scholar
  11. 11.
    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.

Copyright information

© Springer Nature Switzerland AG 2020

Authors and Affiliations

  1. 1.Higher School of EconomicsNational Research UniversityMoscowRussia
  2. 2.Maharaja Ranjit Singh Punjab Technical UniversityBathindaIndia

Personalised recommendations