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.

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

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.

Celebrate Successes, but Don't Declare Victory

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

Half, Not Half-Assed

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

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

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

Rule No. 2: Pair Customer Development with Agile Development Customer Development is useless unless the product development organization can iterate the product with speed and agility.

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.

21st century leaders will be growers, not knowers.

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

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

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

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.

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.

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.

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

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

Agile is simple—it just isn’t easy.

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

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.

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

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

agility: the ability to quickly change direction while traveling at a high speed.

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.

The R6 Resilience Change Management Framework is a cyclical framework that consists of six iterative puzzle pieces: 1. Review the Macro/Micro Changes: This iteration emphasizes the importance of scanning (mostly) the external environment to identify emerging trends, disruptions, and opportunities. By understanding the broader context in which the organization operates, leaders can anticipate future challenges and proactively adapt their strategies. There should never be a time in the organizations existence where it stops reviewing the macro changes. There are times, though, when micro changes (internal) are where the focus needs to be. 2. Reassess the Business’ Capabilities in the Context of Macro Changes: This iteration is fundamentally about “who are we, and how can we really add value?” It also involves a critical evaluation of the organization's strengths, weaknesses, opportunities, and threats in light of the identified macro changes. This reassessment helps to identify areas where the organization needs to adapt or transform its capabilities to remain competitive. This iteration is largely inward-looking, focused on the organization. But it tempered with the idea that “how do our capabilities allow us to add value to our customers lives (existing or new).” 3. Redefine Target Market(s) Based on Reassessment of Capabilities: This iteration focuses on aligning the organization's target markets with the evolving needs and preferences of customers, the changing competitive landscape, and the new reality of the businesses capabilities. This may involve identifying new customer segments, developing personalized offerings, creating seamless omnichannel experiences, or approaching the same target market in new ways (offering them new kinds of value, or the same kind of value in new ways). 4. Redirect Capabilities Toward Redefined Target Market: This iteration involves realigning the organization's resources, processes, and strategies to effectively serve the redefined target markets. This may require investments in new technologies, optimization of supply chains, or the development of innovative products and services. 5. Restructure the Organization: This iteration focuses on adapting the organization's structure, culture, and talent to support the desired changes. This may involve creating agile teams, fostering a culture of innovation, or empowering employees to make decisions through new policies. 6. Repeat in Perpetuity – or – Render Paradigm Shift [R6-RPS]: This iteration underscores the importance of continuous monitoring, evaluation, and adaptation. The R6 framework is not a one-time process in response to a change event, but an iterative cycle that enables organizations to remain agile and resilient in the face of ongoing change. Additionally, there are times when before repeating the cycle, a business may want/need to render an external paradigm shift by introducing a product or service or way of doing things that fundamentally changes the market – fundamentally changes the value exchange between customers, employees and organizations.

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.

DevOps benefits all of us in the technology value stream, whether we are Dev, Ops, QA, Infosec, Product Owners, or customers. It brings joy back to developing great products, with fewer death marches. It enables humane work conditions with fewer weekends worked and fewer missed holidays with our loved ones. It enables teams to work together to survive, learn, thrive, delight our customers, and help our organization succeed.

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.

Winners throw out the traditional product management and introduction processes they learned at existing companies. Instead, they combine agile engineering and Customer Development to iteratively build, test and search for a business model, turning unknowns into knowns. Winners also recognize their startup “vision” as a series of untested hypotheses in need of “customer proof.” They relentlessly test for insights, and they course-correct in days or weeks, not months or years, to preserve cash and eliminate time wasted on building features and products that customers don’t want.

DevOps requires potentially new cultural and management norms and changes in our technical practices and architecture. This requires a coalition that spans business leadership, Product Management, Development, QA, IT Operations, Information Security, and even Marketing, where many technology initiatives originate. When all these teams work together, we can create a safe system of work, enabling small teams to quickly and independently develop and validate code that can be safely deployed to customers. This results in maximizing developer productivity, organizational learning, high employee satisfaction, and the ability to win in the marketplace.

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?

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.

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.

In typical DevOps transformations, as we progress from deployment lead times measured in months or quarters to lead times measured in minutes, the constraint usually follows this progression: Environment creation: We cannot achieve deployments on-demand if we always have to wait weeks or months for production or test environments. The countermeasure is to create environments that are on demand and completely self-serviced, so that they are always available when we need them. Code deployment: We cannot achieve deployments on demand if each of our production code deployments take weeks or months to perform (i.e., each deployment requires 1,300 manual, error-prone steps, involving up to three hundred engineers). The countermeasure is to automate our deployments as much as possible, with the goal of being completely automated so they can be done self-service by any developer. Test setup and run: We cannot achieve deployments on demand if every code deployment requires two weeks to set up our test environments and data sets, and another four weeks to manually execute all our regression tests. The countermeasure is to automate our tests so we can execute deployments safely and to parallelize them so the test rate can keep up with our code development rate. Overly tight architecture: We cannot achieve deployments on demand if overly tight architecture means that every time we want to make a code change we have to send our engineers to scores of committee meetings in order to get permission to make our changes. Our countermeasure is to create more loosely-coupled architecture so that changes can be made safely and with more autonomy, increasing developer productivity.

