Agile Teams Quotes

In high-performing organizations, everyone within the team shares a common goal—quality, availability, and security aren’t the responsibility of individual departments, but are a part of everyone’s job, every day.

We practice mastering ourselves in the moment so that we can better open ourselves to being a servant leader and to harness our emotions and choose what to do with our reactions.

We found in surveys of Agile teams that some 80 percent to 90 percent of Agile teams perceive tension between the way the Agile team is run and the way the whole organization is run. In half of those cases, the tension was “serious.

Over-seriousness is a warning sign for mediocrity and bureaucratic thinking. People who are seriously committed to mastery and high performance are secure enough to lighten up. —Michael J. Gelb

Celebrate Successes, but Don't Declare Victory

small batches of work, small teams, short cycles, and quick feedback—in effect, “small everything.

That which a team does not want to discuss, it most needs to discuss.

What this team did not realize was that having dirty tests is equivalent to, if not worse than, having no tests.

Team performance is directly proportional to team stability. Focus on building and maintaining a stable team. Stability reduces friction and increases credibility and confidence.

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 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".

It’s often the case that teams working in agile processes do not actually go back to improve the user interface of the software. But, as the saying goes, “it’s not iterative if you only do it once.” Teams need to make a commitment to continuous improvement, and that means not simply refactoring code and addressing technical debt but also reworking and improving user interfaces. Teams must embrace the concept of UX debt and make a commitment to continuous improvement of the user experience.

High Performance Teams and Execution Speed, has no value, if you are going in the wrong direction!

If you have a problem and to solve it you need someone else to change, you don’t understand your problem yet

To be full of love and enthusiasm for your work is a prerequisite for collaboration, a professional obligation;

First, how could I protect my team from the incessant demands of the business and achieve what the Agile community now refers to as a “sustainable pace”?

every Scrum team needs a ScrumMaster.

true agility means that teams are constantly working to evolve their processes to deal with the particular obstacles they are facing at any given time.

The problem is not that there are problems. The problem is expecting otherwise and thinking that having problems is a problem. —Theodore Rubin

In high-performance teams, "the leaders managed the principles, and the principles managed the team.

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

In an agile project the team takes care of the tasks and the project leader takes care of the team.

At the core of healthy team relationships is trust and respect.

Where is the integrity in telling the team they “must have all this done by this date” when you haven’t asked the team if it is even possible?

If everyone is speaking the same language, then it becomes easier to create a team where everyone is of the same mind.

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.

A retrospective’s huge potential for learning should not be off-limits to any team member.

Beginners think that there is no documentation in agile, which is not true. It’s about choosing the types of documentation that are useful.

Lean UX is a transparent process that not only reveals what designers do but encourages participation from everyone on the team.

Our goal is not to create a deliverable or a feature: it’s to positively affect customer behavior or change in the world — to create an outcome.

If you focus on the strength of the team, you will begin to find work as a positive challenge.

A good manager focuses on managing impediments, process, team’s health, protects the boundaries of self-organizing teams, promotes a healthy culture, and helps eliminate waste.

Good agile project managers and teams don’t focus on mistakes — or on who did them, or on how many times they were done.

We choose and wear our clothes every morning. Attitude is the same. Positivity is an attitude – we can choose to wear it every morning

Intrinsically we humans want to be happy, and happiness derives from having purpose, pursuit towards interesting and challenging ‘something’ that is greater than oneself.

Stubbornness pays! We tend to think that it doesn’t, we might be hesitant to be stubborn – however only the stubborn succeed.

It appears evident that, for the average team, insisting on writing tests first, before functional coding, improves quality.

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

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.

A job interview is a two-way communication to probe for cultural and team fit. No matter which side of the table you sit, you should be asking questions that are important to you without fear.

stress can be a real monster you have to vanquish from your team. And one of the main ways to do this is by ensuring that you plan your project in a very sustainable way, from the very beginning.

Frame your problem statements into actionable tasks and goals that lead to a solution. Problem statements incite procrastination and resistance whereas solution statements inspire hope and motivation.

Situational leadership articulates that effective leaders are the ones able to change their behavior according to the situation at hand. It identifies leadership styles relevant to specific situations.

Summary of Scrum vs Kanban Similarities: - Both are Lean and Agile - Both use pull scheduling - Both limit WIP - Both use transperency to drive process improvement - Both focus on delivering releasable software and often - Both are based on self-organizing teams - Both require breaking the work into pieces. - In both, the release plan is continuously optimized based on empirical data (velocity/lead time)

