Agile Development Quotes

Elephant, beyond the fact that their size and conformation are aesthetically more suited to the treading of this earth than our angular informity, have an average intelligence comparable to our own. Of course they are less agile and physically less adaptable than ourselves -- nature having developed their bodies in one direction and their brains in another, while human beings, on the other hand, drew from Mr. Darwin's lottery of evolution both the winning ticket and the stub to match it. This, I suppose, is why we are so wonderful and can make movies and electric razors and wireless sets -- and guns with which to shoot the elephant, the hare, clay pigeons, and each other.

The more detailed we made our plans, the longer our cycle times became

What someone may lack in talent can be more than made up for in self-motivation, self-direction, and follow-through.

Perhaps you thought that “getting it working” was the first order of business for a professional developer. I hope by now, however, that this book has disabused you of that idea. The functionality that you create today has a good chance of changing in the next release, but the readability of your code will have a profound effect on all the changes that will ever be made.

When business leaders talk about the next quarter, they ought to sometimes be talking about the next quarter century.

Overactive ego chakras kill objectivity, but mindfulness activates the win-win leadership chakras and brings collective and shared leadership.

Then I said to myself, "If the centuries are going by, mine will come too, and will pass, and after a time the last century of all will come, and then I shall understand." And I fixed my eyes on the ages that were coming and passing on; now I was calm and resolute, maybe even happy. Each age brought its share of light and shade, of apathy and struggle, of truth and error, and its parade of systems, of new ideas, of new illusions; in each of them the verdure of spring burst forth, grew yellow with age, and then, young once more, burst forth again. While life thus moved with the regularity of a calendar, history and civilization developed; and man, at first naked and unarmed, clothed and armed himself, built hut and palace, villages and hundred-gated Thebes, created science that scrutinizes and art that elevates, made himself an orator, a mechanic, a philosopher, ran all over the face of the globe, went down into the earth and up to the clouds, performing the mysterious work through which he satisfied the necessities of life and tried to forget his loneliness. My tired eyes finally saw the present age go by end, after it, future ages. The present age, as it approached, was agile, skillful, vibrant, proud, a little verbose, audacious, learned, but in the end it was as miserable as the earlier ones. And so it passed, and so passed the others, with the same speed and monotony.

Half, Not Half-Assed

Celebrate Successes, but Don't Declare Victory

Suppose a developer has a conversation with a customer about details of a feature. The conversation should not be considered complete until it is expressed as a customer test.

Resistance to change should be a thing of the past if we could develop growth mindsets and create organizations with growth cultures.

Motivation is a fine example of social complexity. It is nonlinear and sometimes unpredictable. It cannot be defined or modeled with a single diagram.

Potentially shippable is defined by a state of confidence or readiness, and shipping is a business decision.

Thriving in today’s marketplace frequently depends on making a transformation to become more agile.

A team can employ agile practices, but it won't achieve the potential benefit of agile development without embracing agile values and principles.

By adopting an agile mindset and providing improved engagement, collaboration, transparency, and adaptability via Scrum's values, roles, events, and artifacts, the results were excellent.

One of the Scrum rules is that work cannot be pushed onto a team; the Product Owner offers items for the iteration, and the team pulls as many as they decide they can do at a sustainable pace with good quality.

The MVP has just those features considered sufficient for it to be of value to customers and allow for it to be shipped or sold to early adopters. Customer feedback will inform future development of the product.

Many of the cataclysmic leadership failures were failures of rationality. The pendulum of leadership development needs to swing back toward the rational: strategy, creativity, foresight, decision-making, and analytics.

The Future of work is all about CREAM. More Consciousness, Relationships, Empathy, AdaptAgility, and Meaning. We must be building a more human-centered context for stakeholders, as opposed to JUST MORE profits for shareholders".