The first surviving manuals of European swordsmanship date from the early fourteenth century, so it is impossible to know precisely how William trained and fought with this weapon, but it is clear that he honed his ability to wield his sword both while mounted and on foot. This must have required the daily repetition of practice sword strokes through his teenage years and beyond – so as to develop strength and acquire muscle memory – and regular sparring to refine coordination and agility. By the time he became a knight, Marshal was an effective swordsman, but so far as the History was concerned, his primary gift was not flashy technique, but the brutish physicality that enabled him to deliver crushing blows. With sword in hand, William was, in the words of his biographer, a man who ‘hammered like a blacksmith on iron’. Marshal probably also trained with a number of other mêlée weapons popular with twelfth-century knights, including the dagger, axe, mace and war-hammer, but much of his time would have been devoted to mastering the lance. By construction this was a fairly rudimentary weapon – often simply a ten- to twelve-foot-long straight spar of hewn wood, usually of ash – but it was fiendishly difficult to use from horseback. The lance would be held under the arm (or couched) during a charge, and directing its point towards a target with any accuracy required immense skill. Lances often broke after one or two uses, but a successful strike could cause devastating damage to an opponent. In the course of his career, William would witness the lethal potential of this weapon with his own eyes and he would also be called upon to charge down one of the greatest warriors of the age, Richard the Lionheart, with lance in hand.

Companies should utilize the CSIPP™ framework whenever they face crises. The 12 elements of CSIPP™, or Crisis Solution Internal Philosophy and Practice, include: 1. Immunity (Immune Systems): Organizations, akin to living organisms, possess inherent vulnerabilities. The CSIPP™ framework advocates for the establishment of proactive and self-regulating systems within an organization which autonomously identify, respond to, and mitigate threats, thereby enhancing the organization's resilience and adaptability. 2. Surveillance: Organizations need to cultivate a culture of informed awareness. This entails the implementation of judicious surveillance mechanisms to gather both internal and external intelligence. Such insights empower organizations to preemptively identify potential risks and opportunities, enabling more agile and effective decision-making. Data serves as the lifeblood of CSIPP™. It is imperative that organizations prioritize the collection, analysis, and interpretation of relevant data. This data-driven approach facilitates evidence-based decision-making, informed risk assessments, and the optimization of crisis response strategies. 3. Decisiveness: Decisiveness is particularly important during times of crisis. Leaders must be able to gather and synthesize the data, and make quick and definite decisions to move the organization forward. 4. Capital Reserves/Liquidity: Financial preparedness is a cornerstone of crisis management. Organizations must maintain adequate reserves of liquid capital to navigate unforeseen challenges. Moreover, they should proactively identify internal assets, both tangible and intangible, that can be readily redeployed in times of crisis. 5. Communication: Effective communication is pivotal during a crisis. Organizations should establish a comprehensive communication plan encompassing all stakeholders - employees, customers, investors, and the community at large. This plan should ensure timely, transparent, and accurate information dissemination, fostering trust and mitigating the spread of misinformation. 6. Response: The ability to respond swiftly and decisively is critical in crisis situations. Organizations must develop well-defined response protocols that outline roles, responsibilities, and escalation procedures. Regular drills and simulations can enhance preparedness and ensure a coordinated response. 7. Risk Evaluation: A continuous process of risk evaluation and assessment is essential. Organizations need to proactively identify, analyze, and prioritize potential risks based on their likelihood and potential impact. This enables the development of targeted mitigation strategies and contingency plans. 8. Leadership: Strong and decisive leadership is indispensable during a crisis. Leaders must be able to make difficult decisions under pressure, communicate effectively, and inspire confidence in their teams. A clear chain of command and delegation of authority are vital for effective crisis management. 9. Readiness (Drills/Training): All individuals likely to be involved in crisis response should receive comprehensive training and participate in regular drills. This ensures that they are familiar with their roles, responsibilities, and the organization's crisis management protocols. 10. Post-Crisis Analysis: Following a crisis, it is crucial to conduct a thorough post-mortem analysis. This involves evaluating the organization's response, identifying lessons learned, and implementing corrective actions to improve future crisis management efforts. 11. Nuanced Adjustment: Crisis management is not a one-size-fits-all endeavor. Organizations need to be adaptable and flexible, adjusting their strategies and tactics as the situation evolves. 12. Protocol: Clear and well-defined protocols are the backbone of effective crisis management. Organizations should establish a set of standard operating procedures (SOPs) that outline the steps to be taken in various crisis scenarios.

