Categories Pricing Corporate
Professional eBook

Agile and the Einstein Paradox

Is Imagination More Important Than Knowledge?

Dan Stelian Roman
0 Recensioner
32
Language:  English
This book is a view of the relationship between knowledge and imagination in Agile. Although doing things differently is important, without knowledge, there is a risk to repeat old mistakes.
Professional Plus subscription free for the first 30 days, then $8.99/mo
Få åtkomst till boken på vår läsplatta. Ingen reklam i boken.
Description
Content

Most Agile frameworks were created before or after the Manifesto for Agile Software Development. These frameworks were focused on continuous change. Presenting Agile as a completely new way of working, aimed at continuously delivering products that make customers happy.
The challenge of balancing knowledge and imagination is that knowledge is seen as an inhibitor for Agility. One of the consequences of this misconception is that practitioners try to ‘reinvent the wheel”. Bringing practices, especially Lean, that were successfully used in manufacturing as a wrong way to scale Agile.

About the Author

Dan is an experienced Project Manager with 40 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. As a successful researcher, he has published several academic books and articles on topics ranging from CAD/CAM to Computer Graphics. Professionally, Dan has managed large development teams and has transitioned into Project Management, becoming a specialist in Business Transformations Projects.

  • About the author
  1. Introduction
    1. Einstein’s paradox
    2. Imagination
    3. Knowledge
    4. Imagination vs Knowledge?
  2. The Agile Enterprise
    1. The adaptive enterprise (1995)
    2. Rediscovering the wheel
  3. Agile, Imagination and Knowledge
    1. Change is inevitable, therefore Agile is inevitable
    2. Agile means different
    3. Agile transformations should have goal
    4. Agile should solve a problem
  4. Table of Figures
  5. References