To call the belief in substantial human equality a superstition is to insult superstition. It might be unwarranted to believe in leprechauns, but at least the person who holds to such a belief isn’t watching them not exist, for every waking hour of the day. Human inequality, in contrast, and in all of its abundant multiplicity, is constantly on display, as people exhibit their variations in gender, ethnicity, physical attractiveness, size and shape, strength, health, agility, charm, humor, wit, industriousness, and sociability, among countless other features, traits, abilities, and aspects of their personality, some immediately and conspicuously, some only slowly, over time. To absorb even the slightest fraction of all this and to conclude, in the only way possible, that it is either nothing at all, or a ‘social construct’ and index of oppression, is sheer Gnostic delirium: a commitment beyond all evidence to the existence of a true and good world veiled by appearances. People are not equal, they do not develop equally, their goals and achievements are not equal, and nothing can make them equal. Substantial equality has no relation to reality, except as its systematic negation. Violence on a genocidal scale is required to even approximate to a practical egalitarian program, and if anything less ambitious is attempted, people get around it (some more competently than others).

agile development reflects a product lifecycle approach (continuous delivery of value), rather than a project approach (begin-end). While an individual release of a product can be managed as a project, an agile approach views a release as a single stage in a product’s ongoing evolution.

It is a myth that we can get systems “right the first time.” Instead, we should implement only today’s stories, then refactor and expand the system to implement new stories tomorrow. This is the essence of iterative and incremental agility. Test-driven development, refactoring, and the clean code they produce make this work at the code level.

There's no way to force someone to be energized. However, you can remove roadblocks.

The surest way to ensure career extinction is to resist change and adaptation.

Do you want a level of income to fit your lifestyle or a lifestyle to fit your income level?

I am suggesting that we don’t put the “income” cart before the “contentment” horse.

there comes a time in a man's life when, no matter how agile the spirit, the earthly carapace develops its limitations

There is really no bad software development process. There is only how you are doing it today and better.

To focus on the visible at the expense of the essential is irresponsible.

It may seem like writing tests slows down development; in fact, testing does not cost, it pays, both during development and over the system’s lifecycle.

Agile is simple—it just isn’t easy.

A ScrumMaster’s role on the team is compared to a sheepdog. They guide the team toward the goal by enforcing boundaries, chasing off predators, and giving the occasional bark.

21st century leaders will be growers, not knowers.

Perhaps the most important problem-solving skill that I have learned and practiced over the years is mental agility.

Complexity kills. It sucks the life out of developers, it makes products difficult to plan, build, and test.” —Ray Ozzie, CTO, Microsoft Corporation

Code formatting is about communication, and communication is the professional developer’s first order of business.

Iterative development, when accompanied with reasonable end-of-iteration reviews—product, technical, process, team—is also self-correcting.

The feature delivery approach helps define a workable interface between customers and product developers.

In my early years of iterative development, I thought timeboxes were actually about time. What I came to realize is that timeboxes are actually about forcing tough decisions.

Project leaders need to focus on value in several ways: value determination (with product owners), value prioritization (backlog management), and value creation (iterative development).

It is not enough for code to work. Code that works is often badly broken. Programmers who satisfy themselves with merely working code are behaving unprofessionally. They may fear that they don’t have time to improve the structure and design of their code, but I disagree. Nothing has a more profound and long-term degrading effect upon a development project than bad code.

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

APM focuses on team management, from building self-organizing teams to developing a servant leadership style. It is both more difficult, and ultimately more rewarding than managing tasks.

While Abraham, gifted with physical agility and uncommon athletic prowess, had to make his mind, Teedie, privileged beyond measure with resources to develop his mind, had to make his body.

Your first investment should be in yourself. Learn new skills. The market can go up or down but you’ll never lose your skills. This is more true today than ever before. Diversify your skills.

Agile Project Management -like its lean development counterparts- streamlines the development process, concentrating on value-adding activities and eliminating overhead and compliance activities.

APM's core purpose of creating innovative new products and services means dealing with constant technological and competitive change, generating novel ideas, and continually reducing product development schedules.

Code formatting is important. It is too important to ignore and it is too important to treat religiously. Code formatting is about communication, and communication is the professional developer’s first order of business.

Consciously Constructive Human Capital Development, Perpetual Reinvention: innovation & Creativity, Adaptability, Resilience and Agility, are not only CORE DRIVERS, but also the DEFINING features of economic success in the 4IR.

