Advertisement

Agility at Scale

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

Abstract

Agile methodologies are being used all through the lifecycle of the software development, not simply the development phase, and regularly in complex situations that require high than the small and collocated team. In the present turbulent markets, where organizations are irately fighting from new businesses and additional rebellious opponent, the possibility of a quick moving and adaptation is very significant. Significant changes in the business have been seen by the organization that scaled up agile implementation. In organizations that extended the agile, in their organizations outlines the support procedures and routine activities largely look same as they did before, however, with less control hierarchies and wider range of control as a leader figure out how to trust and enable individuals. Big organizations mostly deal with more complex and bigger problems than that medium- or small-scale enterprises. Large companies often have many subcontracting companies and have a large number of workforces, different subsidies, and strong culture and rule for doing things. For transforming from traditional to agile, it is always advised to learn lessons from companies that have already transform themselves from traditional to agile methodologies. Agile transformation may take time to get on right path, but by understanding challenges and risks they can reducer to get stuck midway or even getting fail.

References

  1. 1.
    Subramaniam, V., & Hunt, A. (2006). Practices of an agile developer: Working in the real world. Pragmatic Bookshelf.Google Scholar
  2. 2.
    Embracing Agile. (2016). HBR. Available https://hbr.org/2016/05/embracing-agile. Accessed 12.11.2018.
  3. 3.
    HR Goes Agile. (2016). HBR, March–April 2018. Available https://hbr.org/2018/03/the-new-rules-of-talent-management. Accessed 2.11.2018.
  4. 4.
    Shore, J. (2007). The art of agile development: Pragmatic guide to agile software development. Newton, MA: O’Reilly Media, Inc. Google Scholar
  5. 5.
    One Bank’s Agile Team Experiment. (2018). HBR. Available https://hbr.org/2018/03/the-new-rules-of-talent-management#one-banks-agile-team-experiment. Accessed 02.11.2018.
  6. 6.
    Do you need an Architect in a Software Company? Available https://blog.rapid7.com/2015/09/16/do-you-need-an-architect-in-a-software-company/. Accessed 29.11.2019.
  7. 7.
    Layton, M. C., & Ostermiller, S. J. (2017). Agile project management for dummies. New York, NY: Wiley.Google Scholar
  8. 8.
    Leffingwell, D. (2007). Scaling software agility: Best practices for large enterprises. London: Pearson Education.Google Scholar
  9. 9.
    IT Project Success Rates Survey Results. (2007). Available http://www.ambysoft.com/surveys/success2007.html. Accessed 10.11.2018.
  10. 10.
  11. 11.
    Highsmith, J. R. (2009). Agile project management: Creating innovative products. London: Pearson Education.Google Scholar

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