Categories Pricing Corporate
home.libro.professionale_ebook

Agile Leader’s Guide to Crisis

Lessons Learned from COVID

34
Lingua:  English
Agile adoption is a disruptive change, similar to a crisis. Some of the lessons learned during the pandemic can be applied to implement Agile in large organizations.
Abbonamento Professional Plus gratuito per i primi 30 giorni poi $8.99 /mese
Non ci sono pubblicità nel libro
Descrizione
Contenuto

Most Agile frameworks are inspired by the Manifesto for Agile Software Development. They have been developed based on practical experience with small software projects. Although most of the values and principles are valid at a larger scale, organizational transformation requires senior leadership support when rapid and hard decisions are made and acting on feedback if the outcome is not as intended. This book is a Project Manager’s analysis of a few lessons learned during the COVID crisis, lessons that can be applied to increase the likelihood of Agile adoption in large organizations.

About the Author

Dan is an experienced Project Manager with over 35 years commercial experience. He started his career as a specialist in Computer Aided Design and Manufacturing (CAD/CAM) following his involvement in research during university studies. After a successful career in research when he also published articles and books on various topics, mainly Computer Aided Design & Manufacturing and Computer Graphics he managed large development teams and then moved to Project Management and is now specialized in Business Transformations Projects.

  • About the author
  • Preface
  1. Crises are unavoidable
    1. Crisis is marked by disruptive change
    2. Crisis needs leaders
    3. Change can’t be predicted
    4. Change can’t be ignored
  2. Agile mindset is a necessity
    1. Agile didn’t start in the 21st Century
    2. Agile is not a methodology
  3. Agile exploits risk
    1. Change means risk
    2. Risk is not always a bad thing
  4. Agile starts from the top
    1. Agile is not limited to software or product development
    2. Agile needs a new culture
  5. Agile’s focus is the outcome
    1. Outcome vs Output
    2. Agile accepts waste
  6. Agile needs knowledge
    1. Empiricism is not enough
    2. Certification vs Qualification
  7. Agile needs planning
    1. Agile is not chaos
    2. Agile needs more planning than predictive approaches
  8. Context is important
    1. Individuals and groups have specific needs
    2. Agile can’t be prescriptive
  9. Agile is not driven by Technology
  • List of Figures
  • References
home.libro.su_autore
Dan

Dan Stelian Roman