Clean code can be read, and enhanced by a developer other than its original author. It has unit and acceptance tests. It has meaningful names. It provides one way rather than many ways for doing one thing. It has minimal dependencies, which are explicitly defined, and provides a clear and minimal API. Code should be literate since depending on the language, not all necessary information can be expressed clearly in code alone. -Dave Thomas, founder of OTI, godfather of the Eclipse strategy

Compared to kids confined indoors, children who regularly play in nature show heightened motor control—including balance, coordination, and agility. They tend to engage more in imaginative and creative play, which in turn fosters language, abstract reasoning, and problem-solving skills, together with a sense of wonder. Nature play is superior at engendering a sense of self and a sense of place, allowing children to recognize both their independence and interdependence. Play in outdoor settings also exceeds indoor alternatives in fostering cognitive, emotional, and moral development. And individuals who spend abundant time playing outdoors as children are more likely to grow up with a strong attachment to place and an environmental ethic.

The agile value "Delivering Value over Meeting Constraints" provides a focus for rethinking how we measure performance on projects. Although constraints such as cost and time are important, they should be secondary to creating value for customers. All too often, we focus on what is easily measurable and ignore really important characteristics that are harder to quantify. Agile development attempts to change that bias and focus on the most important things, and value is at the top of that list.

Agile coach: The individual is an agile expert who provides guidance for new agile implementations as well as existing agile teams. The agile coach is experienced in employing agile techniques in different environments and has successfully run diverse agile projects. The individual builds and maintains relationships with everyone involved, coaches individuals, trains groups, and facilitates interactive workshops. The agile coach is typically from outside the organization, and the role may be temporary or permanent.

So, why do we do development work in these short cycles? To learn. Experience is the best teacher, and the scrum cycle is designed to provide you with multiple opportunities to receive feedback—from customers, from the team, from the market—and to learn from it.

Nothing has a more profound and long-term degrading effect upon a development project than bad code. Bad schedules can be redone, bad requirements can be redefined. Bad team dynamics can be repaired. But bad code rots and ferments, becoming an inexorable weight that drags the team down.

The majority of the cost of a software project is in long-term maintenance. In order to minimize the potential for defects as we introduce change, it’s critical for us to be able to understand what a system does. As systems become more complex, they take more and more time for a developer to understand, and there is an ever greater opportunity for a misunderstanding. Therefore, code should clearly express the intent of its author. The clearer the author can make the code, the less time others will have to spend understanding it. This will reduce defects and shrink the cost of maintenance.

Shifting customer needs are common in today's marketplace. Businesses must be adaptive and responsive to change while delivering an exceptional customer experience to be competitive. Traditional development and delivery frameworks such as waterfall are often ineffective. In contrast, Scrum is a value-driven agile approach which incorporates adjustments based on regular and repeated customer and stakeholder feedback. And Scrum’s built-in rapid response to change leads to substantial benefits such as fast time-to-market, higher satisfaction, and continuous improvement—which supports innovation and drives competitive advantage.

In our relationships, creative lives, personal development, and work, we can promote this advancement in two ways-- expanding our breadth (what we do: the skills we acquire, the topics we talk about, the avenues we explore) and our depth (how well we do what we do: the quality of our listening, our level of engagement with the world).

The ability to respond to change is good. The ability to create change for competitors is even better. When you create change you are on the competitive offensive. When you respond to competitors' changes you are on the defensive. When you can respond to change at any point in the development lifecycle, even late, then you have a distinct advantage.

Executives, project leaders, and development teams must embrace a different view of the new product development world, one that not only recognizes change in the business world, but also understands the power of driving down iteration costs to enable experimentation and emergent processes. Understanding these differences and how they affect product development is key to understanding APM.

Driving exploration is critical, but knowing when to stop is also. Product development is exploring with a purpose, delivering value within a set of constraints. Frequent, timeboxed iterations compel the development and product teams and executives to make difficult tradeoff decisions early and often during the project. Feature delivery contributes to realistic evaluations because product managers can look at tangible, verifiable results.

While it is not unheard of, most sane people would be embarrassed to take an introductory martial arts class and then develop their own “martial art” from it and teach it to unsuspecting students, exposing them to the danger of miscalculating their effectiveness at defending themselves in a critical situation. Yet agile practitioners do this every day ― some do not even feel any sense of shame for calling themselves “agile coaches” after a year of practical experience.