A maxim in the theater tells us this: On time is already late (Devin 2009). That is, if we arrive at work on time with our bodies only, having not groomed our minds to collaborate, we are simply late. Unprepared.

The more I recognized these tactical styles, the more I saw the ideal as a balance. Despite the contradiction, a recon [team leader] had to be part wolf and part rabbit--selectively bold or cautious--but few men can agilely switch back and forth.

Agile project leaders help their team balance at the edge of chaos—some structure, but not too much; adequate documentation, but not too much; some up-front architecture work, but not too much. Finding these balance points is the "art" of agile leadership.

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.

First, how could I protect my team from the incessant demands of the business and achieve what the Agile community now refers to as a “sustainable pace”? And second, how could I successfully scale adoption of an Agile approach across an enterprise and overcome the inevitable resistance to change?

I noticed a bumper sticker that said, simply, "gravity works." yes it does. Rock climbers know this and plan for it. So do agile coaches. I use this metaphor to illustrate that, in our physical environment, somethings are simply taken as a given. Constant. Always present. Undeniable. So, too, in our work environment.

For an agile project, the ensemble includes core team members, customers, suppliers, executives, and other participants who interact with each other in various ways. It is these interactions, and the tacit and explicit information exchanges that occur within them, that project management practices need to facilitate.

Only experience can refine a leader's art. High-uncertainty projects are full of anxiety, change, and ambiguity that the team must deal with. It takes a different style of project management, a different pattern of team operation, and a different type of project leader. I've labeled this type of management leadership-collaboration.

One of the kindest services a scrum master can do for his or her team and for the organization as a whole is to create transparency—to radiate information. Transparency allows us to see flaws, and when we see the flaws we can make the choice to do something about them. We can stop being victims of process and start being warriors of change.

In a self-organized team, individuals take accountability for managing their own workload, shift work among themselves based on need and best fit, and take responsibility for team effectiveness. Team members have considerable leeway in how they deliver results, they are self-disciplined in their accountability for those results, and they work within a flexible framework.

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.

The capability of self-organizing teams lies in collaboration. When two engineers scratch out a design on a whiteboard, they are collaborating. When team members meet to brainstorm a design, they are collaborating. When team leaders meet to decide whether a product is ready to ship, they are collaborating. The result of any collaboration can be categorized as a tangible deliverable, a decision, or shared knowledge.

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.

a good set of questions to determine whether a project leader—or even an individual contributor—has an agile mindset might be, "In what specific ways and with what practices do you focus on value first and constraints last?" "In what specific ways and with what practices do you manage teams rather than tasks?" "In what specific ways and with what practices do you adapt to change rather than conform to plans?" Try these out in your organization to get a feel for your agile maturity.

Outcomes indicators include product vision, business objectives, and capabilities (high-level product functionality), not detail requirements. These outcome characteristics define a releasable product and quality objectives define a reliable and adaptable (works today, easy to enhance) product. These are the critical value traits, then teams need to strive to meet constraints—scope, schedule, and cost—but as secondary in importance to the value components. In many, if not most, agile projects schedule becomes the most critical constraint and is timeboxed (fixed) and scope varies.

Authoritarian managers use power, often in the form of fear, to get people to do something their way. Leaders depend for the most part on influence rather than power, and influence derives from respect rather than fear. Respect, in turn, is based on qualities such as integrity, ability, fairness, truthfulness—in short, on character. Leaders are part of the team, and although they are given organizational authority, their real authority isn't delegated top-down but earned bottom-up. From the outside, a managed team and a led team can look the same, but from the inside they feel very different.

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.

we had to unlearn a great deal of what we thought we knew about how war—and the world—worked. We had to tear down familiar organizational structures and rebuild them along completely different lines, swapping our sturdy architecture for organic fluidity, because it was the only way to confront a rising tide of complex threats. Specifically, we restructured our force from the ground up on principles of extremely transparent information sharing (what we call “shared consciousness”) and decentralized decision-making authority (“empowered execution”). We dissolved the barriers—the walls of our silos and the floors of our hierarchies—that had once made us efficient. We looked at the behaviors of our smallest units and found ways to extend them to an organization of thousands, spread across three continents. We became what we called “a team of teams”: a large command that captured at scale the traits of agility normally limited to small teams.

