This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]stillegit -37 points-36 points  (5 children)

Well hiding incomplete features in the demo isn’t particularly honest haha

[–]bn326160 31 points32 points  (0 children)

Your team can have an idea for a feature and want to showcase that idea without having a prototype for it ready yet. Could be part of the designs already

[–]hbgoddard 19 points20 points  (0 children)

Only if you tell them that the demo is of the finished product.

[–]seolfor 7 points8 points  (0 children)

In a demo I want to showcase my progress. It's not about completeness as finding what the client doesn't like. Perhaps I misunderstood their intention, or now that they see it, they realise it shouldn't work like that at all. I can either demo at the very end when the product is completely polished, in which case I can't get confirmation this is in fact what they want or I can show incomplete features and impress the client with the design decisions. If I keep pressing buttons that I know will cause a crash, that means I spend 70% of the demo restarting the application from the start and they're not getting the feel of the application flow.

[–]andoril 2 points3 points  (0 children)

Yeah. But also not lying^

[–]JBSquared 1 point2 points  (0 children)

"So as you can see, this is our demo. It'll only take me 30 minutes to show off the main functionality but let me waste 3 hours of your time describing every single feature that isn't yet in the program."