Management 3.0 Quotes
Management 3.0: Leading Agile Developers, Developing Agile Leaders
by
Jurgen Appelo2,842 ratings, 4.15 average rating, 154 reviews
Open Preview
Management 3.0 Quotes
Showing 1-30 of 57
“Motivation is a fine example of social complexity. It is nonlinear and sometimes unpredictable. It cannot be defined or modeled with a single diagram.”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“Agile recognizes that people are unique individuals instead of replaceable resources and that their highest value is not in their heads but in their interactions and collaboration. Agile”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“The 21st century is the age of complexity. It is the century where managers realize that, to manage social complexity, they need to understand how things grow. Not how they are built.”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“Systems thinking is similar to system dynamics, though the latter typically uses actual simulations and calculations in an attempt to analyze the impact of alternative policies objectively. Systems”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“assuming that software teams are systems, can we actually call them complex adaptive systems? Can we compare team members to children playing in bath tubs?”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“Unfortunately, Don Norman used the term simplification both for linearization of behavior (horizontally) and simplification of structure (vertically). And”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“Ordered = Fully predictable • Complex = Somewhat predictable (but with many surprises) • Chaotic = Very unpredictable”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“• Simple = Easily understandable • Complicated = Very hard to understand”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“The goal of visual thinking is to make the complex understandable by making it visible, not by making it simple.”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“Simplification is the act of making the structure better understandable (moving it from top to bottom in my model). • Linearization is the act of making behavior better predictable (moving it from right to left in the model).”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“Chaos theory taught us that even the smallest changes in a dynamic system can have tremendous consequences at a later time.”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“general systems theory3 (sometimes simply called systems theory). Their studies were based on the idea that most phenomena in the universe can be viewed as webs of relationships among elements. And”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“internal conflict is a natural aspect of complex systems and a prerequisite for creativity and innovation. It”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“Even though Agile suggests a people-over-process paradigm, this doesn’t mean that process is unimportant.”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“One of the primary reasons the Agile Manifesto was crafted was to address the need to respond to change. The”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“Software is produced in short time frames, often in time boxes or “sprints,” and delivered in many incremental releases, where each release is a potentially shippable product.”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“In an Agile context, tools are meant to strengthen motivation, communication, and collaboration in a team.”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“Agile software development needs teams to be motivated. But repetitive tasks are boring, not motivating, so they should be automated. Many”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“For successful products a focus on quality is crucial,”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“Simplicity is the key to good design of each feature, and after their implementation the usefulness of features is immediately verified by the customer.”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“grew the process while building the product.”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“I had no plan, only a list of features. I”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“I was my own critical customer.”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“• I built my product passionately.”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“Make sure you’re not oversimplifying the complexity of the problems and that you’re not addressing the wrong cause.”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“Complexity science teaches us that applying linear thinking to complex problems can lead to painful mistakes.”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“we are all managers of the environment around us.”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“manage teams knowing that systems are usually complex, not linear, and how to focus on adaptability, not predictability.”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“social complexity: the study of social groups as complex systems.”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
“Only by repeatedly accepting failure and subsequently purging its causes from the system you can steadily grow a software project and allow it to perform successfully.”
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
― Management 3.0: Leading Agile Developers, Developing Agile Leaders
