Agile Design and Development
So that you can get feedback on it and make it better
The most rewarding iterations
Building is never a straight line
Product owner vs. product manager
A Product Owner is focused on output i.e. how quickly can we build these features?
Product Management, on the other hand, is focused on outcomes i.e. why are we building these features in the first place?
Good design is redesign
Good design is redesign. It's rare to get things right the first time. Experts expect to throw away some early work. They plan for plans to change.
It helps to have a medium that makes change easy. When oil paint replaced tempera in the fifteenth century, it helped painters to deal with difficult subjects like the human figure because, unlike tempera, oil can be blended and overpainted.
Finish designing as close to the end of a sprint as possible
The traditional process of delivering design, vs. delivering design just in time.
Designers are often working at least one sprint ahead of engineers. While one sprint might not seem like much of a lag, a typical product team learns a lot after the design hand-off. ...Instead of working ahead, we should finish designing as close to the end of a sprint as possible: just-in-time design.
We optimize what we measure
Scrum does not say “only focus on output”, but, unfortunately, humans will optimize for what they measure.
If you worry about story points & hitting your estimations, that’s what is going to consume your attention. That is what you and your team will optimize for.
And that is the core critique of Scrum as it is practiced: That it focuses a product team’s attention so heavily on delivery — on building lots of features quickly & efficiently — that teams fail to focus on spending time to discover what the right thing to build is.
How we can do better
It actually doesn't matter whether you actually have a formal retrospective. It doesn't matter whether you have four or five labels of things on your retro board, or exactly how you do the retro. What does matter is the notion of thinking about what we're doing and how we can do better, and it is the team that's doing the work that does this, that is the central thing.
The 'date scrum' anti-pattern
Date Scrum is an R&D pattern where developers are asked to estimate software project requirements upfront for the entirety of the project. After the project is green lighted and the budget is set based on the final estimates, the team then holds daily scrums to status and manage risk as they “iterate” the solution toward the release date. To some, this approach is described as doing Waterfall in sprints.
The fundamental problem with Date Scrum is that the team is de-focused from discovering the best solution. Instead they are heavily focused on delivering Something™ by the Date™. Engineers are problem solvers, and if the primary problem becomes delivering Something™ that will pass QA by the Date™, they will, with enough pressure, solve that exact problem.
That which requires caring
Today's real world of technology is characterized by the dominance of prescriptive technologies.
The temptation to design more or less everything according to prescriptive and broken-up technologies is so strong that it is even applied to those tasks that should be conducted in a holistic way. Any tasks that require caring, whether for people or nature, any tasks that require immediate feedback and adjustment, are best done holistically. Such tasks cannot be planed, coordinated, and controlled the way prescriptive tasks must be.
Prescriptive technologies eliminate the occasions for decision-making and judgment in general and especially for the making of principled decisions. Any goal of the technology is incorporated a priori in the design and is not negotiable.
Manifesto for Agile Software Development
A DefinitionWe are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Agile Scrum is not working
The Agile founders had it right, one size doesn't fit all. What the founders perhaps didn’t foresee, or couldn’t agree on, is that in order for the world to scale and consume their wisdom, it had to be packaged as concrete practices, not as abstract classes with virtual methods to be defined in context. And to the proponents of Agile Scrum, give them their due, for their part, they made it concrete – Agile Scrum has been packaged and delivered. Yet much work remains to realize the promise of Agile, which in summary is, the realization of wise use of lightweight development practices and workflows that flexibly adapt to the changing and evolving needs of customers.
Driving engineers to an arbitrary date is a value destroying mistake
An Article by Gandalf HudlowWhat happens when you apply date pressure to software engineers working on high value software projects? The engineers will focus on delivering Something™ by the Date™! This fatal flaw results in delivery of a Something™ full of chaos and features that nobody really wants or needs.
Beware SAFe, an Unholy Incarnation of Darkness
An Article by Sean DexterThe Lean Portfolio Management function that controls funding, are given sole authority to approve which Portfolio Epics move into each stream. Epics are not explanations about a problem that needs to be solved. They are pre-formed ideas about how best to solve those problems.
Right away we can see signs of the old-school mindset of viewing teams as a “delivery” function instead of a strategic one. The high level thinkers come up with ideas, and the low level doers execute on those ideas. Ignored is the possibility that those closest to the work might be best equipped to make decisions about it. Escaping from this misguided mindset is a core goal of Agile thinking that SAFe fails to remotely accomplish.
Why Scrum is killing your product
An Article by Henry LathamDesign Systems, Agile, and Industrialization
An Article by Brad FrostI’ve come to the conclusion that “enterprise web development” is just regular web development, only stripped of any joy or creativity or autonomy. It’s plugging a bunch of smart people into the matrix and forcing them to crank out widgets and move the little cards to the right.
In these structures, people are stripped of their humanity as they’re fed into the machine. It becomes “a developer resource is needed” rather than “Oh, Samantha would be a great fit for this project.” And the effect of all this on individuals is depressing. When people’s primary motivation is to move tickets over a column, their ability to be creative or serve a higher purpose are almost completely quashed. Interaction with other humans seems to be relegated to yelling at others to tell them they’re blocked.
Reading “AS PER THE REQUIREMENTS” in tickets makes me dry heave. How did such sterile, shitty language seep into my everyday work?
The value-destroying effect of arbitrary date pressure on code
An Article by Gandalf HudlowThe mandate from above is clear, just get it done! Avoid everything that's in the way: all advice, all expertise, all discovery efforts that detract from hitting the Date™!
What these organizations don't realize is that all software change can be modeled as three components: Value, Filler and Chaos. Chaos destroys Value and Filler is just functionality that nobody wants. When date pressure is applied to software projects, the work needed to remove Chaos is subtly placed on the chopping block. Work like error handling, clear logging, chaos & load testing and other quality work is quietly deferred in favor of hitting the Date™.
Agile is Dead (Long Live Agility)
An Article by Dave ThomasThe word “agile” has been subverted to the point where it is effectively meaningless, and what passes for an agile community seems to be largely an arena for consultants and vendors to hawk services and products.
…Let’s abandon the word agile to the people who don’t do things. Instead, let’s use a word that describes what we do. Let’s develop with agility.
- You aren’t an agile programmer—you’re a programmer who programs with agility.
- You don’t work on an agile team—your team exhibits agility.
- You don’t use agile tools—you use tools that enhance your agility.
/
Individuals and Interactions over Processes and Tools
Working Software over Comprehensive Documentation
Customer Collaboration over Contract Negotiation, and
Responding to Change over Following a PlanTraditional companies are losing because they mismanage software engineers
An Article by Emma WattersonInnovation is messy, and frankly Anti-Steve [Jobs] can’t figure out why you wouldn’t just tell people the right thing to build and skip all the trial and error that comes with innovation. Anti-Steve and his board of directors that keep him in place fundamentally believe that they know what needs to be built. Or at least that they can hire the messiah that will come down off the mountain and tell everyone what to build. There is no such messiah.
Why we stopped breaking down stories into tasks
An Article by Adam SilverThe Scrum process says to break down stories into tasks to make estimation easier, encourage collaboration and to be able to show more granular progress during a sprint.
But after a few sprints, we decided to do the next sprint without creating tasks. As a result we drastically increased our velocity and never went back. Here I'll jot down some of the reasons we decided to do this:
- Breaking down stories into tasks is time consuming
- The tasks we came up with invariably would change as we worked on the stories
- Tasks are repetitive
- Tasks were often carried out in parallel
- Our estimates didn't improve
- It decluttered our task board
- It encouraged collaboration throughout the sprint
While we started our process by following Scrum to the letter, we soon realised that breaking down stories into tasks was something that wasn’t worthwhile for us. In the end we realised that it was overplanning and poor use of our time. In the end we used that time to get on with the work and deliver at a significantly faster pace.
Why We Don't Do Daily Stand-Ups at Supercede
An Article by Jezen ThomasYesterday I worked on the widget.
Today I will work on the widget.
I have no blockers.Are you asleep yet? The developers are. You promise them an intellectually stimulating work environment and what they end up with is drudgery.
What value can be had from these meetings anyway? Using “alignment” for justification is so nebulous that it is essentially meaningless. Engineers align themselves. They talk. Especially if you hire good ones (which, you know, you’ll struggle to if you have a culture of coercing them into this kind of busywork). Where does the real discussion happen? It’s written down.
Software that nobody wants
An Article by Gandalf HudlowFinding value is the result of enabling individual and group-level discovery attempts. It's not the result of everyone following one leader's gut.
What just happened is a new software product/feature was created that no customer wanted. This happens way too often. In fact, most hyper important software projects that must be done by date certain or else, have deep flaws that cause some variation of this phenomenon, flaws that include:
- Not wanted - Company specified a solution to a problem that customers don't actually have
- No Rarity - Company is pursuing an iKnockoff of existing products. The market already has two scaled competitors with working solutions, customers naturally spend budget on products that are already successful to avoid risk
- Incorrect Packaging - Customers need a website, but the company created an iOS app instead
- Incorrect Pricing - Customers need SaaS pricing, but the company created a shrink wrapped, on-premise solution with CapEx and maintenance agreements instead
Making sense of MVP
An ArticleHenrik Kniberg:
The top scenario (delivering a front tire) sucks because we keep delivering stuff that the customer can’t use at all. If you know what you’re doing – your product has very little complexity and risk, perhaps you’ve built that type of thing hundreds of times before – then go ahead and just do big bang. Build the thing and deliver it when done.
Doing It Right
An Article by Brad FrostDoing it right requires a different pace of working and a much broader thought process than “ok, let’s get this thing out the door.” Which is super tough because most workplaces place a huge emphasis on getting things out the door, and fast. Little agile tickets that are expected to be completed in micro sprints to me seem to be antithetical to doing it right.
Planning doesn't make for better software
A Fragment by Robin RendleMy own time in a Silicon Valley startup has proved this much to be true; planning doesn’t make for better software. In fact today our design systems team doesn’t have sprints, we don’t have tickets or a daily standup. Each day we come to work, figure out what’s the most important thing that we could be doing, and then we—gasp!—actually do it.
Watching so many other teams slowly flail about whilst they plan for quarter 3.2 of subplan A, whilst our team produces more work in a week than they all do combined in a quarter has been shocking to me.
After four years of working in a large startup, I know what I always assumed was true: you don’t need a plan to make a beautiful thing. You really don’t. In fact, there’s a point where overplanning can be a signal of inexperience and fear and bullshit. The scrum board and the sprints and the inane meetings each and every day are not how you build another Super Mario 64.
Instead all you have to do is hire smart people, trust them to do their best work, and then get the hell out of their way.
Agile as Trauma
An Essay by Dorian TaylorThe Agile Manifesto is an immune response on the part of programmers to bad management.
Yagni
A Definition by Martin FowlerYagni originally is an acronym that stands for "You Aren't Gonna Need It". It is a mantra from Extreme Programming that's often used generally in agile software teams. It's a statement that some capability we presume our software needs in the future should not be built now because "you aren't gonna need it".
The State of Agile Software in 2018
A Talk by Martin FowlerOn the surface, the world of agile software development is bright, since it is now mainstream. But the reality is troubling, because much of what is done is faux-agile, disregarding agile's values and principles. The three main challenges we should focus on are: fighting the Agile Industrial Complex and its habit of imposing process upon teams, raising the importance of technical excellence, and organizing our teams around products (rather than projects).
Product vs. Feature Teams
An Article by Marty CaganThis article is certain to upset many people.
The Shape of Design
Near and far
The creative process, in essence, is an individual in dialogue with themselves and the work. The painter, when at a distance from the easel, can assess and analyze the whole of the work from this vantage. He scrutinizes and listens, chooses the next stroke to make, then approaches the canvas to do it. Then, he steps back again to see what he’s done in relation to the whole. It is a dance of switching contexts, a pitter-patter pacing across the studio floor that produces a tight feedback loop between mark-making and mark-assessing. The artist, when near, is concerned with production; when far, he enters a mode of criticism where he judges the degree of benefit (or detriment) the previous choice has had on the full arrangement.
Painting’s near and far states are akin to How and Why: the artist, when close to the canvas, is asking How questions related to craft; when he steps back, he raises Why questions concerned with the whole of the work and its purpose. Near and Far may be rephrased as Craft and Analysis, which describe the kinds of questions the artist asks while in each mode. This relationship can be restated in many different ways, each addressing a necessary balance:
- How and Why
- Near and Far
- Making and Thinking
- Execution and Strategy
- Craft and Analysis
Why we should read
Unfortunately, the program met its end because the show’s approach opposed the contemporary standard format of children’s television: teaching kids how to read, rather than Reading Rainbow’s objective, which was to teach kids about why they should read.
Reading Rainbow had a long run, lasting twenty-three years, but its cancellation feels like a symbolic blow. Education, just like climbing the ladder, must be balanced between How and Why. We so quickly forget that people, especially children, will not willingly do what we teach them unless they are shown the joys of doing so. The things we don’t do out of necessity or responsibility we do for pleasure or love; if we wish children to read, they must know why.
We hear a voice whisper
The Shakers have a proverb that says, “Do not make something unless it is both necessary and useful; but if it is both, do not hesitate to make it beautiful.” We all believe that design’s primary job is to be useful. Our minds say that so long as the design works well, the work’s appearance does not necessarily matter. And yet, our hearts say otherwise. No matter how rational our thinking, we hear a voice whisper that beauty has an important role to play.
Needs more love
He held the phone to his chest, looked at me, and simply said, “Needs more love.” He pushed the portfolio back across his desk, smiled warmly, and shooed me out of his office.
I still think about this advice, and what exactly he might have meant when he said my work needed more love. At the time, I took it to mean that I should improve my craft, but I’ve come to realize that he was speaking of something more fundamental and vital. My work was flat, because it was missing the spark that comes from creating something you believe in for someone you care about. This is the source of the highest craft, because an affection for the audience produces the care necessary to make the work well.
One candle can light another
Lighting one candle
with another candle—
spring evening.Buson is saying that we accept the light contained in the work of others without darkening their efforts. One candle can light another, and the light may spread without its source being diminished.
A great leap of lightness
The first step of any process should be to define the objectives of the work with Why-based questions. The second step, however, should be to put those objectives in a drawer. Objectives guide the process toward an effective end, but they don’t do much to help one get going. In fact, the weight of the objectives can crush the seeds of thought necessary to begin down an adventurous path.
The creative process, like a good story, needs to start with a great leap of lightness, and that is only attainable through a suspension of disbelief. The objectives shouldn’t be ignored forever, but they should be defined ahead of time, set aside, and then deployed at the appropriate moment so that we may be audacious with our ideas.
Going evil
To begin, we must build momentum and then reintroduce the objectives to steer the motion. I find the best way to gain momentum is to think of the worst possible way to tackle the project. Quality may be elusive, but stupidity is always easily accessible; absurdity is fine, maybe even desired. If the project is a business card for an optician, perhaps you imagine it is illegible. (This is in the spirit, but you can do better.) If it is a brochure for an insurance agency, imagine otters on the cover and deranged handwriting on the inside for the copy. (Further!) If it is design for an exhibition of Ming Dynasty vases, brand it as an interactive show for kids, and put the vases on precariously balanced pedestals made of a shiny metal that asks to be touched. (Yes!)
The important realization to have from this fun—though fruitless–exercise is that every idea you have after these will be better. Your ideas must improve, because there is no conceivable way that you could come up with anything worse.
The momentum of making
Limitations narrow a big process into a smaller, more understandable space to explore. It’s the difference between swimming in a pool and being dropped off in the middle of the ocean with no land in sight. Those limitations also become the basis for the crucial first steps in improvisation. After those, the momentum of making accelerates as ideas are quickly generated without judgment.
Let the body wander
If the mind needs to wander, best let the body do the same. A short walk is more effective in coming up with an idea than pouring all the coffee in the world down your gullet.
Message, tone, format
All design work seems to have three common traits: there is a message to the work, the tone of that message, and the format that the work takes. Successful design has all three elements working in co-dependence to achieve a whole greater than the sum of the individual parts.
Asking why
Most inventions are recombinations of existing things, but where do the sparks for those combinations come from? What instigates that magic to make hybrids, to use them for unimagined purposes, and to inspire new settings for the three levers? Certain advancements seem logical and inevitable—smaller cellphones, faster computers, more reliable medical technology—while others seem to come out of nowhere. Turning avocado into caviar, for example, is not a logical conclusion in the kitchen. That choice is an inspired one. You can always spot these brilliant inventions as instances of magic, because our reaction, much like Achatz’s first meal at elBulli, is always disbelief.
Henry Ford famously said that if he had asked his customers what they wanted, they would have said a faster horse. Of course, we know that the faster horse is a testament to the limited imagination of customers, but I’d suggest that it’s more representational of not reassessing the objectives of the work in light of new opportunities. The faster horse is a recombination of the three levers in a predictable way: the customer’s answer is staunchly loyal to the horse, the already established format of transportation. They are inside of the adjacent possible, and ask a How question: How can horses be better?
Asking a Why question leads us to a different conclusion: Why are horses important? Because they quickly and reliably get us from one place to another. A Why question defines our need and uses an objective to create a satisfactory outcome for the work. This type of question is specific enough to be observable, but flexible enough to be approached in a variety of different ways. It’s easy to think that the way to improve life is to iterate on the things that we already have, but that is a trap of limited imagination. We should be iterating on how we answer our needs, and not necessarily on the way our old solutions have taken shape. The root of our practice is located in the usefulness of the work, not the form that it takes.
Outcomes and consequences
The primary purpose of the design is to have it do something particular, not be any particular thing. All of this implies that design is a field of outcomes and consequences more than one of artifacts. The forms that designers produce are flexible, so long as the results serve the need.
The source of delight
Design doesn’t need to be delightful for it to work, but that’s like saying food doesn’t need to be tasty to keep us alive. The pedigree of great design isn’t solely based on aesthetics or utility, but also the sensation it creates when it is seen or used. It’s a bit like food: plating a dish adds beauty to the experience, but the testament to the quality of the cooking is in its taste. It’s the same for design, in that the source of a delightful experience comes from the design’s use.
Every exit is an entrance somewhere
At the Ace Hotel in New York, a required exit sign over a door was an eyesore, and a stark contrast from the considered, detailed wall where it was mounted. Rather than accept the wart as it was, the sign was embraced as a chance to create an experience for the hotel’s guests by integrating the exit sign into the space. Now, surrounding the sign are other letters painted on the wall in a similar condensed style.
Every requirement is an opportunity for delight, even the ugly ones. Sometimes the creative treatment of these warts are the most enjoyable parts of a design.