jump to navigation

Getting Real Chapter 1 – Introduction September 11, 2008

Posted by ArgeL CruZ in Getting Real.
Tags: , ,
trackback

     Getting real is a guide in developing a web-based program or software. Its priority when building an application is the end-users. It encourages to start building an app with the user interface first, as they described it as “real screen that people are going to use”, after that, the coding is done. Getting real delivers just what customers need and eliminates anything they don’t. They also intend to lower the cost of maintenance and constantly improving which they think it’s the best approach for a web-based software.

 

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

 

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
  • How to promote your app and spread the word
  • Secrets to successful support
  • Tips on keeping momentum going after launch

 

Comments»

No comments yet — be the first.