SEVEN CHANGE MASTERY SHIFTS • Change Mastery Shift 1: From Problem Focus to Opportunity Focus. Effective leaders tend to perceive and to innovate on the opportunities inherent in change. • Change Mastery Shift 2: From Short-Term Focus to Long-Term Focus. Effective leaders don’t lose sight of their long-term vision in the midst of change. • Change Mastery Shift 3: From Circumstance Focus to Purpose Focus. Effective leaders maintain a clear sense of purpose, value, and meaning to rise above immediate circumstances. • Change Mastery Shift 4: From Control Focus to Agility Focus. Effective leaders understand that control is a management principle that yields a certain degree of results. However, agility, flexibility, and innovation are leadership principles that sustain results over the long haul. • Change Mastery Shift 5: From Self-Focus to Service. Effective leaders buffer their teams and organizations from the stress of change by managing, neutralizing, and/or transcending their own stress. • Change Mastery Shift 6: From Expertise Focus to Listening Focus. Effective leaders stay open and practice authentic listening to stay connected with others and to consider multiple, innovative solutions. • Change Mastery Shift 7: From Doubt Focus to Trust Focus. Effective leaders are more secure in themselves; they possess a sense that they can handle whatever may come their way; their self-awareness and self-trust are bigger than the circumstances of change.

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.

Bram stared into a pair of wide, dark eyes. Eyes that reflected a surprising glimmer of intelligence. This might be the rare female a man could reason with. “Now, then,” he said. “We can do this the easy way, or we can make things difficult.” With a soft snort, she turned her head. It was as if he’d ceased to exist. Bram shifted his weight to his good leg, feeling the stab to his pride. He was a lieutenant colonel in the British army, and at over six feet tall, he was said to cut an imposing figure. Typically, a pointed glance from his quarter would quell the slightest hint of disobedience. He was not accustomed to being ignored. “Listen sharp now.” He gave her ear a rough tweak and sank his voice to a low threat. “If you know what’s good for you, you’ll do as I say.” Though she spoke not a word, her reply was clear: You can kiss my great woolly arse. Confounded sheep. “Ah, the English countryside. So charming. So…fragrant.” Colin approached, stripped of his London-best topcoat, wading hip-deep through the river of wool. Blotting the sheen of perspiration from his brow with his sleeve, he asked, “I don’t suppose this means we can simply turn back?” Ahead of them, a boy pushing a handcart had overturned his cargo, strewing corn all over the road. It was an open buffet, and every ram and ewe in Sussex appeared to have answered the invitation. A vast throng of sheep bustled and bleated around the unfortunate youth, gorging themselves on the spilled grain-and completely obstructing Bram’s wagons. “Can we walk the teams in reverse?” Colin asked. “Perhaps we can go around, find another road.” Bram gestured at the surrounding landscape. “There is no other road.” They stood in the middle of the rutted dirt lane, which occupied a kind of narrow, winding valley. A steep bank of gorse rose up on one side, and on the other, some dozen yards of heath separated the road from dramatic bluffs. And below those-far below those-lay the sparkling turquoise sea. If the air was seasonably dry and clear, and Bram squinted hard at that thin indigo line of the horizon, he might even glimpse the northern coast of France. So close. He’d get there. Not today, but soon. He had a task to accomplish here, and the sooner he completed it, the sooner he could rejoin his regiment. He wasn’t stopping for anything. Except sheep. Blast it. It would seem they were stopping for sheep. A rough voice said, “I’ll take care of them.” Thorne joined their group. Bram flicked his gaze to the side and spied his hulking mountain of a corporal shouldering a flintlock rifle. “We can’t simply shoot them, Thorne.” Obedient as ever, Thorne lowered his gun. “Then I’ve a cutlass. Just sharpened the blade last night.” “We can’t butcher them, either.” Thorne shrugged. “I’m hungry.” Yes, that was Thorne-straightforward, practical. Ruthless. “We’re all hungry.” Bram’s stomach rumbled in support of the statement. “But clearing the way is our aim at the moment, and a dead sheep’s harder to move than a live one. We’ll just have to nudge them along.” Thorne lowered the hammer of his rifle, disarming it, then flipped the weapon with an agile motion and rammed the butt end against a woolly flank. “Move on, you bleeding beast.

