The fuzzy front end
July 1st, 2007 | 3 comments
I want to collect together all the terms that describe activities at the start of software projects.
The fuzzy front end
- Discovery
- Ideation
- Brainstorming
- Chartering
- Initiation
- Information Architecture
- Wire Frames
- High-level Design
- High-level Requirements
Big design up front
- Mocks
- Conceptual Modeling
- Specification
- Detailed Design
- Detailed Requirements
- Software System Architecture
Any additions? Please…
Short link: http://jkat.me/gqxPc4
Comments
Comment from >Luke Melia
Time: July 1, 2007, 4:34 am
“Platform selection” is somewhere in there. “Iteration 0″, “Project Kickoff”, “sketches”, “Prototypes”, “Greenlighting”
Comment from >Steve Freeman
Time: July 4, 2007, 5:19 pm
I know I’m being pedantic, but I don’t understand why mocks count as BDUF.
S.
Comment from >Ken
Time: July 4, 2007, 9:43 pm
For clarification: I meant design mockups not object mocks.
Detailed design mockups are definitely an upfront design activity.
37 Signal’s Getting Real involves going directly from idea to implementation.
From their blog Signal vs. Noise :
“In general I don’t believe in mocking up screens with Photoshop. Your HTML/CSS screens will never look quite the same as the initial mock, so it’s easy to waste time pushing pixels that won’t even exist later.”
At Oxygen we’re starting to follow 37 Signals lead and replace Photoshop mockups with simple sketches (not meticulous wireframes) and/or working software.
Write a comment