agile is the most disciplined and quality-driven set of development practices the industry has invented to date.

the user story as the primary artifact for identifying system behaviors that deliver value to the customer. We implied that engaging a user in a dialogue about how they use the system, and what benefit they derive, is a straightforward process.

Aesthetic perception involves changing frames of reference in order to see the hidden logic and orderliness behind what at first may seem random and strange. One of the selective pressures behind the development of the arts may be as a mechanism for developing mental agility; a way of rehearsing the capacity to change a mindset in the face of novelty and surprise. This leads directly to the mental shake-up which occurs whenever we are faced with fairly radical departures from the norm in terms of art and architecture: ‘the shock of the new’. It is this protean factor which enables us to adjust our mental models to accommodate such new evocations of art and architecture. As such it is an essential component of the fabric of aesthetic perception.

In the agile model, every sprint lasts for about 2 to 4 weeks where the developer has to spend 20% time on design, 40% on development and 40% on testing, which includes daily stand up call and other sprint meetings such as planning, review and retrospective.

Rather than the domain of work being repetitive, knowable, and deterministic with known-unknowns (you know how to fix it if something goes wrong), unique product development is unknowable and emergent with unknown-unknowns instead. For something that has not been done before, you don’t know what you don’t know until you do something and get feedback.

When I started exploring what flag I should plant back in 2009, there was a confluence of events in the works. The business world was increasingly using a methodology called Agile as its preferred product-development process while, at the same time, digital design was becoming increasingly important. Technology was rapidly evolving, and design was becoming a key differentiating factor for success—this was just a couple of years after the introduction of the iPhone. Companies were struggling to figure out how to integrate these two trends successfully, which created an opportunity for me—no one had solved this problem. This is where I decided to plant my flag—because I had the expertise, the opportunity, a real problem to solve that many people were dealing with, and the credibility to speak to it. I decided to work on solving this challenge and to bring everyone willing along with me on my journey. My teams and I started experimenting, trying different ways of working. We often failed, but as we were going through our ups and downs, I was sharing—publicly writing and giving talks about—what we were trying to do. Turned out I wasn’t the only one struggling with this issue. The more I wrote and the more I presented, the more widely I became known out in the world as someone who was not only working to solve this issue, but who was a source of ideas, honesty, and inspiration. So, when I left TheLadders, I had already planted my flag. I had found the thing I wanted to be known for and the work I was passionate about. A quick word of warning… Success on this path is a double-edged sword and you should approach this process with eyes open. The flag you plant today may very well be with you for the rest of your life—especially if you build widespread credibility on the topic. It’s going to follow you wherever you go and define you. No matter what else I do out in the world, I will forever be Jeff Gothelf—the Lean UX guy.

how to use Agile for physical products: Ask “What will you learn?” instead of “What will you do?” Make decisions at the right time, with the right people and the best available knowledge. Visualize the flow of knowledge from idea to launch.

The team quickly realized that the kanban board wasn’t helping as much as they thought. They could see the work on the board, and at first that had been exciting. But the work wasn’t moving.

The norm is that if you launch a big initiative and it fails (in any department, not just tech), it would certainly limit your career. In more agile cultures, failure isn’t punished. Instead, it’s a learning opportunity. The mindset of embracing risk and tolerating failure is a huge part of the software ethos. It’s also one of the biggest things that old companies avoid—even those with leaders who claim, as many do, that they want to become more like a startup.

It’s not just software itself—it’s the fundamental agility of software that drives Software People. It starts by listening to customers, rapidly building initial solutions to their problems, getting feedback, and then constantly iterating and improving. With this progression of computation, Software People can apply this software process to more and more of the world’s problems. I particularly enjoy seeing it arise in traditionally hardware-centric fields because when you see a Software Person running the playbook in the field of hardware, you can see the evolution play out physically in plastic, metal, and glass.

The GAP, or divide, between... Knowing and Doing, is only crossed by people who can effectively, and positively, manage their emotional state, and their inner RESPONSES to the outside world.

In Operations, we may deal with this problem with the following rule of thumb: When something goes wrong in production, we just reboot the server. If that doesn’t work, reboot the server next to it. If that doesn’t work, reboot all the servers. If that doesn’t work, blame the developers, they’re always causing outages.

We will continue to concentrate our energies entirely on prescription medicines and in vitro diagnostics, rather than diversify into other sectors like generics and biosimilars, over-the-counter medicines and medical devices.” ■ “With our in-house combination of pharmaceuticals and diagnostics, we are uniquely positioned to deliver personalized healthcare.” ■ “Our distinctiveness rests on four key elements: an exceptionally broad and deep understanding of molecular biology, the seamless integration of our pharmaceuticals and diagnostics capabilities, a diversity of approaches to maximise innovation, and a long-term orientation.” ■ “Our structure is built for innovation. Our autonomous research and development centres and alliances with over 200 external partners foster diversity and agility. Our global geographical scale and reach enables us to bring our diagnostics and medicines quickly to people who need them.