Ellen Braun, an accomplished agile manager, noticed that different behaviors emerge over time as telltale signs of a team’s emotional maturity, a key component in their ability to adjust as things happen to them and to get to the tipping point when “an individual’s self interest shifts to alignment with the behaviors that support team achievement” (Braun 2010). It is better to know some of the questions than all of the answers. —James Thurber Team Dynamics Survey Ellen created a list of survey questions she first used as personal reflection while she observed teams in action. Using these questions the same way, as a pathway to reflection, an agile coach can gain insight into potential team problems or areas for emotional growth. Using them with the team will be more insightful, perhaps as material for a retrospective where the team has the time and space to chew on the ideas that come up. While the team sprints, though, mull them over on your own, and notice what they tell you about team dynamics (Braun 2010). • How much does humor come into day-to-day interaction within the team? • What are the initial behaviors that the team shows in times of difficulty and stress? • How often are contradictory views raised by team members (including junior team members)? • When contradictory views are raised by team members, how often are they fully discussed? • Based on the norms of the team, how often do team members compromise in the course of usual team interactions (when not forced by circumstances)? • To what extent can any team member provide feedback to any other team member (think about negative and positive feedback)? • To what extent does any team member actually provide feedback to any other team member? • How likely would it be that a team member would discuss issues with your performance or behavior with another team member without giving feedback to you directly (triangulating)? • To what extent do you as an individual get support from your team on your personal career goals (such as learning a new skill from a team member)? • How likely would you be to ask team members for help if it required your admission that you were struggling with a work issue? • How likely would you be to share personal information with the team that made you feel vulnerable? • To what extent is the team likely to bring into team discussions an issue that may create conflict or disagreement within the team? • How likely or willing are you to bring into a team discussion an issue that is likely to have many different conflicting points of view? • If you bring an item into a team discussion that is likely to have many different conflicting points of view, how often does the team reach a consensus that takes into consideration all points of view and feels workable to you? • Can you identify an instance in the past two work days when you felt a sense of warmth or inclusion within the context of your team? • Can you identify an instance in the past two days when you felt a sense of disdain or exclusion within the context of your team? • How much does the team make you feel accountable for your work? Mulling over these questions solo or posing them to the team will likely generate a lot of raw material to consider. When you step back from the many answers, perhaps one or two themes jump out at you, signaling the “big things” to address.

While a team’s deliverable is the product, a scrum master’s deliverable is a high-performing, self-organizing team.

Individuals should be given every incentive possible to work as a team. If the team’s throughput is increased by my helping someone else, that’s what I should do. Team velocity matters; individual velocity doesn’t.

It has been said that because we have been given two ears and only one mouth, we should listen twice as much as we talk. Listening is an art form, and asking questions is a tool to active listening.

the team structure works well for us because it is well-aligned with our culture, our technical architecture and platform, our product, and even our workspace.

DevOps simply adds the idea that small, cross-functional teams should own the entire delivery process from concept through user feedback and production monitoring.

heard things like “DevOps is the new Agile,” “Lean doesn’t apply to software delivery,” “Of course this worked for the mobile app team. They are a unicorn.

The leadership team would then spend most of their days walking the floor trying to understand where we were struggling and why. This is a new role for most executives and one we encourage executives to embrace if this process is going to be successful. We

This book lays a lot of emphasis on having teams responsible for business outcomes (outcome-oriented teams) as opposed to being responsible for activities (activity-oriented teams). To

all team members as well as passers-by can see the latest information at a glance: count of automated tests, velocity, incident reports, continuous integration status, and so on. This

Some of the same forces have come to bear in the business world, where many companies in thriving talent-dependent industries embraced a new workplace ethos in which hierarchies were softened and office floor plans were reengineered to break down the walls that once kept management and talent separated. One emerging school of thought, popular among technology companies in Silicon Valley, is that organizations should adopt “flat” structures, in which management layers are thin or even nonexistent. Star employees are more productive, the theory goes, and more likely to stay, when they are given autonomy and offered a voice in decision-making. Some start-ups have done away with job titles entirely, organizing workers into leaderless “self-managing teams” that report directly to top executives. Proponents of flatness say it increases the speed of the feedback loop between the people at the top of the pyramid and the people who do the frontline work, allowing for a faster, more agile culture of continuous improvement. Whether that’s true or not, it has certainly cleared the way for top executives to communicate directly with star employees without having to muddle through an extra layer of management. As I watched all this happen, I started to wonder if I was really writing a eulogy. Just as I was building a case for the crucial value of quiet, unglamorous, team-oriented, workmanlike captains who inhabit the middle strata of a team, most of the world’s richest sports organizations, and even some of its most forward-thinking companies, seemed to be sprinting headlong in the opposite direction.

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

