This link has been bookmarked by 75 people . It was first bookmarked on 27 Apr 2006, by netklon.
-
09 Jul 09
-
08 Jun 09
-
10 Mar 09
-
Will KnottGetting Real is all about starting from the user interface and customer experience and then building out. Visual design first, programming second. The more traditional process is starting from the abstract (documentation, diagrams, charts, etc.), coding a
specification spec specs documentation ui projectmanagement project design business usability
-
09 Mar 09
-
11 Feb 09
gavin sadeGetting Real is all about starting from the user interface and customer experience and then building out. Visual design first, programming second.
-
14 Oct 08
-
Functional specifications document are “yes documents.” They’re political. They’re all about getting to “yes” and we think the goal up front should be getting to “no.” Functional specs lead to scope creep from the very start. There’s very little cost in saying “yeah, ok, let’s add that” to a Word document.
-
Functional specs are often appeasement documents. They’re about making people feel involved. But, there’s very little reality attached to anything you do
-
Functional specs are about making decisions before you have enough information to decide. They are about predicting the future and we all know how accurate that is.
-
-
03 Oct 08
-
18 Sep 08
-
08 Jul 08
-
18 Jun 08
-
26 Feb 08
-
30 Nov 07
Phillip LongAn alternate design process that leaves out functional specs in favor or doing the design.
design development tools programming software process 37signals
-
24 Jun 07
darius kumanaNo functional spec - The interface is the functional spec
-
19 Jun 07
-
21 Apr 07
-
20 Feb 07
-
13 Dec 06
-
25 Oct 06
-
16 Oct 06
-
03 Sep 06
-
31 Jul 06
-
19 May 06
-
27 Apr 06
-
05 Mar 06
-
31 Jan 06
-
18 Jan 06
highrollerStep 1: Don’t write a functional specifications document Don’t write a functional specifications document. Why? Well, there’s nothing functional about a functional specifications document.
-
03 Jan 06
livwestMock interface designs instead of a functional spec. Use a one-page 'story' to describe, then go to mockup.
-
Getting Real is all about starting from the user interface and customer experience and then building out. Visual design first, programming second. The more traditional process is starting from the abstract (documentation, diagrams, charts, etc.), coding a skeleton app, and then homing in on the real by finishing it up with an interface. We think that’s backwards.
-
-
17 Nov 05
-
09 Oct 05
xose 33Step 1: Donâ⊘t write a functional specifications document
-
08 Oct 05
-
08 Aug 05
Jason MarottiGetting Real is all about starting from the user interface and customer experience and then building out. Visual design first, programming second.
-
21 Jun 05
-
20 Jun 05
Luis OopshDon’t write a functional specifications document. Why? Well, there’s nothing functional about a functional specifications document. (...)
-
17 Jun 05
-
15 Jun 05
-
14 Jun 05
-
26 Mar 05
-
04 Mar 05
Matt ConstantineWhy it's a bad idea to write functional specs. Instead, a one page user story is all that's needed.
-
16 Feb 05
-
15 Feb 05
-
We talk a lot about our “Getting Real” process at the Building of Basecamp workshops (next one to be announced shortly — sign up for the mailing list at the bottom of the sidebar to be notified).
-
-
13 Feb 05
eddequinceyDon’t write a functional specifications document. Why? Well, there’s nothing functional about a functional specifications document.
-
11 Feb 05
Johann RichardDon’t write a functional specifications document. Why? Well, there’s nothing functional about a functional specifications document.
-
10 Feb 05
Are Halland"Don’t write a functional specifications document. Why? Well, there’s nothing functional about a functional specifications document."
Page Comments
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.