The strength that is developed in your muscles is underpinned by the other 6 foundations of total fitness: Flexibility Mobility Stability Agility Endurance Nutrition

Games as a Service is the future of the industry. Even large AAA franchises are transitioning to shipping minimal games that they can use to grow through live support over time.

A dispersed team has each of its members in separate locations. The COVID-19 pandemic of 2020 saw a massive increase of dispersed teams due to many developers transitioning to working from home, where they could be physically isolated from one another. Distributed teams have the advantage of co-location for each team. With proper inter-team management, such teams can overcome most challenges described in the next section. Dispersed teams, on the other hand, have a much more significant challenge. The daily communication within the team is constrained by members’ physical separation and the tools they use. Very often, such teams lose the cohesion necessary for a good team and simply become a “group of individuals” with far less engagement and productivity.

In their 2012 paper, “A Taxonomy of Dependencies in Agile Software Development,” Diane Strode and Sid Huff propose three different categories of dependency: knowledge, task, and resource dependencies.14 Such a taxonomy can help pinpoint dependencies between teams and the potential constraints to the flow of work ahead of time.

Archetype Other descriptions Achievement Performance, accountability, focus, speed, delivery, meritocracy, discipline, transparency, rigour Customer-Centric External focus, service, responsiveness, reliability, listening One-Team Collaboration, globalisation, internal customer, teamwork, without boundaries Innovative Learning, entrepreneurial, agility, creativity, challenging status quo, continuous improvement, pursuit of excellence People-First Empowerment, delegation, development, safety, care, respect, balance, diversity, relationships, fun Greater-Good Social responsibility, environment, citizenship, meaning, community, making a difference, sustainability

That’s why many Agile products start as feature poor. Chances are, features aren’t as important as getting an idea in front of customers quickly. So deadlines trump features, with quality as an underlying assumption.

That’s why many Agile products start as feature poor. Chances are, features aren’t as important as getting an idea in front of customers quickly. So deadlines trump features, with quality as an underlying assumption. Build less, but with confidence, is the path of many early product teams. If you’re right about the core, you can always iterate and build more features later.

Switch to proving ourselves wrong. We don’t do this enough, it’s like developing only happy paths, charged with biases and own agendas and we know where that leads. That’s why we write negative tests, do the same with your product bets

Actions for Impact If you’re interested in working on your rethinking skills, here are my top thirty practical takeaways. I. INDIVIDUAL RETHINKING A. Develop the Habit of Thinking Again 1. Think like a scientist. When you start forming an opinion, resist the temptation to preach, prosecute, or politick. Treat your emerging view as a hunch or a hypothesis and test it with data. Like the entrepreneurs who learned to approach their business strategies as experiments, you’ll maintain the agility to pivot.

Examples of slowification practices: using mock-ups, prototypes, simulations, scale model tests, offline problem-solving, land-based models, etc. §§ Examples of simplification practices: simple workflows, agile software development, modularization, just-in-time, pull systems, etc. ¶¶ Examples of amplification practices: stress tests, andon cords, smoke detectors, etc. to flag problems sooner rather than later.

Agile achieves speed, flexibility and responsiveness by working in small batches

Instead of making decisions early and waiting to the end to validate their decisions, they tried to learn as much as they could before committing to a decision.

Small batches create speed, flexibility and responsiveness for software projects.

Agile don’t hold true for physical product development: It’s much more difficult to develop a physical product by breaking it down into a single workstream of relatively independent features

No matter how good their CAD tools are, eventually they must build and test the product in the physical world.

Optimize batch sizes Limit work-in-process Put repeating events on a cadence Prioritize batches

Unmanaged” deconstructs the discipline of management and makes the compelling case that knowledge workers perform much more effectively for “Humble Gardeners” than “Angry Ranchers.” With decades of experience working with hundreds of professional service firms, Jack Skeels presents a convincing case for how the chronically misunderstood agile framework can produce transformational results.

The Agile, Lean IT, and DevOps movements helped demonstrate the enormous value of smaller, more autonomous teams that were aligned to the flow of business, developing and releasing in small, iterative cycles, and course correcting based on feedback from users.

You visit these big companies. You walk in the front door and it looks like the Taj Mahal. You are expecting wonders, but you start talking to people and you find that it’s just an ordinary place with dispirited staff. They aren’t pursuing big ideas and, even if they are, there’s no mechanism for developing them.” He adds, “I often walk out of these companies depressed about the waste of the human talent working there. These companies must become profoundly more productive if they are to survive in our competitive global economy.