Silicon Valley is famous for mantras like “move fast and break things” and implementing them through strategies like “minimum viable product” (MVP). These types of agile strategies can only work if you have the option to quit. You can’t put out an MVP unless you have the ability to pull it back. The whole point is to get information quickly, so you can quit the stuff that isn’t working and stick with the things that are worthwhile or develop new things that might work even better.

This principle fits well with the concept of business and development working daily. Business needs to be intensely involved with the process, if for nothing more than identifying the 80% of the work that we really don’t have to do. Just think of the amount of money that could be saved every year by reducing project scope to only those features and functions that are actually used! Think of how quickly we could deliver functionality! Think of how many more “projects” we could complete!

An adaptive development process has a different character from an optimizing one. Optimizing reflects a basic prescriptive Plan-Design-Build lifecycle. Adapting reflects an organic, evolutionary Envision-Explore-Adapt lifecycle. An adaptive approach begins not with a single solution, but with multiple potential solutions (experiments). It explores and selects the best by applying a series of fitness tests (actual product features or simulations subjected to acceptance tests) and then adapting to feedback.

We live in an age in which the volume of available information stupefies us. On any relatively interesting subject we can find thousands of Web pages, tens—if not hundreds—of books, and article after article. How do we filter all this information? How do we process all this information? Core values and principles provide one mechanism for processing and filtering information. They steer us in the direction of what is more, or less, important. They help us make product decisions and evaluate development practices.

Recommended Reading The Definitive Guide to Getting Your Budget Approved by Johannes Ritter and Frank Röttgers provides a systematic guide for creating a financial business case. The book includes examples as well as the methods for using Monte Carlo simulation and sensitivity analysis to create the business case. The methods described in the book can also be used for quantifying risks and project costs. Mary and Tom Poppendieck in their book Lean Software Development: describe the lean principles and the types of waste in software projects.

Countering the juggernaut of formalism is a minority worldview of equal historical standing, even though it does not share equal awareness or popularity. Variously known as hermeneutics, constructivism, interpretationalism, and most recently postmodernism, this tradition has consistently challenged almost everything advanced by the formalists. Iterative development practices, including XP, and object thinking are consistent with the hermeneutic worldview. Unfortunately, most object, XP, and agile practitioners are unaware of this tradition and its potential for providing philosophical support and justification for their approach to software development.

That is what I want our young nascent readers to become: expert, flexible code switchers -- between print and digital mediums now and later between and among the multiple future communication mediums....I conceptualize the initial development of learning to think in each medium as largely separated into distinct domains in the first school years, until a point in time when the particular characteristics of the two mediums are each well developed and internalized. That is an essential point. I want the child to have parallel levels of fluency, if you will, in each medium, just as if he or she were similarly fluent in speaking Spanish and English. In this way the uniqueness of the cognitive processes honed by each medium would be there from the start.

Improve performance through process improvements introduced with minimal resistance. Deliver with high quality. Deliver a predictable lead time by controlling the quantity of work-in-progress. Give team members a better life through an improved work/life balance. Provide slack in the system by balancing demand against throughput. Provide a simple prioritization mechanism that delays commitment and keeps options open. Provide a transparent scheme for seeing improvement opportunities, thereby enabling change to a more collaborative culture that encourages continuous improvement. Strive for a process that enables predictable results, business agility, good governance, and the development of what the Software Engineering Institute calls a high-maturity organization.

How could boredom be beneficial? In Hindu and Buddhist traditions, boredom is described as a precursor to insight and discovery. Parents sometimes want their children to be bored because they have an intuitive sense that grappling with this uncomfortable state is how kids discover what they’re interested in, quiet their mind, and find outlets to channel their energy. We wish more parents would trust that when their kids get bored, they’ll find the way out on their own, resisting the temptation to schedule activities from morning to night to keep boredom at bay. But don’t just take our word for it. The American Academy of Pediatrics released a 2007 consensus statement on how child-directed, exploratory play is far superior when it comes to developing emotional, social, and mental agility than structured, adult-guided activity.

