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.
- ââSteve Jobsââ
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.
Winning by Design: The Methods of Gordon Murray
A case study of the working methods of one particularly successful designer in a highly competitive design domain - Formula One racing car design. Gordon Murray was chief designer for the very successful Brabham and McLaren racing car teams in the 1970s and 1980s. His record of success is characterised by innovative breakthroughs, often arising as sudden illuminations, based on considering the task from first principles and from a systemic viewpoint. His working methods are highly personal, and include intensive use of drawings. Personality factors and team management abilities also appear to be relevant. There are some evident similarities with some other successful, innovative designers
You need to make the step forward
Throughout a racing season there is constant, relentless pressure on the designer to keep making design improvements. But there is a limit to what can be achieved with any car design, before a jump has to be made to basically a new design, an innovation. As Gordon Murray says, âGiven the situation and the pressure at any one time, you do get to the brick wall...I mean you're doing all these normal modifications, you know you can't go any quicker, you need to make the step forward.â
In the midst of the pressure, the fervour, the panic, he âused to get breakthroughs, I mean I used to get like suddenly a mental block's lifted.â
Drawing the bits
That's what is great about race car design, because even though you've had the big idea - the âlight bulbâ thing, which is fun - the real fun is actually taking these individual things, that nobody's every done before, and in no time at all try and think of a way of designing them. And not only think of a way of doing them, but drawing the bits, having them made and testing them.
Like designing things for the first time
Gordon Murray insists on keeping experience 'at the back of your mind, not the front' and to work from first principles when designing. For instance, in designing a component such as a suspension wishbone, 'it's all too easy - and the longer you're in design the easier it is - to say, I know all about wishbones, this is how it's going to look because that's what wishbones look like.' But if you want to make a step forward, if you're looking for ways of making it much better and much lighter, than you have to go right back to load path analysis. It is like designing things for the first time, rather than the nth time.
Wonder Plots
Working from first principles, and working in a highly organized way seem to come naturally to him, but his personal design process is much less structured than the results might suggest. Although he can tightly organize his team and run a complex racing organisation, his personal ways of designing are relatively unstructured, based on annotated, thumb-nail sketches. âI don't sit down and say, OK, now I've had the idea, let's see, this is a solution, these are the different ways to go, if I do this, and do that; I do lots of scribbles just to save it, before I forget.â
Gordonâs design process is based on starting with a quick sketch of a whole idea, which is then developed through many different refinements. âI do a quick sketch of the whole idea, and then if there's one bit that looks good, instead of rubbing other bits out, I'd put that bit to one side; I'd do it again and expand on the good bit, and drop out the bad bit, and keep doing it, doing it; and end up with all these sketches, and eventually you end up throwing ninety percent of these away.â He also talks to himself - or rather, writes notes to himself on the sketches; notes such as ârubbishâ, âtoo heavyâ or âmove it this way 30mm.â Eventually he gets to the stage of more formal, orthographic drawings, but still drawing annotated plans, elevations and sections all together, âUntil at the end of the day the guys at Brabham used to call them âWonder Plotsâ, because they used to say âIt's a wonder anybody could see what was on themâ!â
I never have engineers that aren't designers
Although Gordon Murray carried immense personal responsibility for the design work of his racing cars, inevitably it involved a lot of teamwork. Clearly he has been successful in inspiring others to work with him. He likes to involve team members in the design problems, and for that reason prefers to recruit all-rounders to his team; âI never have engineers that aren't designers.â
The problem with CAD
He also likes to work collectively, standing around a drawing board discussing problems and trying ideas.
For this kind of teamwork, and especially for conceptual design work, he finds computer aided design systems too restrictive. For the McLaren F1 super-car, he installed a five-metre long drawing board in the design office, so that the car could be drawn full size. âThe problem with CAD for this sort of stuff is that you can never have a full-size drawing, unless you do a print, and by the time you do a print it's out of date in the concept stage.â He also does not like the one-person emphasis of CAD screens; âYou can only ever talk to one person at once - you stand behind and look over somebody's shoulder, which is not very good for a boss-designer relationship anyway, to have somebody standing behind you is never a good thing. To look over somebody's shoulder at a tiny little screen, it's just wrong, it's totally wrong.â
(On the other hand, he fully acknowledges that tasks like a complex suspension plot to determine the wheel envelope are ideal for CAD.)
Drawing as a means of thinking
Two-dimensional plans or sections can be seen with sketches and more diagrammatic marks all on the same piece of paper in what appears a confusing jumble.â These sound like Gordonâs âwonder plotsâ. The architects also use their drawings as a means of thinking âaloudâ, or âtalking to themselvesâ, as Gordon put it. For example, Lawson reports the architect Richard MacCormac as saying, âI use drawing as a process of criticism and discoveryâ; and the engineer-architect Santiago Calatrava as saying, âTo start with you see the thing in your mind and it doesnât exist on paper and then you start making simple sketches and organizing things and then you start doing layer after layer.... it is very much a dialogue.â
The common elements in these similar descriptions are the use of drawing not only as a means of externalising cognitive images but also of actively âthinking by drawingâ, and of responding, layer after layer and view after view, to the design as it emerges in the drawings. These observations also confirm SchĂśnâs observation of designing as a âreflective conversationâ between the designer and the emerging design. It is the reliance on drawing, and the preference for the immediacy of the interaction and feedback that manual drawing gives, that makes the architects, like Gordon Murray, unenthusiastic about CAD as a conceptual design tool.
A new gestalt
The innovator has a systems mind, one that sees things in terms of how they relate to each other in producing a result, a new gestalt that to some degree changes the world.
Intense activity, then relaxation
The working style is based on periods of intense activity, coupled with other periods of more relaxed, reflective contemplation. This working style may not be a reflection of a particular personality trait, but a necessary aspect of creative work, which requires alternating intense effort with relaxation.
Strategic, not tactical
The working methods of the innovative designer are, for the most part, not systematic; there is little or no evidence of the use of systematic methods of creative thinking, for example. The innovative designer seems to be too involved with the urgent necessity of problem solving to want, or to need, to stand back and consider their working methods. Their design approach is strategic, not tactical.
Drawing for parallel design thinking
An important feature of their strategy is parallel working - keeping design activity going at many levels simultaneously. The best cognitive aid for supporting and maintaining parallel design thinking is drawing. Drawing with the conventional tools of paper and pencil gives the flexibility to shift levels of detail instantaneously; allows partial, different views at different levels of detail to be developed side by side, or above and below and overlapping; keeps records of previous views, ideas and notes that can be accessed relatively quickly and inserted into the current frame of reference; permits and encourages the simultaneous, non-hierarchical participation of co-workers, using a common representation.
The drawing of partial solutions or representations also aids the designerâs thinking processes, and provides some âtalk-backâ. As well as drawing, innovative designers frequently like to undertake practical work related to the design solution, such as building models or mock-ups, or participating in construction.
A small team of committed coworkers
The innovative designer also likes, perhaps needs, to work with a small team of committed co-workers who share the same passions and dedication.
- ââOn Talentââ