There are unfortunately too many coaches who once they have secured a high-paying year-long contract will not use that time to help the organization along, but suddenly develop a lot of understanding for the PMO, partially to have a more comfortable life (sometimes under the disguise of not being a Scrum Nazi)

Innovation development, as we originally knew it, has changed fundamentally. It is increasingly a question of bringing new products and services into the market as quickly as possible. To meet changes in the market today means to realize new ideas with astonishing speed. Agile methods, such as design thinking or a focus on minimum viable products (see chapter MVP), help achieve

A decade earlier, we might have struggled for a year to get SARS-CoV-2 to grow in cell cultures. Messenger RNA proved to be an agile approach, allowing us to develop highly effective vaccines directly from the virus’s genetic composition.

In this tech-savvy world, the enhancement of globalization is changing our life very fast. However, you owe a small or large business; the use of the software is making our business simple yet. It helps us to manage our business effectively and reach great heights of success. Like many other software development companies around the world, Tech Dyno BD offers a software development service that helps your business or organization stay innovation-oriented, agile, and effective in managing company values best.

Bewilderingly, among some enterprises, there is a recent trend of anointing a special team that is separate from development and operations: the “DevOps” team. The whole point of DevOps is to create unity and collaboration among different specialties, not more silos. We even see job ads for “DevOps engineers,” who apparently are a special breed different from normal engineers and system admins. What happened? We believe this is the result of a buzzword-bingo approach to management. Rather than cultivating “individuals and interactions,” we have organizations hoping to avoid rethinking how to operate and instead get by with a reconfiguration of the software factory. And the surprising thing is that many have achieved that dubious goal.

Teams make decisions in Early Development that don’t get validated until later in the process. Then they have to go backwards to fix the problem, causing project delays, cost overruns and disappointing results.

shorten the time from decision to validation — but the implementation for hardware is completely different.

The inherent problem of waterfall development is that it forces a team to make decisions without the knowledge needed to make those decisions with confidence.

Agile software teams solve the problems with waterfall by building their software incrementally, making only the decisions around the specific work packages they’ve chosen to complete in a sprint. They delay even the decisions about which work packages or user stories to implement, choosing them out of a backlog at the start of each sprint. They get immediate feedback, first from their own tests and then from the users at a Demo to validate their decisions.

Early Development is all about making better decisions to set up the teams for success in middle and late development, then middle development is all about reducing risk of mistakes when these decisions are executed.

The Agile project manager plays a crucial role in ensuring the successful delivery of projects using Agile methodologies. They act as facilitators, coaches, and leaders, guiding the team through the iterative development process. Here are some key responsibilities of an Agile project manager: Orchestrating the project's lifecycle: This involves planning and breakdown of work into sprints, facilitating ceremonies like daily stand-ups, sprint planning, and retrospectives, and ensuring the project progresses smoothly towards its goals. Promoting collaboration and communication: Agile thrives on open communication and collaboration. The project manager fosters an environment where team members feel comfortable sharing ideas, concerns, and updates. They actively remove roadblocks and ensure everyone is aligned with the project vision and goals. Empowering the team: Agile teams are self-organizing and empowered to make decisions. The project manager provides guidance and support but avoids micromanaging. They trust the team's expertise and encourage them to take ownership of their work. Stakeholder management: The project manager acts as a bridge between the development team and stakeholders, including clients, sponsors, and other interested parties. They keep stakeholders informed of project progress, manage expectations, and address their concerns. Continuous improvement: Agile is an iterative process that emphasizes continuous improvement. The project manager actively seeks feedback from team members and stakeholders, analyzes project data, and identifies areas for improvement. They implement changes to the process and tools to enhance efficiency and effectiveness. Overall, the Agile project manager plays a vital role in driving successful project delivery through Agile methodologies. They wear multiple hats, acting as facilitators, coaches, leaders, and problem-solvers, ensuring the team has the resources, support, and environment they need to thrive.

Gate Reviews focus on questions around acceptable levels of risk, strategic alignment and business value.

Agile Software Development constructs that are not helpful when there are dependencies, long lead times, and resources from a variety of specific disciplines to manage with high cost-of-change. They don’t start over with a new plan every sprint or program increment.

the software team needs some way to validate their work before the responses from actual hardware are available. Simulators model behaviors from subsystems through the full system in virtual space — including user behavior. An emulator is a physical device that imitates the behavior of one subsystem, providing realistic inputs and outputs so that another subsystem can be developed independently.

For those aspects of the design that are high risk because they are entirely new and unproven, teams can choose to reduce this risk by exploring multiple alternatives. This allows them to delay the Last Responsible Moment for the final decision to preserve flexibility, and to learn faster about the alternatives so they are more likely to find the one that best meets their needs.

The key question to answer about any prototype is “What do I want to learn?” Prototypes validate the earlier decisions and design work, so often what we want to learn is this: “How well are the different parts working together?” and “Are we on target to meet our specifications and requirements?” If there’s a faster, better, cheaper way to learn those things, then it’s not yet time for a full system prototype.