I would compare a project with a country, which is either properly regulated by the laws or enslaved by a dictator whom everybody is supposed to love. What modern management is doing in most companies is the latter scenario. They expect us to love the customer and work just because of that. There are no laws, no discipline, no regulations, and no principle, because, like every dictator, they simply are not competent enough in creating them. Dictators just capture the power and rule by the force: it's much easier than building a system of laws, which will work by itself. The management in software projects also can't create a proper management system, since they simply don't have enough knowledge for that. Instead, they expect our love. Isn't it obvious that rather soon that love turns into hate and we quit or the project collapses?

It is difficult to find any precise use of metaphor, simile, or other conceit, which is common to all the poets and at the same time important enough as an element of style to isolate these poets as a group. Donne, and often Cowley, employ a device which is sometimes considered characteristically 'metaphysical'; the elaboration (contrasted with the condensation) of a figure of speech to the furthest stage to which ingenuity can carry it. Thus Cowley develops the commonplace comparison of the world to a chess-board through long stanzas ("To Destiny"), and Donne, with more grace, in "A Valediction," the comparison of two lovers to a pair of compasses. But elsewhere we find, instead of the mere explication of the content of a comparison, a development by rapid association of thought which requires considerable agility on the part of the reader.

When applying agile practices at the portfolio level, similar benefits accrue: • Demonstrable results—Every quarter or so products, or at least deployable pieces of products, are developed, implemented, tested, and accepted. Short projects deliver chunks of functionality incrementally. • Customer feedback—Each quarter product managers review results and provide feedback, and executives can view progress in terms of working products. • Better portfolio planning—Portfolio planning is more realistic because it is based on deployed whole or partial products. • Flexibility—Portfolios can be steered toward changing business goals and higher-value projects because changes are easy to incorporate at the end of each quarter. Because projects produce working products, partial value is captured rather than being lost completely as usually happens with serial projects that are terminated early. • Productivity—There is a hidden productivity improvement with agile methods from the work not done. Through constant negotiation, small projects are both eliminated and pared down.

recent research indicates that unstructured play in natural settings is essential for children’s healthy growth. As any parent or early childhood educator will attest, play is an innate drive. It is also the primary vehicle for youngsters to experience and explore their surroundings. Compared to kids confined indoors, children who regularly play in nature show heightened motor control—including balance, coordination, and agility. They tend to engage more in imaginative and creative play, which in turn fosters language, abstract reasoning, and problem-solving skills, together with a sense of wonder. Nature play is superior at engendering a sense of self and a sense of place, allowing children to recognize both their independence and interdependence. Play in outdoor settings also exceeds indoor alternatives in fostering cognitive, emotional, and moral development. And individuals who spend abundant time playing outdoors as children are more likely to grow up with a strong attachment to place and an environmental ethic. When asked to identify the most significant environment of their childhoods, 96.5 percent of a large sample of adults named an outdoor environment. In

Plan-driven development works well if you are applying it to problems that are well defined, predictable, and unlikely to undergo any significant change. The problem is that most product development efforts are anything but predictable, especially at the beginning. So, while a plan-driven process gives the impression of an orderly, accountable, and measurable approach, that impression can lead to a false sense of security. After all, developing a product rarely goes as planned. For many, a plan-driven, sequential process just makes sense, understand it, design it, code it, test it, and deploy it, all according to a well-defined, prescribed plan. There is a belief that it should work. If applying a plan-driven approach doesn’t work, the prevailing attitude is that we must have done something wrong. Even if a plan-driven process repeatedly produces disappointing results, many organizations continue to apply the same approach, sure that if they just do it better, their results will improve. The problem, however, is not with the execution. It’s that plan-driven approaches are based on a set of beliefs that do not match the uncertainty inherent in most product development efforts.