work can bounce between teams endlessly due to incomplete information, or work can be passed onto downstream work centers with problems that remain completely invisible until we are late delivering what we promised to the customer or our application fails in the production environment.

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. ††

To mitigate these types of problems, we strive to reduce the number of handoffs, either by automating significant portions of the work or be reorganizing teams so they can deliver value to the customer themselves, instead of having to be constantly dependent on others.

Broadly speaking, to acheive DevOps outcomes, we need to reduce the effects of functional orientation ("optimizing for cost") and enable market orientation ("optimizing for speed") so we can have many small teams working safely and independently, quickly delivering value to the customer

limit on [team] size ... ensures the team has a clear, shared understanding of the system they are working on. As teams get larger, the amount of communication required for everybody to know what's going on scales in a combinatorial fashion.

Another way we can enable more market-oriented outcomes is by enabling product teams to become more self-sufficient by embedding Operations engineers within them, thus reducing their reliance on centralized Operations.

Instead of project teams where developers are reassigned and shuffled around after each release, never receiving feedback on their work, we keep teams intact so they can keep iterating and improving, using those leanings to better achieve their goals.

When Dev teams had problems with testing or deployment, they needed more than just technology or environments. What they also needed was help and coaching. At first, we embedded Ops engineers and architects into each of the Dev teams, but there simply weren’t enough Ops engineers to cover that many teams. We were able to help more teams with what we called an Ops liaison model and with fewer people.

Agile software development needs teams to be motivated. But repetitive tasks are boring, not motivating, so they should be automated. Many

In an Agile context, tools are meant to strengthen motivation, communication, and collaboration in a team.

For a long time, the German shepherd was the standard bearer for work in law enforcement and the military, but for many reasons, including practicality, the breed has been surpassed by the Malinois. Among the factors in favor of the Malinois are size and resiliency. While the Malinois has nothing on the German shepherd when it comes to brainpower or strength, it does have the advantage of being a smaller and more agile breed. the Belgian Malinois is built for military work, and especially for the sort of job commonly undertaken in Special Operations. While either breed can reliably detect the presence of explosives or a human target in hiding, the Malinois is quicker and stabler, simply by virtue of it's smaller and more compact musculature. It is better suited to traversing uneven terrain, and, when necessary, more easily transported.

The Scrum Master’s job is to help the organization and the Scrum Team use Scrum properly to improve their ability to deliver value.

Smart decisions reflect diverse opinions across disciplines, experiences, and outcomes. In today's collaborative mindset culture, teams strive to optimize each of these inputs. We listen to everyone's input and respond to it. We seek to bring everyone along. Everyone is treated as having an equal voice in the decision. Agility is compromised when people believe they need to make decisions together. In the end, the process is exhausting, and the decision is vanilla.

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.

In a leader-nurturing culture, people can build psychological safety, the single most important ingredient of a high-performing team.

Choose activities that support the goal of the retrospective. If there’s no way to discuss the activity that makes a connection between the activity and the work, omit it. We’re not against games and simulations—in fact we use them often—when they serve a purpose and move the retrospective forward. Icebreakers, energizers, and games that don’t relate to the work don’t fit in retrospectives. There’s only so much time, so don’t waste it with activities that are “just for fun.” Have fun, but have a purpose.

Once again, the proxy variables of “number of people trained on the Agile process” or “deploys per day” will only be meaningful if training or deployment are the bottleneck. But when the business is disconnected from IT, the Agile teams and DevOps pipeline never get the opportunity to become the bottleneck.

less. All the work to create value happens within a sprint.

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.

In traditional performance management models, working teams present to leadership in performative, high-stakes monthly or quarterly reviews. By keeping these reviews on such an infrequent cadence, both sides can lose sight of what the real purpose of the review is: to support and sustain the work, and to ensure that everyone is moving together toward the desired results. Such an approach is ill-suited to the ecosystem economy. When you have agile tribes, chapters, and squads working on dynamic, cross-sectoral value propositions, you need to push your performance management process toward a much more frequent operating cadence.

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