If the group has done its work with emulators, simulators, small subsystem prototypes, convergence and other experiments, the team will be able to deliver a full system prototype that needs less work before moving on to the next phase.

knowledge work expands to fill the available time” problem.

Key Decisions have a sequence that reflects the process for executing the innovation. When teams understand how Key Decisions flow into one another, the sequence and timing for these decisions and who is ultimately responsible for making the decisions, they will be better prepared to make these decisions

But that doesn’t mean the plan is as stable as the plan to build a house. In middle development, teams still have learning to do, but the team’s focus is more on producing the deliverables that their partners need to produce the product at scale, sell it and support it in the field. While the team still has some Key Decisions to make and Knowledge Gaps to close, their focus turns more towards executing decisions that have already been made.

phase-gates are essential for effective physical product development because of the escalating levels of investment

At the end of every learning cycle, teams have Learning Cycle Events to share what they’ve learned. When it’s time to make Key Decisions, teams have Integration Events to bring together the decision makers with the knowledge the team has built to close the decisions.

Every learning cycle is a timebox: a fixed amount of time that the team will use to learn as much as it can about its Knowledge Gaps.

These scrums provide opportunities for problems to surface and for a team member who’s overloaded to get help from another team member. Software teams benefit from meeting every day because their batches (user stories) are small enough to require daily coordination.

A daily stand-up can get frustrating — it can seem like nothing’s moving. Teams usually do better with a Status Event two or three times per week instead of a daily scrum.

In software development, user stories can deliver direct user value independently

The user value delivered by a physical product can’t be broken down in the same way.

Rapid learning is guided by principles that propel learners to sprint through concepts, skills, and technologies, emerging as agile, lifelong learners.

We are big fans of the agile software movement. In 2001, seventeen software developers met in Snowbird, Utah, and published the “Manifesto for Agile Software.” The four main values in the manifesto remind us how the best friction fixers think and act: (1) “individuals and interactions over processes and tools”; (2) “working software over comprehensive documentation”; (3) “customer collaboration over contract negotiation”; and (4) “responding to change over following a plan.” Agile software teams deliver their work in small increments rather than in one “big bang” launch. Rather than following a rigid plan, they constantly evaluate results and constraints and update the software, and how they work, along the way.

Agile development is an approach to software development that emerged in the late 1990’s from a collection of ideas about how to make software development more lightweight, flexible, and incremental; it was formally defined during a meeting of practitioners in 2001.

One of the most important elements of agile development is the notion that development should be incremental and iterative. In the agile approach, a software system is developed in a series of iterations, each of which adds and evaluates a few new features; each iteration includes design, test, and customer input.

It used to be that developers rarely wrote tests. If tests were written at all, they were written by a separate QA team. However, one of the tenets of agile development is that testing should be tightly integrated with development, and programmers should write tests for their own code. This practice has now become widespread.

measure:9 •deployment frequency •deployment cycle time •change failure rate •development cycle time •number of incidents •mean time to recover (MTTR)

These organizations are able to perform experiments to test business ideas, discovering which ideas create the most value for customers and the organization as a whole, and which are then further developed into features that can be rapidly and safely deployed into production.

Instead of security and compliance activities only being performed at the end of the project, controls are integrated into every stage of daily work in the software development life cycle, resulting in better quality, security, and compliance outcomes.

David Varonin, a Certified Scrum Product Owner, thrives on fostering cultures of creativity and innovation. With a knack for problem-solving, he guides development teams in Agile practices, ensuring projects stay on track.

the development teams learn the product or the feature from the business owner’s point of view. They use the features. They understand more than what the feature does; they understand how the feature is intended to be integrated into the product. They understand the role of the feature in the intended customer experience. With this insight, the development team can make recommendations that simplify the experience and enable even more efficient future development. And with the trust that has been established, and with the credibility that the development team has earned by learning the experience of the product, they can challenge the requirements. They can make suggestions and recommendations from the customer perspective, not exclusively from a developer’s perspective. They immerse in the product to learn the experience of the product.

Understanding the requirements, and as importantly, understanding the value of the requirements, helps the developers prioritize each requirement against every other requirement.

You are the leader. What do you do? You have daily standups. Who do you include? You include your developers, your product owner, and your business owner. Why do you have daily standups? What’s your objective? What’s your intended outcome? It’s this: you connect so that you can gain insight, achieve clarity, achieve alignment, establish priorities, and make meaningful progress.

Motivated individuals are key to success. You as the leader motivate and inspire individuals from the day they join your team to the day they leave. You motivate and inspire the people on your team by teaching, sharing, empowering, challenging, trusting, holding accountable, rewarding, and developing.

Meaningful work has social value. The software development that enables meaningful work is by extension meaningful work in and of itself.

