categorías corporativa
Libro Electrónico de ámbito Profesional

Scrum Master’s Guide to Project Management

From Agile Team to Agile Enterprise

28
Idioma :  English
This book is an attempt to explain the differences between Scrum Master and Project Manager and help Scrum Masters to take an informed decision.
La suscripción Profesional Plus es gratuita durante los primeros 30 días, posteriormente %cuesta%/mo
Accede a este libro en nuestro eReader. No hay publicidad dentro del libro.
Descripción
Contenido

Still perceived as a promotion from developer to a managerial level, the Scrum Master has dangerously morphed in a Technical Subject Expert that can (and in some organization should) replace Project Managers. Project Manager is the natural progression path for a Scrum Master, but is not as easy as attending a few days Training course.This book is an attempt to explain the differences between Scrum Master and Project Manager and help Scrum Masters aspiring to become Project Managers to take an informed decision.

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
  • Introduction
  1. Master or Manager
    1. What is A Scrum Master?
    2. Should a Scrum Master manage projects?
    3. Can a Scrum Master Manage Projects?
  2. The path to Project Manager
    1. Why Project Management?
    2. What’s the difference?
    3. What do you need to learn?
    4. What do you need to unlearn?
  3. Project Manager vs Scrum Master
    1. Myths and facts
    2. Getting out of Software Development
    3. Getting out of Scrum Team
    4. Getting out of IT
    5. Thinking Business
  4. New Knowledge
    1. Leading with Authority
    2. Responsibility to deliver
    3. Risk management
    4. Stakeholders Management
    5. Governance
    6. Reporting
  5. Use your strengths
    1. Facilitate
    2. Influence
    3. Serve
    4. Leading with Empathy
  6. Conclusion
  • End Notes
Sobre el Autor
Dan

Dan Stelian Roman