Over the span of a year or two, teams that were moving very fast at the beginning of a project can find themselves moving at a snail’s pace. Every change they make to the code breaks two or three other parts of the code. As productivity decreases, management does the only thing they can; they add more staff to the project to increase productivity. But that new staff is not versed in the design of the system. Furthermore, they, and everyone else on the team, are under horrific pressure to increase productivity. So they all make more and more messes, driving productivity further toward zero. Eventually the team rebels. They inform management that they cannot continue to develop in this odious code base. Management does not want to expend resources on a whole new redesign of the project, but they cannot deny that productivity is terrible. Eventually, they bend to the demands of the developers and authorize the grand redesign in the sky. A new tiger team is selected. Everyone wants to be on this team because it’s a green-field project. They get to start over and create something wonderful. But only the best and brightest are chosen for the tiger team. Everyone else must continue to maintain the current system. Now the two teams are in a race. The tiger team must build a new system that does everything that the old system does. Management will not replace the old system until the new system can do everything that the old system does. This race can go on for a very long time. I’ve seen it take 10 years. And by the time it’s done, the original members of the tiger team are long gone, and the current members are demanding that the new system be redesigned because it’s such a mess.

A great tide of civilization governs how humans do things. When that tide goes out, we centralize, establish command and control structures, and attempt to find efficiencies in large batches and long queues. When the water starts to come back in, we break down those structures, start to drive control down into the hands of 'common' folk, and attempt to find efficiencies in the quick decisions that get made by people closest to the problem. The tide is coming back in and will probably continue to ebb that direction for the lifespan of anyone alive at the time of this writing.

Everyone is dispensable but some are more dispensable than others.

Labor saving devices have destroyed many jobs but have given rise to many new ones. It simply is up to us if we are going to resist or embrace the future.

The construct of retirement is dubious at best and a farce at worst. Expectations contrary to this are to be dashed.

Adaptability is the name of the game; if you understand that you must now be adaptable and flexible, you will find a way to succeed in your career. If not, you will succumb to job market pressures.

In the name of all that is holy, please consider the wages of a particular profession before you select that degree plan.

Whereas previous generations had to face some unpredictability, current generations are facing unprecedented levels of instability.

Finding a job that is a good fit is as much about you selecting the right company as it is about them selecting the right candidate.

Can’t we do better with Applicant Tracking System (ATS) software?

When presented with an open door in your job, drive a Mack truck through it.

There remains a natural career progression even though the tougher job climate seeks to delay it.

Our career mantra should be learn, relearn, repeat.

We don’t deserve our job. Period.

the critical factor in motivation is not measurement,8 but empowerment: moving decisions to the lowest possible level in an organization while developing the capacity of those people to make decisions wisely.

Mike had explained that agile software development, intentional community, and group dynamics had emerged from a single pool of primordial psychological research and indigenous traditions.

Certified Scrum Developers have demonstrated through a combination of formal training and a technical skills assessment that they have a working understanding of Scrum principles and have learned specialized Agile engineering skills. This 3-5 day course provides hands-on instruction in the agile engineering practices. Engineering practices include agile architecture and design, test first approach, paired programming and behavior driven development.

believe that this is simpler than it sounds. It is about identifying the obstacles in our way and taking today’s best-practice ideas—those found in the Agile Manifesto and in books like Lean Startup, Lean Software Development, Lean Enterprise, The DevOps Handbook, and others on today’s management bookshelves—and applying them to IT leadership.

We’re all doing the same thing — getting stuff done. We work together to make it happen, and we jump back and forth between all the normal development activities as the situation dictates.

Given the fear or indecision we often confront when attempting to unleash our creativity, the practice of rigorously smallifying problems is liberating. At the same time, while some externally imposed constraints can be onerous, many can be enormously helpful starting points. This is the great irony about constraints. And if we can delineate the job before us into discrete problems to solve, as General McMaster, agile developers, and Gehry do by taking a proactive approach to problem finding, we are more likely to discover unique possibilities.

In the previous two decades, as NUMMI’s success had become better known, executives in other industries had started adapting the Toyota Production System philosophy to other industries. In 2001, a group of computer programmers had gathered at a ski lodge in Utah to write a set of principles, called the “Manifesto for Agile Software Development,” that adapted Toyota’s methods and lean manufacturing to how software was created.

If you are going to use automated testing and Continuous Integration (CI) to dramatically improve your productivity, you need to treat your testing investments as being at least as important, or even more important, than your development investments, which is a big cultural change for most organizations. In

If this feedback takes days or weeks to get to them, it is of limited value to the developers’ learning. If