On this page... (hide)
Getting Real is about skipping all the stuff that
represents real (charts, graphs, boxes, arrows, schematics,
wireframes, etc.) and actually building the real thing.
Getting Real starts with the interface, the real screens that
people are going to use. It begins with what the customer
actually experiences and builds backwards from there.This lets
you get the interface right before you get the software wrong.
Getting Real is about iterations and lowering the
cost of change. Getting Real is all about launching,
tweaking, and constantly improving which makes
it a perfect approach for web-based software.
The benefits of Getting Real - Getting Real delivers better results because it forces you to deal with the actual problems youíre trying to solve instead of your ideas about those problems. .
Once you iterate quickly and react on customer feedback, you
will establish a customer connection.
- Build Less
- Whatís Your Problem?
- Fund Yourself
- Fix Time and Budget, Flex Scope
- Have an Enemy
- It Shouldnít be a Chore
Conventional wisdom says that to beat your competitors you
need to one-up them.
This sort of one-upping Cold War mentality is a dead-end. Itís
an expensive, defensive, and paranoid way of building products.
Defensive, paranoid companies canít think ahead, they can only
think behind. They donít lead, they follow.
Do less than your competitors to beat them. . Instead of one upping, try one-downing. Instead of outdoing, try underdoing.
- Less features
- Less options/preferences
- Less people and corporate structure
- Less meetings and abstractions
- Less promises
Build software for yourself - When you solve your own problem, you create a tool that youíre passionate about. And passion is key. Passion means youíll truly use it and care about it. And thatís the best way to get others to feel passionate about it too.
"Scratching your own itch."
As the designer or developer of a new application, each and every day: blue or green? One table or two? Static or dynamic? Abort or recover? How do we make these decisions?
If itís something we recognize as being important, . The rest, .
And all that guessing builds up a kind of debt in our applications Ė an .
As a developer, I hate this. The knowledge of all these small-scale in the applications I write adds to my . Open Source developers, scratching their own itches, donít suffer this. Because they are their own users, they know the correct answers to 90% of the decisions they have to make.
ĖDave Thomas, The Pragmatic Programmers
Born out of necessity
Constraints force creativity
Run on limited resources and youíll be forced to reckon with
constraints earlier and more intensely. And thatís a good thing.
Constraints drive innovation.