What is Getting Real?
[Read the entire book for free in Swedish or English]
Want to build a successful web app? Then it's time to Get Real. Getting Real is a smaller, faster, better way to build software.
* Getting Real is about spending more time building the real thing and less time building stuff that represents the real thing, such as charts, graphs, boxes, arrows, schematics, wireframes, etc.
* Getting real is less. Less mass, less software, less features, less paperwork, less of everything that's not essential (and most of what you think is essential actually isn't).
* Getting Real is staying small and being agile.
* 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.
* Getting Real delivers just what customers need and eliminates anything they don't.
[Read the entire book for free in Swedish or English]
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. It forces you to deal with reality.
Getting Real foregoes functional specs and other transitory documentation in favor of building real screens. A functional spec is make-believe, an illusion of agreement, while an actual web page is reality. That's what your customers are going to see and use. That's what matters. Getting Real gets you there faster. And that means you're making software decisions based on the real thing instead of abstract notions.
Finally, Getting Real is an approach ideally suited to web-based software. The old school model of shipping software in a box and then waiting a year or two to deliver an update is fading away. Unlike installed software, web apps can constantly evolve on a day-to-day basis. Getting Real leverages this advantage for all its worth.
How To Write Vigorous Software
Vigorous writing is concise. A sentence should contain no unnecessary words, a paragraph no unnecessary sentences, for the same reason that a drawing should have no unnecessary lines and a machine no unnecessary parts. This requires not that the writer make all sentences short or avoid all detail and treat subjects only in outline, but that every word tell.
—From "The Elements of Style" by William Strunk Jr.
[Read the entire book for free in Swedish or English]
No more bloat
The old way: a lengthy, bureaucratic, we're-doing-this-to-cover-our-asses process. The typical result: bloated, forgettable software dripping with mediocrity. Blech.
Getting Real gets rid of...
* Timelines that take months or even years
* Pie-in-the-sky functional specs
* Scalability debates
* Interminable staff meetings
* The "need" to hire dozens of employees
* Meaningless version numbers
* Pristine roadmaps that predict the perfect future
* Endless preference options
* Outsourced support
* Unrealistic user testing
* Useless paperwork
* Top-down hierarchy
You don't need tons of money or a huge team or a lengthy development cycle to build great software. Those things are the ingredients for slow, murky, changeless applications. Getting real takes the opposite approach.
In this book we'll show you...
* The importance of having a philosophy
* Why staying small is a good thing
* How to build less
* How to get from idea to reality quickly
* How to staff your team
* Why you should design from the inside out
* Why writing is so crucial
* Why you should underdo your competition
[Read the entire book for free in Swedish or English]
Some additional information on agile development techniques from Wikipedia: