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.
Dieter Rams: As Little Design as Possible
Beyond improvement
In so many ways Dieter Rams’s work is beyond improvement. Although new technologies have since offered new opportunities, his designs are not undermined by the limits of the technologies of their time. The concave button top, designed to stop your finger from slipping as it made the long travel necessary for earlier mechanical switches, does not point to obsolete mechanisms. Instead, it reminds us how immediately and intuitively form alone can describe what an object does and suggest how we should use it.
Cardinal sin
Indifference towards people and the reality in which they live is actually the one and only cardinal sin in design.
The duty of industrial design is first and foremost to users and the users are, generally, human beings, with all their complexities, habits, ideas and idiosyncrasies.
On display
The SK4 record player, aka 'Snow White's Coffin'.
Instead of being hidden away in a piece of furniture, the controls and the functional aspects of the device were not only on display, but they were the predominant feature of the design.
Rams suggested making a transparent lid from a new plastic that had just come on the market and was being used for advertising displays. It was an inspired thought and lent the phonograph just the lightness needed to balance the metal and wood of the base, as well as helping to define the acoustics. It also set the standard for all record players that followed - a turntable without a Perspex dust cover is now almost unthinkable.
Long-term
"Apart from his own design work, this is the second greatest achievement of Dieter Rams: establishing a design department within a company, which succeeded for decades in preserving its own individual approach and rigorously advancing it, without really being influenced by changing market interests." — Klaus Kemp
He is right; it was a remarkable feat. It takes a considerable degree of doggedness and conviction to follow the ungratifying and difficult path of insisting on a consistently long-term view in a corporate world that is constantly shifting and full of short-term decisions.
Humble servants
Our electrical appliances should be humble servants, to be seen and heard as little as possible. They should ideally stay in the background, like a valet in the old days, that one hardly noticed. — Erwin Braun
They should accompany an individual over a long period of time without hindering or disturbing through ‘extravagant forms, loud colors or flashy proportions’.
Restrained beauty
Braun design had a beauty that was more than skin deep. It would be wrong to say that because the Braun approach spurned fashion in an ongoing quest for functional and useable perfection, it ended up with this beauty by accident. There is a very strong aesthetic sense in both the proportion and materials of nearly all the products of the Rams era. They have a ‘restrained beauty’, he admits.
Braun products designed by Rams and his team have a haptic aesthetic as well: when you pick them up, handle them, and use them as the tools they are supposed to be, you become aware of the effort that has gone into making them sit comfortably in the hand, of the texture, weight and balance they possess, and of the satisfying click of the control buttons.
Camels
When you look at the consumer products generated by many other manufacturers, and even by Braun today, there seem to be an awful lot of camels around. Maybe these companies are too diffuse, have the decision-makers in the wrong places or are continually making the wrong decisions and have no one to stop them. They make products with short-term goals in mind, seducing the eye of the buyer with fashionable colors, sensational curves or exotic surfaces. They may have external designers and, perhaps most significantly, the brand identity is defined by external marketing concerns, rather than design or user-related issues.
The lesson to learn from Braun is that allowing a consistent philanthropic design approach to define a company can be extremely successful if it is executed with discipline, flexibility and good timing combined with hard work and, not least, great talent.
A timeless quality
Of all Rams’s products, the 606 Universal Shelving System is perhaps his most successful in fulfilling his own principles of good design. It is still in production today, some fifty years after its conception. The system is distinctive yet unobtrusive, and when the shelves and cabinets are filled, its slim profile allows it to fade quietly into the background.
Its ‘plainness’ lends it a timeless quality that has transcended the vagaries of fashion like no other of Rams’s designs. It was conceived in such a way as to optimize its function as simply and in as many different situations as possible, while still permitting upgrades and alterations without falling into obsolescence: all later adaptations and additions could still be integrated into the original structure and sizes.
"Fashion objects are not capable of being long-lived," said Rams in 2007. "We simply cannot afford this throw-away mentality anymore. Good design has to have built-in longevity. I believe that the secret of the longevity of my furniture lies in its simplicity and restraint. Furniture should not dominate, it should be quiet, pleasant, understandable and durable."
A certain kind of world
Perhaps more directly than with the Braun products, my furniture arose from a belief in how the world should be ‘furnished’ and how man should live in this artificial environment. In this respect, each piece of furniture is also a design for a certain kind of world and way of living, they reflect a specific vision of mankind.
Designing detail
My heart belongs to the details.
I actually always found them to be more important than the big picture.
Nothing works without details.
They are everything, the baseline of quality.Truly functional design only comes from the most careful and intense attention to detail.
Although he did not directly design all products and even had very little to do with some of them, he constantly encouraged tiny improvements that could make a good design better. This attention to detail ranged from the acuteness of angles in forms; the size, feels and distances between switches; the integration of handle fixings; the placement and nature of graphic elements on the products themselves and extended to product photography and packaging.
Designing detail is about achieving a fine balance in all aspects and areas of the product, including those external to the object.
Controlled!
Braun design is greatly reduced - stripped of all that is unnecessary. Nevertheless, there is a strong aesthetic characterized by balance, order and harmony.
Self-control is very important. Although my own taste is involved it always has to be under control. Not suppressed though! Controlled!
Chromatic mutiny
Nevertheless there were a number of colorful appliances produced by Braun, particularly from the late 1960s onwards, when plastics in bright primary colors became fashionable and available.
T3 domino lighter
KMM 2 coffee grinder
HLD 4 hairdryer
KF 145 coffee maker
HT 95 pop-up toasterWhen Rams’s team used color in such a way, it was uncompromising in its intensity: loud and demanding. The highly reduced forms of the products that it clothed, which had gently rounded edges, smooth opaque surfaces and discreet (usually black) detailing only served to increase this intensity.
"The intention was to create product alternatives for people who wished for strong color highlights in their living environments. This impulse came from marketing - not from design,” says Rams, dissociating himself from this approach. This was one instance where marketing got the upper hand in the decision-making process and the design team had to bow to contemporary fashion.
Indeed, there is a defiant aspect to these chromatic exceptions; they are not so much compromises as mutinous responses. Nevertheless, the resulting products are beautiful objects in their stand-alone way.
Color codes
When not compelled to do otherwise, the Braun design team’s use of color in products was reduced to highly specific areas such as control switches. Restricting the use of color to small points on an otherwise neutral object concentrates its effect, which is shifted away from decoration and towards function, especially when each color is assigned a signal role such as green for ‘on / off' switches, red for ‘fm’ and yellow for ‘phono’ on hi-fis or yellow for the second hand on clocks and watches.
This color coding of operating details is a primary example of the self-explanatory nature of Braun products.
Shorten the wings
The labile tastes of certain decision-makers in a company are often a great burden for designers. Too many feel themselves qualified to pass judgment. And how insensitive, how superficial these judgments often are.
Taste, believes Rams, is something that needs to be trained, since the aesthetic decisions at this level in product design are intrinsically bound to the entire form and function of the object. It would be unimaginable, for example, that the management of an aerospace company would ask the designers of a new plane to shorten the wings because they think it would make it look prettier.
The evolution of Braun design principles
1975
Three general rules govern every Braun design - a rule of order, a rule of harmony and a rule of economy.1976
The function for us is the starting point and the target of every design.
Experience with design is experience with people.
Only orderliness makes design useful to us.
Our design attempts to bring all individual elements into their proper proportions.
Good design means to us: as little design as possible.
Our design is innovative because the behavior patterns of people change.1983
Good design is innovative.
Good design renders utility to a product.
Good design is aesthetic design.
Good design makes a product easy to understand.
Good design is unobtrusive.
Good design is honest.1985
Good design is innovative.
Good design makes a product useful.
Good design is aesthetic.
Good design makes a product understandable.
Good design is honest.
Good design is unobtrusive.
Good design is long-lasting.
Good design is thorough down to the last detail.
Good design is environmentally friendly.
Good design is as little design as possible.Less, but better
There must be millions less of things, less words, less gestures, less of everything. But every word and every gesture will become more valuable. If we can put it all into perspective we will need less things as a result.