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.
My Life as an Architect in Tokyo
World renowned architect Kengo Kuma presents an enlightening tour of Tokyo, expressing his personal thoughts and reflections on the city's most influential buildings and its rich architectural heritage.
A collection of villages
I became a 'border person', as defined by the sociologist and philosopher Max Weber, viewing Tokyo from an outsider's perspective. Observing the city while walking around its streets enabled me to discover a wide variety of location, cultures and people, and that Tokyo is a collection of small villages, rather than one big city.
...When I design a building in any city, I believe that the world is a collection of villages, instead of a group of nations.
Low wooden silhouettes
While [Kenzo] Tange aspired to verticality, we looked to horizontality, believing that pre-1964 Tokyo, with its low wooden silhouettes, was a better model for the city of the future.
Occupied by a void
Roland Barthes wrote that the centre of Tokyo is occupied by a void...it is a quiet forest that lies at Tokyo's heart.
...The centre of Tokyo is certainly a void, but one that is protected by a circular train line, the Yamanote, which forms a 40-km (25-mile) loop around it. It seems to me that this ring of steel emphasizes the importance of the void, and the depth of its significance.
Such an enormous machine
In cities across the world, industrial zones beside rivers and canals have become the focus of attention, with their unique vivacity associated with places where things are made.
...Because the area is designated as a semi-industrial zone, we were able to get away with such an enormous machine inside [the Starbucks Reserve Roastery].
A more spiritual place
In the centre of the forest is the sandō, leading up to the shrine. It follows an L-shaped curve, and is very different to the straight processional pathways found in religious buildings in the West or in China. Curves ensure that the view changes constantly, helping visitors make the transition to a deeper, more spiritual place.
The building as less important than the path
In the design of Japanese tea houses, the building is seen as less important than the path (roji) leading up to it, and tea masters of the past believed that the journey along the roji allowed participants to better immerse themselves in the slow time of the tea ceremony.
The gentle light of shoji screens
Le Corbusier, the greatest architect of the last century, noted that 'architecture is the learned game, correct and magnificent, of forms assembled in light', demonstrating to what extent light has been prioritized in the Western tradition. Tanizaki, on the other hand, spoke of the important of shadows, of extended eaves. Rather than the light that shines directly into a room, he praised the soft light that penetrates a space after being reflected off the floor, and again from the ceiling.
...In Japanese architecture, the gentle light that passes through shoji screens serves a key purpose. It reaches right to the back of the room, so that the space feels bright, even without the aid of artificial light. The soft light filtering through the white film at Takanawa Gateway Station represents a form of light that was forgotten about by Japanese Modernism.
The thin lip of a teacup
To give the building a sense of the delicacy associated with such crafts, as well as a feeling of warmth, I designed louvres from white porcelain panels, and used them to cover the outer walls. The louvres are tapered, to make their tips as fine as possible. (In fact, making tips as thin as possible is one of my key design principles: the thin lip of a teacup allows a better experience of the subtleties of tea - this is always at the forefront of my mind when I pay such close attention to edges.)
Skyscrapers are frowned upon
During the twentieth century, much importance was attached to things that were big and tall, but, as we moved into the twenty-first century, I felt that being big and tall had become embarrassing.
...Today, skyscrapers are frowned upon in Japan, and are seen as the product of the mistaken mindset that prevailed during the country is period of enhanced growth.
The Metabolist philosophy
Tange put Tsukiji as the centre of his plan, which now seems grandiose and delusional. His design for the Dentsu building had much in common with the Metabolist philosophy of the 1960s, which maintained that buildings needed to continually evolve in a flexible way.
...With [the Nakagin Capture Tower], Kurokawa's Metabolist philosophy was fully realized. After it was completed, however, it became almost impossible to switch over the capsules - indeed, since its completion, not one of the capsules has been moved. As a result, the Metabolist movement has been forgotten. Yet its core principles, which sought to draw architectural lessons from living organisms, has much inspiration to offer society today.
A city of hills
Many of the stations [on the Yamanote Line] have one entrance on the uphill side and another lower down, and the neighbourhoods around them have a totally different feel, depending on which exit you use to leave the station.
The hilly areas in Tokyo are mostly made up of quiet, well-to-do residential districts, while the lower sections often have more of a populist feel, with shopping arcades and small urban factories. As a result, the atmosphere outside the entrances are dramatically different in character. Take the wrong exit, and you might find yourself lost in a completely different kind of neighbourhood than you were expecting. In Tokyo, elite and working-class cultures exist alongside one another and mix together. I think the fundamental cause of this is the complexity of the city's topography.
...Tokyo is a city of hills, with most of it lying on an alluvial plain between the Tama and Kanda rivers. It is via these hills that the upland, elite neighbourhoods are connected with the more working-class areas down below. The slopes are thus a key part of the co-existence of these two worlds, used by people to come and go between them. Kagurazaka is particularly notable in this respect.
They can smell the wood
All of the wooden shelves used for storing books were on the warehouse's first floor. We decided to keep these shelves as they were to form a library, and we also created a small lecture hall for holding talks by writers and makers. Although contemporary society is moving away from books and towards computers and information technology, people nevertheless have a strong feeling of connection to – and nostalgia for – trees and things that are made from wood. La kagu is a space where visitors can really get a sense of the culture of books. When they step inside, some even say that they can smell wood.
As a kind of gateway
Historically, Japan's shrines have been built in order to worship the gods who live in the sacred mountains or seas; They don't reside in the shrine itself, but in the space beyond it. This belief that the spirits and deities exist beyond the confines of the shrine, and that the shrine itself acts not as a centre, but as a kind of gateway, is very different to the grand, imposing churches and cathedrals of Christianity.
The majority of shrines are not found in the mountains or in the middle of the fields, therefore, but at the borders of mountain villages – which is to say, at what is seen as the edge of the mountains. The tori gate, marking the entrance to a shrine, indicates that there are gods on the other side of it.
The golden poo
On the opposite bank of the Sumida River lies the Asahi Beer headquarters (1989), a strange building with a golden sculpture mounted on top of a granite-plated black box. It was designed by Philippe Starck, and completed in 198g when the Japanese economy was still going strong. The sculpture, with no clearly defined use, is a clear representation of its time. Today, the building is known as the 'golden poo', a reference to the shape of its crowning object.
Like crossing the sea
The Sumida is a symbol of Tokyo, but is not like the Thames in London or the Seine in Paris, or other rivers that are woven into the geography of the city. Its banks were pushed back, so that the river became extremely wide and travelling across it feels liberating, like crossing the sea.
These thrown-away items
I decided to furnish the restaurant [Tetchan] with the kinds of discarded items one wouldn't normally use in interior design, from recycled LAN cables to acrylic by-products.
When using discarded objects in interior design, it gives even brand-new places the feeling that they have always been there. I think this is due to the inherent history of these thrown-away items, which lives on inside of them.
Kengo Kuma's sketches