This document contains quotes from various authors, business leaders, and public figures on topics related to iterative development, planning, change, mistakes, customer focus, and agility. In total, there are over 50 short quotes presented without additional context or attribution.
Execution is one of the most overlooked elements of business. Strategy, finances, and market opportunities seem to get a lot more attention. In my own experience, getting an A+ on execution will beat out the other companies who have A+'s in the more traditional areas.
The document provides a collection of thoughts and ideas from various sources organized into sections on general thoughts, management thoughts, and software development thoughts. Some of the key ideas summarized are: it is better to focus on creating value rather than profits; expecting the best from people can lead to better outcomes than persistent pessimism; and that fixing errors often costs less than extensive prevention efforts. The document collects wisdom from diverse thinkers and applies to different domains like management, teamwork, and software development.
The software developers are very important in the context of startups. A new mindset is one of responsible for it. This presentation shows what context of this, what are changing and some of the main aspects that support this change.
This document contains a presentation by Bill Smith on lessons learned from process improvement initiatives. The presentation includes 10 lessons: 1) Treat process improvement like a project; 2) Involve future users when developing processes; 3) Understand root causes of problems before assigning blame; 4) Avoid a one-size-fits-all improvement approach; 5) Walk before you run when implementing changes; 6) Keep an open mind; 7) Process improvement and compliance are not the same; 8) Plans without implementation are meaningless; 9) You may lose people and that's okay; and 10) Consider dissenting opinions. The presentation provides examples and references to support each lesson.
Dr.* Truemper, Or: How I learned to Stop Being Wasteful and Love Lean UXJake Truemper
Introduction to Lean UX, presented Nov 15 2013 at the St. Louis Days of .Net
In this presentation, Jake ("Dr. Truemper") speaks to Lean UX: what it is, why it should matter to you, basic tenants, and how it can be applied.
This document discusses lean thinking and agile principles for improving productivity. It promotes embracing change and continuous improvement over rigid plans. Key aspects covered include lean concepts like just-in-time production, eliminating waste, continuous flow, and respect for people. Agile principles emphasized include valuing individuals, interactions, and responding to change over rigid processes. Methodologies like Scrum, Kanban, and lean software development are presented as ways to apply these principles through iterative development, visualization, inspection, and adaptation.
The meeting notes covered many topics related to improving and focusing the company's culture and operations. Key discussion points included the need to do less but improve in core areas, lead by example, define the company's core values, listen to employee feedback, improve training, empower employees, and raise hiring standards. Overall, the notes emphasized the importance of clarity of purpose, continual small improvements, and creating work of excellence and contribution.
Execution is one of the most overlooked elements of business. Strategy, finances, and market opportunities seem to get a lot more attention. In my own experience, getting an A+ on execution will beat out the other companies who have A+'s in the more traditional areas.
The document provides a collection of thoughts and ideas from various sources organized into sections on general thoughts, management thoughts, and software development thoughts. Some of the key ideas summarized are: it is better to focus on creating value rather than profits; expecting the best from people can lead to better outcomes than persistent pessimism; and that fixing errors often costs less than extensive prevention efforts. The document collects wisdom from diverse thinkers and applies to different domains like management, teamwork, and software development.
The software developers are very important in the context of startups. A new mindset is one of responsible for it. This presentation shows what context of this, what are changing and some of the main aspects that support this change.
This document contains a presentation by Bill Smith on lessons learned from process improvement initiatives. The presentation includes 10 lessons: 1) Treat process improvement like a project; 2) Involve future users when developing processes; 3) Understand root causes of problems before assigning blame; 4) Avoid a one-size-fits-all improvement approach; 5) Walk before you run when implementing changes; 6) Keep an open mind; 7) Process improvement and compliance are not the same; 8) Plans without implementation are meaningless; 9) You may lose people and that's okay; and 10) Consider dissenting opinions. The presentation provides examples and references to support each lesson.
Dr.* Truemper, Or: How I learned to Stop Being Wasteful and Love Lean UXJake Truemper
Introduction to Lean UX, presented Nov 15 2013 at the St. Louis Days of .Net
In this presentation, Jake ("Dr. Truemper") speaks to Lean UX: what it is, why it should matter to you, basic tenants, and how it can be applied.
This document discusses lean thinking and agile principles for improving productivity. It promotes embracing change and continuous improvement over rigid plans. Key aspects covered include lean concepts like just-in-time production, eliminating waste, continuous flow, and respect for people. Agile principles emphasized include valuing individuals, interactions, and responding to change over rigid processes. Methodologies like Scrum, Kanban, and lean software development are presented as ways to apply these principles through iterative development, visualization, inspection, and adaptation.
The meeting notes covered many topics related to improving and focusing the company's culture and operations. Key discussion points included the need to do less but improve in core areas, lead by example, define the company's core values, listen to employee feedback, improve training, empower employees, and raise hiring standards. Overall, the notes emphasized the importance of clarity of purpose, continual small improvements, and creating work of excellence and contribution.
Cross Functional Teams and the Product ManagerSVPMA
This document summarizes a presentation by Ken Norton on working effectively as a product manager. Some key points include:
- Product managers often have accountability but little direct authority over teams who work on their products.
- It is important to build the right cross-functional team of about 7 people and invest "political capital" to do so.
- A product manager must communicate effectively to different stakeholders using their languages and represent the interests of those not in the room.
- To gain respect, a product manager should understand customer needs, remove obstacles for engineers, and make commitments for sales while bringing donuts for the team.
A Dutch presentation (with English quotes) about the ongoing renaissance in software engineering where we transition from begin regarded as mere drones to software craftsmen. This presentation is heavily influenced by Robert C. Martin's The Renaissance of Craftsmanship.
The document discusses the concept of "stickiness" and how to create messages that stick with audiences. It notes that messages need to be both simple and unexpected to stick. Simplicity is about prioritizing the most important elements, while unexpected elements violate people's existing schemas or preconceptions. Examples are then provided of startup ideas and management skills that emphasize starting small and focusing on writing and demonstration of value.
I have been fortunate to have worked with some geeks with incredible coding skills. I felt amazed at how they can play games with compilers, perform magic with their incantations on the shell, and solve some insanely complex algorithm problems with ease. I naively assumed that they are going to achieve greatness in near future. Alas, I was wrong. Really wrong. [Read the rest of the article ... ]
A talk I gave to the design and marketing team of a very large corporate about why it's hard to practice Design Thinking in a corporation. Borrows heavily from Clay Shirky. The slides may not make too much sense without me doing the talk.
Stand In The Gap - Leaders Think and ActClay Staires
This document discusses building leadership skills through different stages of development from worker to team builder to manager to leader. It emphasizes the importance of systems and execution to scale a business. It notes that most entrepreneurs are merely technicians who work in their business rather than on their business. To advance, it suggests focusing on developing systems, using checklists for accountability, and learning to delegate in order to gain freedom from the daily work. The overall message is that leadership requires ongoing learning and a shift from an individual production mindset to one focused on developing others and scalable processes.
Ready, Set, GO: Taking the First Steps in a UX Design Project and Unlocking C...Daniel Romlein
The daunting challenge of a blank page...er...Sketch file. For many of us, the actual “designing” phase of a project is typically fairly comfortable; it’s starting that’s messiest and most challenging. How do you avoid paralysis and get to that place where you can effectively use creativity to solve complex UX problems? Whether you’re designing a dazzling Uber-for-cupcakes consumer product or an HR insurance policy management tool, there are often pieces of the puzzle missing that it’s your job to track down and fit into the overall process. In this talk, I cut through the jargon and buzzwords and dig into practical first steps toward making your next project move faster and be more successful. As part of this we break into groups to test drive some techniques at our disposal to enhance the getting-started process. Expect to walk away more confident of how to go about getting the UX project ball rolling and producing your best work possible.
Agile Quote provides you with inspirational quotes on Agile software development delivered to you daily.
Quotes are from on-the-ground practitioners and speakers of the Agile community and contain links to resource and how-to-find more information.
Some quotes are not directly connected to agile software development, but somehow related ;-)
To celebrate 1000th quote milestone, we gathered top 20 most popular quotes to share here.
Project Management in practice - tips & tricksDana Manolescu
A presentation for students who want to embark on a journey to become Project Managers. The presentation is focused on digital projects, and talks from a personal perspective.
Follow dana-about-pm.com for more articles or presentations on this topic.
This document provides guidance on developing an effective vision statement for a startup founder. It recommends a two-part approach: 1) Explaining why you are doing what you do in terms of making meaning and addressing an important problem. 2) Clearly describing your value proposition or core offering in a concise statement. The vision should provide both meaning and direction for the company. Examples of early visions from successful companies are discussed. Developing an inspiring yet focused vision is presented as an important task for founders to guide strategic decisions and long-term success.
Becoming a UX Specialist, Generalist, or Both - David Thomas, 2016Mad*Pow
The document discusses different types of UX roles including specialists, generalists, and consultants. It emphasizes that soft skills are more important than hard skills for UX work. The document also explains that UX is about designing for experiences rather than discrete interfaces. True UX work requires skills in areas like research, strategy, information architecture, and design in order to understand user needs and improve their experiences.
This document outlines Oracle Primavera's vision for enterprise project portfolio management (EPPM) to drive innovation and productivity improvements. It discusses how EPPM can help organizations balance innovation with execution excellence through financial discipline, operational efficiency, and risk mitigation. The vision is to make EPPM enterprise-wide by deploying it across all initiatives and including all stakeholders. This integrated approach could help save organizations over $1 trillion annually through 60% productivity gains in industries like infrastructure.
Building A Successful Technology Career. Surviving and thriving in a technology career can be quite difficult. First you need to focus on your technical chops. Then you have to figure out how to work with your team members and manage your boss. We will cover the steps it takes to make a tech career successful.
This document contains a collection of quotes on various topics related to sustainability and innovation. Some of the key ideas discussed include:
- Sustainability and innovation require stepping outside of established mental models and challenging existing assumptions. Complex problems require systems-level thinking.
- Failure and risk-taking are necessary for innovation, but many organizations focus more on preventing failures than enabling innovation. Small-scale failures can provide learning opportunities.
- Future-focused thinking and embracing uncertainty can help unlock creativity and shape the future in a more sustainable direction. Both collaboration and individual acts of initiative will be needed to address sustainability challenges.
Software development management slides by George Berkowski (Hailo)MiniBar
This document provides a summary of key aspects of effective software development management. It discusses starting with a clear vision, focusing on building something useful. It emphasizes the importance of finding the right people through networking and making friends. When it comes to incentives for startups, it recommends creating your own company and mastering your own destiny. It also touches on outsourcing versus in-house work, the importance of being agile, using simple and integrated tools, and acting as your own best user to ensure quality.
This document discusses principles of management according to Tom Peters. It discusses how to build a curious corporation by hiring curious people, collecting weirdos, weeding out dullards, supporting generous sabbaticals, and fostering new interaction patterns. It also discusses making prototyping effective by using more prototypes early and representing system interactions, having customers be part of innovation teams, and having a plan-less culture of trying things first and fixing them fast. The document emphasizes that human resources must model innovative behavior 100% of the time and that the organization should have an adhocracy culture without strict linearity assumptions.
Design Thinking for Startups - Are You Design Driven?Amir Khella
This document discusses design thinking and how startups can integrate it into their process. It defines design thinking as combining creative and analytical thinking to solve problems. It recommends that startups (1) involve everyone in design thinking, not just designers, (2) deeply understand the problem to be solved, (3) create prototypes and get feedback to refine the solution, and (4) hire "T-shaped" individuals with skills across disciplines and encourage cross-training. The document emphasizes that design thinking is about understanding people and that anyone can be a good design thinker.
Cross Functional Teams and the Product ManagerSVPMA
This document summarizes a presentation by Ken Norton on working effectively as a product manager. Some key points include:
- Product managers often have accountability but little direct authority over teams who work on their products.
- It is important to build the right cross-functional team of about 7 people and invest "political capital" to do so.
- A product manager must communicate effectively to different stakeholders using their languages and represent the interests of those not in the room.
- To gain respect, a product manager should understand customer needs, remove obstacles for engineers, and make commitments for sales while bringing donuts for the team.
A Dutch presentation (with English quotes) about the ongoing renaissance in software engineering where we transition from begin regarded as mere drones to software craftsmen. This presentation is heavily influenced by Robert C. Martin's The Renaissance of Craftsmanship.
The document discusses the concept of "stickiness" and how to create messages that stick with audiences. It notes that messages need to be both simple and unexpected to stick. Simplicity is about prioritizing the most important elements, while unexpected elements violate people's existing schemas or preconceptions. Examples are then provided of startup ideas and management skills that emphasize starting small and focusing on writing and demonstration of value.
I have been fortunate to have worked with some geeks with incredible coding skills. I felt amazed at how they can play games with compilers, perform magic with their incantations on the shell, and solve some insanely complex algorithm problems with ease. I naively assumed that they are going to achieve greatness in near future. Alas, I was wrong. Really wrong. [Read the rest of the article ... ]
A talk I gave to the design and marketing team of a very large corporate about why it's hard to practice Design Thinking in a corporation. Borrows heavily from Clay Shirky. The slides may not make too much sense without me doing the talk.
Stand In The Gap - Leaders Think and ActClay Staires
This document discusses building leadership skills through different stages of development from worker to team builder to manager to leader. It emphasizes the importance of systems and execution to scale a business. It notes that most entrepreneurs are merely technicians who work in their business rather than on their business. To advance, it suggests focusing on developing systems, using checklists for accountability, and learning to delegate in order to gain freedom from the daily work. The overall message is that leadership requires ongoing learning and a shift from an individual production mindset to one focused on developing others and scalable processes.
Ready, Set, GO: Taking the First Steps in a UX Design Project and Unlocking C...Daniel Romlein
The daunting challenge of a blank page...er...Sketch file. For many of us, the actual “designing” phase of a project is typically fairly comfortable; it’s starting that’s messiest and most challenging. How do you avoid paralysis and get to that place where you can effectively use creativity to solve complex UX problems? Whether you’re designing a dazzling Uber-for-cupcakes consumer product or an HR insurance policy management tool, there are often pieces of the puzzle missing that it’s your job to track down and fit into the overall process. In this talk, I cut through the jargon and buzzwords and dig into practical first steps toward making your next project move faster and be more successful. As part of this we break into groups to test drive some techniques at our disposal to enhance the getting-started process. Expect to walk away more confident of how to go about getting the UX project ball rolling and producing your best work possible.
Agile Quote provides you with inspirational quotes on Agile software development delivered to you daily.
Quotes are from on-the-ground practitioners and speakers of the Agile community and contain links to resource and how-to-find more information.
Some quotes are not directly connected to agile software development, but somehow related ;-)
To celebrate 1000th quote milestone, we gathered top 20 most popular quotes to share here.
Project Management in practice - tips & tricksDana Manolescu
A presentation for students who want to embark on a journey to become Project Managers. The presentation is focused on digital projects, and talks from a personal perspective.
Follow dana-about-pm.com for more articles or presentations on this topic.
This document provides guidance on developing an effective vision statement for a startup founder. It recommends a two-part approach: 1) Explaining why you are doing what you do in terms of making meaning and addressing an important problem. 2) Clearly describing your value proposition or core offering in a concise statement. The vision should provide both meaning and direction for the company. Examples of early visions from successful companies are discussed. Developing an inspiring yet focused vision is presented as an important task for founders to guide strategic decisions and long-term success.
Becoming a UX Specialist, Generalist, or Both - David Thomas, 2016Mad*Pow
The document discusses different types of UX roles including specialists, generalists, and consultants. It emphasizes that soft skills are more important than hard skills for UX work. The document also explains that UX is about designing for experiences rather than discrete interfaces. True UX work requires skills in areas like research, strategy, information architecture, and design in order to understand user needs and improve their experiences.
This document outlines Oracle Primavera's vision for enterprise project portfolio management (EPPM) to drive innovation and productivity improvements. It discusses how EPPM can help organizations balance innovation with execution excellence through financial discipline, operational efficiency, and risk mitigation. The vision is to make EPPM enterprise-wide by deploying it across all initiatives and including all stakeholders. This integrated approach could help save organizations over $1 trillion annually through 60% productivity gains in industries like infrastructure.
Building A Successful Technology Career. Surviving and thriving in a technology career can be quite difficult. First you need to focus on your technical chops. Then you have to figure out how to work with your team members and manage your boss. We will cover the steps it takes to make a tech career successful.
This document contains a collection of quotes on various topics related to sustainability and innovation. Some of the key ideas discussed include:
- Sustainability and innovation require stepping outside of established mental models and challenging existing assumptions. Complex problems require systems-level thinking.
- Failure and risk-taking are necessary for innovation, but many organizations focus more on preventing failures than enabling innovation. Small-scale failures can provide learning opportunities.
- Future-focused thinking and embracing uncertainty can help unlock creativity and shape the future in a more sustainable direction. Both collaboration and individual acts of initiative will be needed to address sustainability challenges.
Software development management slides by George Berkowski (Hailo)MiniBar
This document provides a summary of key aspects of effective software development management. It discusses starting with a clear vision, focusing on building something useful. It emphasizes the importance of finding the right people through networking and making friends. When it comes to incentives for startups, it recommends creating your own company and mastering your own destiny. It also touches on outsourcing versus in-house work, the importance of being agile, using simple and integrated tools, and acting as your own best user to ensure quality.
This document discusses principles of management according to Tom Peters. It discusses how to build a curious corporation by hiring curious people, collecting weirdos, weeding out dullards, supporting generous sabbaticals, and fostering new interaction patterns. It also discusses making prototyping effective by using more prototypes early and representing system interactions, having customers be part of innovation teams, and having a plan-less culture of trying things first and fixing them fast. The document emphasizes that human resources must model innovative behavior 100% of the time and that the organization should have an adhocracy culture without strict linearity assumptions.
Design Thinking for Startups - Are You Design Driven?Amir Khella
This document discusses design thinking and how startups can integrate it into their process. It defines design thinking as combining creative and analytical thinking to solve problems. It recommends that startups (1) involve everyone in design thinking, not just designers, (2) deeply understand the problem to be solved, (3) create prototypes and get feedback to refine the solution, and (4) hire "T-shaped" individuals with skills across disciplines and encourage cross-training. The document emphasizes that design thinking is about understanding people and that anyone can be a good design thinker.
Gen Z and the marketplaces - let's translate their needsLaura Szabó
The product workshop focused on exploring the requirements of Generation Z in relation to marketplace dynamics. We delved into their specific needs, examined the specifics in their shopping preferences, and analyzed their preferred methods for accessing information and making purchases within a marketplace. Through the study of real-life cases , we tried to gain valuable insights into enhancing the marketplace experience for Generation Z.
The workshop was held on the DMA Conference in Vienna June 2024.
Discover the benefits of outsourcing SEO to Indiadavidjhones387
"Discover the benefits of outsourcing SEO to India! From cost-effective services and expert professionals to round-the-clock work advantages, learn how your business can achieve digital success with Indian SEO solutions.
HijackLoader Evolution: Interactive Process HollowingDonato Onofri
CrowdStrike researchers have identified a HijackLoader (aka IDAT Loader) sample that employs sophisticated evasion techniques to enhance the complexity of the threat. HijackLoader, an increasingly popular tool among adversaries for deploying additional payloads and tooling, continues to evolve as its developers experiment and enhance its capabilities.
In their analysis of a recent HijackLoader sample, CrowdStrike researchers discovered new techniques designed to increase the defense evasion capabilities of the loader. The malware developer used a standard process hollowing technique coupled with an additional trigger that was activated by the parent process writing to a pipe. This new approach, called "Interactive Process Hollowing", has the potential to make defense evasion stealthier.
2. “
When to use iterative
development? You should
use iterative development
only on projects that you
want to succeed.
Martin Fowler
Author and programmer
3. “
Do not be afraid to
make decisions.
Do not be afraid to
make mistakes.
Carly Fiorina
Business coach and politician
4. “
An organization that
treats its programmers
as morons
will soon have
programmers that
are willing and able
to act like morons only.
Bjarne Stroustrup
Computer scientist
9. There is nothing
so useless as
doing efficiently
that which should
not be done at all.
“
Peter Drucker
Management consultant and author
10. “
A vision should be judged
by the clarity of its values,
not the clarity of its
implementation path.
Donella H. Meadows
author of Thinking in Systems: A Primer
11. “
Sometimes it can
be really freeing to
have identified the
problem... Even
when you're it.
Kristen Belcher
Agile coach
12. “
The value of an idea
lies in the using of it.
Thomas Edison
Inventor
13. “
We shouldn’t add features
until they are needed.
Forget just in case;
develop just in time.
Mary Poppendieck
Lean trainer and author
16. Anonymous
“
The secret of getting ahead is getting started.
The secret of getting started is breaking your
complex overwhelming tasks into small
manageable tasks, and then start on the first
one.
17. Geoff Watts
Scrum trainer and author
“
As ScrumMasters,
we should all value
being great over
being good.
18. Antoine de Saint-Exupéry
Author
“
It seems that perfection is reached not
when there is nothing left to add,
but when there is nothing left
to take away.
22. “
Right and wrong
cease to be
useful concepts
when you’re talking about
software development.
Kent Beck
XP trainer and author
23. “
It doesn’t make sense to measure
anything unless you know why you are
measuring. This is the question to start
with, “What do you care most about?”
Pat Kua
Technical leader and author
24. If you want a
guarantee,
buy a toaster.
Clint Eastwood as
Nick Pulovski in
The Rookie
“
27. Jim Highsmith
Agile author
“
As a software development
consultant, I’ve never
encountered a successful
software company
(although my sample size is
limited) in which the team
and project leaders were
not technically savvy.
28. The important thing is not your process.
The important thing is your process for
improving your process.
“
Henrik Kniberg
Agile trainer and author
29. “
We have a propensity to believe in
magic. Anything we can do to align
our conversation around reality is
going to advance us much more.
Don Moen
Agile Coach
30. Douglas McGregor
Management professor
Most teams aren’t teams at all but merely
collections of individual relationships with
the boss. Each individual vying with the
others for power, prestige, and position.
“
31. Just because you make a
good plan, doesn’t mean
that’s what's gonna happen.
Taylor Swift
Singer-songwriter
32. Roman Pichler
Agile trainer and author
“
Keep your roadmap simple
and easy to understand.
Capture what really matters;
leave out the rest.
33. T. S. Eliot
Poet
“ When forced to work
within a strict framework
the imagination is taxed to
its utmost – and will
produce its richest ideas.
Given total freedom the
work is likely to sprawl.
37. “
As a general rule of thumb,
when benefits are not
quantified at all,
assume there aren’t any.
Tom DeMarco and Timothy Lister
Software development authors
41. That which is a feature to
a component team is a
task to a feature team.
“
Ken Rubin
Agile author and trainer
42. “
Be honest –
Without objectivity
and honesty,
the project team
is set up for failure,
even if developing
iteratively.
Ian Spence and Kurt Bittner
Agile authors
43. “
To be uncertain is to be uncomfortable,
but to be certain is to be ridiculous.
Chinese Proverb
44. “
Software is the most malleable product.
Companies need to use this
characteristics to their competitive
advantage, and sticking to traditional
waterfall development negates this
advantage.
Jim Highsmith
Agile author
45. “
It’s not the customer’s
job to solve their own
problems. It’s your job
to ask them the right
questions.
Melissa Perri
Author of Escaping the Build Trap
46. “
The more elaborate
our means of communication,
the less we communicate.
Joseph Priestley
Theologian
47. “
Everything is vague to a degree
you do not realize ‘till you have
tried to make it precise.
Bertrand Russell
Philosopher
48. “
(In software) Speed
is safety... the slower
you go, the more
dangerously you
wobble.
Charity Majors
Co-Founder and engineer, Honeycomb
49. “
Scrum without automation is like driving
a sports car on a dirt track – you won’t
experience the full potential,
you will get frustrated, and you will
probably end up blaming the car…
Ilan Goldstein
Scrum trainer and author
50. “
As an Agile coach, you don’t
need to have all the answers;
it takes time and a few
experiments to hit on
the right approach.
Rachel Davies and Liz Sedley
Agile trainers and authors
51. “
Eric Ries
Author, The Lean Startup
Innovation is a
bottoms-up,
decentralized, and
unpredictable thing,
but that doesn’t
mean it cannot be
managed.
53. “
In XP, we don’t
divide and conquer.
We conquer and
divide.
First we make
something that
works, then we bust
that up and solve
the little parts.
Kent Beck
XP trainer and author
54. “
People, not methodologies or
tools, make projects successful.
Lisa Crispin & Janet Gregory
Authors of Agile Testing
56. Bas Vodde and Craig Larman
Agile trainers and authors
“
After working for some years in the
domains of large, multisite, and
offshore development, we have
distilled our experience and advice
down to the following:
Don’t do it.
60. “
If you define the
problem correctly,
you almost have
the solution.
Steve Jobs
Apple Co-Founder
61. “
We define an agile tester this way:
a professional tester who embraces change,
collaborates well with both technical and
business people, and understands the
concept of using tests to document
requirements and drive development.
Lisa Crispin and Janet Gregory
Agile trainers and authors
62. “
You improvise.
You adapt.
You overcome.
Clint Eastwood as
Sergeant Highway in
Heartbreak Ridge
65. “
As a rule of thumb,
for every user who
tells you about a
problem, there will be
between 10 and 100
other users who
experienced the same
problem and didn’t
think to get in touch.
Paul Butcher
Software engineering author
66. “
As human beings,
we are amazingly
adaptable and
creative, yet most
of us work for
companies that
are not.
Gary Hamel
Author
67. Leonard Bernstein
Composer and conductor
“
To achieve great things,
two things are needed:
a plan, and not quite
enough time.
68. Pekka Himanen
Philosopher and author
“
It is not possible to create
interesting things in a constant
hurry or in a regulated way from
nine to five.
69. Ron Livingston as
Peter Gibbons in
Office Space
“
The thing is, Bob,
it’s not that I’m lazy,
it’s that I just don’t care.
79. Eric Ries
Author, The Lean Startup
“
Remove any
feature, process, or
effort that does not
contribute directly
to the learning you
seek.
80. Michael Hugos
Agile systems architect
“
Agility means that
you are faster than
your competition.
Agile time frames
are measured in
weeks and months,
not years.
84. “
Agile leaders lead teams,
non-agile ones manage tasks.
Jim Highsmith
Agile author
85. “
If you have a problem
and to solve it you
need someone else
to change, you don’t
understand your
problem yet.
Lyssa Adkins
Agile coach and author
87. “
Design and programming
are human activities;
forget that and all is lost.
Bjarne Stroustrup
Computer scientist
88. Karl Scotland
Agile trainer
“
Scrum focuses on being agile
which may (and should) lead to improving.
Kanban focuses on improving,
which may lead to being agile.
89. Walt Disney
Entrepreneur and Animator
“
When we go into that new project,
we believe in it all the way.
We have confidence in
our ability to do it right.
90. Elisabeth Hendrickson
Agile author and trainer
“
Agile teams produce a continuous
stream of value, at a sustainable pace,
while adapting to the
changing needs of the business.
94. “
You can’t make decisions based
on fear and the possibility of what
might happen.
Michelle Obama
Attorney, author, and former US First Lady
95. “
Making work visible
is one of the most
fundamental things
we can do to improve
Dominica DeGrandis
Author of Making Work Visible
96. Rachel Davies and Liz Sedley
Agile trainers and authors
“
Agile is all about teams
working together to
produce great software.
As an Agile coach, you
can help your team go
from first steps to
running with Agile to
unleashing their full
Agile potential.
97. “
No matter what the problem is,
it's always a people problem.
Gerald M. Weinberg
Author
98. “
A wrong decision is better than
no decision.
James Gandolfini as
Tony Soprano in
The Sopranos
100. “
Change is not for its own sake, it’s
the means to the end, not the end.
Pearl Zhu
Author of Digital Agility: The Rocky Road
from Doing Agile to Being Agile
101. “
Although self-organizing
is a good term,
it has, unfortunately,
become confused with
anarchy.
Jim Highsmith
Agile author
102. “
The benefit of allowing a
team to self-organize isn’t
that the team finds some
optimal organization for
their work that a manager
may have missed. Rather, it
is that by allowing the team
to self-organize, they are
encouraged to fully own the
problem.
Mike Cohn
Agile trainer and author
106. “
Kill your product
if a pivot is not
beneficial and
persevering
no option.
It’s tough but
the right thing to do.
Roman Pichler
Agile trainer and author
107. George Dinwiddie
Agile coach and trainer
“
Remember:
it’s not the documentation
that needs to be in sync,
but the people.
108. “
The first thing to realize when
formulating your first DoD (Definition
of Done) is that it isn’t cast in stone.
You don’t need to spend an eternity
deliberating what it should be,
because it can evolve over time.
Ilan Goldstein
Scrum trainer and author
109. “
Any fool can write code that
a computer can understand.
Good programmers write code
that humans can understand.
Martin Fowler
Author and programmer
113. “
Be prepared to cut your losses –
Canceling bad projects early
is success because you save time,
money and resources that can be
applied to better opportunities.
Ian Spence and Kurt Bittner
Agile authors
114. “
The best way to get
a project done faster
is to start sooner.
Jim Highsmith
Agile author
115. “
Optimism is an
occupational hazard
of programming:
feedback is
the treatment.
Kent Beck
XP trainer and author
116. “
Inside every large program,
there is a small program
trying to get out.
C.A.R. Hoare
Computer scientist
118. “
Be fixed on the vision,
but flexible on the journey.
Jeff Bezos
Founder of Amazon
119. “
“Scaling agile” always
sounds to me like “scaling
small-batch, hand-crafted
artisanal beer.” You end up
with Bud Light
Andy Hunt
Pragmatic programmer
120. Facts are better than
dreams.
Winston Churchill
Prime Minister
“
121. “
It’s better to be roughly
right than precisely wrong.
John Maynard Keynes
Economist
122. “
It is better to lead from
behind and to put
others in front,
especially when you
celebrate victory when
nice things occur. You
take the front line when
there is danger. Then
people will appreciate
your leadership.
Nelson Mandela
South African President
123. “
Agile is a philosophy,
not a methodology.”
Paul Bennett
Software engineer
124. “
When you are at a
crossroads about
trying something
or not, always
default to the try.
Carla A. Harris
Leader, author, and singer
125. “
In coaching, the idea
is to coach the person,
not the problem.
Lyssa Adkins
Agile coach and author
126. “
Frame our agility with fragility.
Embrace the humanity.
Lizzy Morris
Scrum trainer
133. “
People are what
make companies
agile, not approaches,
methodologies or
tools.
Pedro Gaspar Fernandes
Facilitator, neo-generalist
134. WHAT NEXT?
Mountain Goat Software offers education and certified training on
Scrum and agile processes to help all types of organizations become
more agile.
So how can you use Mountain Goat Software to succeed with agile?
WATCH A VIDEO COURSE
Master agile without leaving your desk with
courses including Better User Stories, Agile
Estimating and Planning, The Scrum Repair
Guide and more.
View video courses at
mountaingoatsoftware.com/training/video
JOIN THE COMMUNITY
The Agile Mentors Community is a growing
online network of agilists. Exclusive content
from Mike Cohn, monthly Q&A sessions, and
a private forum provide a wealth of agile
support when you need it.
View member benefits at
agilementors.com
135. ABOUT MOUNTAIN GOAT SOFTWARE
Mountain Goat Software offers education and certified training on
Scrum and agile processes to help all types of organizations become
more agile.
We offer training and education to help any organization adopt and
improve their use of agile processes and techniques. Scrum helps
companies build extreme high-performance development teams.
Whether you are interested in receiving coaching, consulting, or
training, we can help.
Learn more at: www.mountaingoatsoftware.com