In these forums, not only are you sharing information and listening, but you are also teaching. This is an opportunity for you to share stories. Share the company’s story. Share your story. You are the leader, and you have stories about your career, about your development, about leaders you’ve had. You have stories about what you’ve learned and how you’ve learned. Stories are one of the most powerful ways to connect that human beings connect. Share your story.

A key differentiator between good leaders and the best leaders is this: good leaders support their teams, where the best leaders develop their teams.

I therefore believe that we will look back at the rise of the Agile brands being nothing more and nothing less than named collections of good practices as a crucial step in the evolution of software development.

with

It seems to me that Scrum and other agile techniques are being used as substitutes for careful modeling, where a product backlog is thrust at developers as if it serves as a set of designs. Most agile practitioners will leave their daily stand-up without giving a second thought to how their backlog tasks will affect the underlying model of the business. Although I assume this is needless to say, I must assert that Scrum, for example, was never meant to stand in place of design. No matter how many project and product managers would like to keep you marching on a relentless path of continuous delivery, Scrum was not meant only as a means to keep Gantt chart enthusiasts happy. Yet, it has become that in so many cases.

It seems to me that Scrum and other agile techniques are being used as substitutes for careful modeling, where a product backlog is thrust at developers as if it serves as a set of designs. Most agile practitioners will leave their daily stand-up without giving a second thought to how their backlog tasks will affect the underlying model of the business. Although I assume this is needless to say, I must assert that Scrum, for example, was never meant to stand in place of design. No matter how many project and product managers would like to keep you marching on a relentless path of continuous delivery, Scrum was not meant only as a means to keep Gantt chart enthusiasts happy. Yet, it has become that in so many cases.

We ignored the fact that many customers don’t know what they want. We ignored that fact that even when they know what they want, they can’t describe it. We ignored the fact that even when they can describe it, they often describe a proposed solution rather than the real need.

Instead of having a lengthy integration and qualification cycle, an agile process makes it part of the ongoing development process. This shift is accomplished through approaches like continuous integration/delivery, sprints with complete requirements, test-driven design, and automated testing. All this is put in place so that when customers think they have enough of the capabilities ready, the code is close to being ready to deploy.

business challenges started with a predicament of two-year long development cycles for delivering firmware, and of complex embedded software that had been slowly aging over many years and needed to be re-architected. Big-bang integrations were frequent. Before learning about agile, we had some early improvements and got to the point of 8-week development cycles, a daily build or two, and a nightly smoke test.

aim is to make the delivery of software from the hands of developers into production a reliable, predictable, visible, and largely automated process with well-understood, quantifiable risks. Using the approach that we describe in this book, it is possible to go from having an idea to delivering working code that implements it into production in a matter of minutes or hours, while at the same time improving the quality of the software thus delivered. The vast majority of the cost associated with delivering successful software is incurred after the first release. This is the cost of support, maintenance, adding new features, and fixing defects. This is especially true of software delivered via iterative processes, where the first release contains the minimum amount of functionality providing value to the customer. Hence the title of this book, Continuous Delivery, which is taken from the first principle of the Agile Manifesto: “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software

Software architecture plays a pivotal role in the delivery of successful software yet it’s frustratingly neglected by many teams.

Non-functional requirements” not sounding cool isn’t a reason to neglect them.

organisations often tend to see software architecture as a rank rather than a role too

As a noun then, architecture can be summarised as being about structure. It’s about the decomposition of a product into a collection of components/modules and interactions.

As a verb, architecture (i.e. the process, architecting) is about understanding what you need to build, creating a vision for building it and making the appropriate design decisions. All of this needs to be based upon requirements because requirements drive architecture.

a software architect who codes is a more effective and happier architect

You don’t need to be the best coder on the team

developers are likely to ignore your coding experience if you’re not programming on the project

Unlike the medieval building industry though, the software development industry lacks an explicit way for people to progress from being junior developers through to software architects. We don’t have a common apprenticeship model.

No one has yet figured out how to manage people effectively into battle; they must be led,” wrote John Kotter

accurately setting and managing expectations.

As anyone who has moved to an iterative development model will tell you, it takes two to be Agile. If

By doing this, Development and Operations may end up creating a shared work queue, instead of each silo using a different one (e.g., Development uses JIRA while Operations uses ServiceNow). A significant benefit of this is that when production incidents

The mix of Customer Development and Agile engineering dramatically increases the odds of new product and company success, while reducing the need for upfront cash and eliminating wasted time, energy, money and effort.

Arguing on the Internet is a complete and utter waste of time and energy. It is futile and illogical. Yet, despite being a category of people who rely on their keen sense of logic, software developers often argue on the Internet.

Agile is a response to the need for more continuous software repair. Its central strategy is to reduce the size and increase the frequency of the design-develop-test lifecycle. Over time, Agile has discovered and incorporated several powerful techniques to remove noise from the iterative lifecycle. These

