Would you define customer touch points first and hack all the way in; or build the core internal features first?
Not middle-out?
I came here to make sure a middle-out joke was made
End to end use cases with acceptable usability... Series of Minimum marketable features..
Contracts and data design first, then middle, outside, inside, and persistence simultaneously.
Vertical slices of functionality. Release a feature at a time even if internally or in beta.
I thought it’s about my golf swing...
“Defining” and “building” are two totally different things. I would define the customer touch points first, but actually build the core features that support it before working on the UI
Can you elaborate if you will expect the user to use your product via the touchpoints? Or will you be open to interim internal touchpoints?
Only thing I thought of when I saw this was in-n-out. I have my priorities right =]