But theory rarely works in practice, and predictability has a devious sister named complexity. But

However, for decades we have ended up with silos of information, where Development only creates logging events that are interesting to developers, and Operations only monitors whether the environments are up or down. As

It was important to us that for a developer, adding production telemetry didn’t feel as difficult as doing a database schema change.

Whenever there’s a problem B, we assume that event A caused it. The financial crisis is caused by bankers; the loss of jobs is caused by immigrants; the bad atmosphere at work is caused by the manager; the melting polar ice is caused by CO2 emissions; and the team didn’t make the deadline because someone screwed things up. Our linear thinking minds see the world as a place full of easily explainable events with simple causes and simple effects. Gerald Weinberg called it the Causation Fallacy [Weinberg 1992:90]. Our

Having developers share responsibility for the quality of the systems they build not only improves outcomes but also accelerates learning.

Contrast this to the more traditional model where Development and Test teams are assigned to a “project” and then reassigned to another project as soon as the project is completed and funding runs out. This leads to all sorts of undesired outcomes, including developers being unable to see the long-term consequences of decisions they make (a form of feedback) and a funding model that only values and pays for the earliest stages of the software life cycle—which, tragically, is also the least expensive part for successful products or services. ††

our goal is to create fast feedback and fast forward loops wherever work is performed, at all stages of the technology value stream, encompassing Product Management, Development, QA, Infosec, and Operations. This

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.

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.

In recent years, Eric Ries famously adapted Lean to solve the wicked problem of software startups: what if we build something nobody wants?[ 41] He advocates use of a minimum viable product (“ MVP”) as the hub of a Build-Measure-Learn loop that allows for the least expensive experiment. By selling an early version of a product or feature, we can get feedback from customers, not just about how it’s designed, but about what the market actually wants. Lean helps us find the goal. Figure 1-7. The Lean Model. Agile is a similar mindset that arose in response to frustration with the waterfall model in software development. Agilistas argue that while Big Design Up Front may be required in the contexts of manufacturing and construction where it’s costly if not impossible to make changes during or after execution, it makes no sense for software. Since requirements often change and code can be edited, the Agile Manifesto endorses flexibility. Individuals and interactions over processes and tools. Working software over comprehensive documentation. Customer collaboration over contract negotiation. Responding to change over following a plan.

We will actively manage this technical debt by ensuring that we invest at least 20% of all Development and Operations cycles on refactoring, investing in automation work and architecture and non-functional requirements (NFRs, sometimes referred to as the “ilities”), such as maintainability, manageability, scalability, reliability, testability, deployability, and security. Figure 11: Invest 20% of cycles on those that create positive, user-invisible value (Source: “Machine Learning and Technical Debt with D. Sculley,” Software Engineering Daily podcast, November 17, 2015,

In other words, when we conflate deployment and release, it makes it difficult to create accountability for successful outcomes—decoupling these two activities allows us to empower Development and Operations to be responsible for the success of fast and frequent deployments, while enabling product owners to be responsible for the successful business outcomes of the release (i.e., was building and launching the feature worth our time).

Myth—DevOps Means Eliminating IT Operations, or “NoOps”: Many misinterpret DevOps as the complete elimination of the IT Operations function. However, this is rarely the case. While the nature of IT Operations work may change, it remains as important as ever. IT Operations collaborates far earlier in the software life cycle with Development, who continues to work with IT Operations long after the code has been deployed into production. Instead of IT Operations doing manual work that comes from work tickets, it enables developer productivity through APIs and self-serviced platforms that create environments, test and deploy code, monitor and display production telemetry, and so forth. By doing this, IT Operations become more like Development (as do QA and Infosec), engaged in product development, where the product is the platform that developers use to safely, quickly, and securely test, deploy, and run their IT services in production.

Greenfield DevOps projects are often pilots to demonstrate feasibility of public or private clouds, piloting deployment automation, and similar tools. An example of a greenfield DevOps project is the Hosted LabVIEW product in 2009 at National Instruments, a thirty-year-old organization with five thousand employees and $1 billion in annual revenue. To bring this product to market quickly, a new team was created and allowed to operate outside of the existing IT processes and explore the use of public clouds. The initial team included an applications architect, a systems architect, two developers, a system automation developer, an operations lead, and two offshore operations staff. By using DevOps practices, they were able to deliver Hosted LabVIEW to market in half the time of their normal product introductions.

Just prior to the production push, all developers with changes going out must be present and check in on their IRC chat channel—any developers not present have their changes automatically removed from the deployment package. Rossi continued, “If everything looks good and our test dashboards and canary tests† are green, we push the big red button and the entire Facebook.com server fleet gets the new code delivered. Within twenty minutes, thousands and thousands of machines are up on new code with no visible impact to the people using the site.