Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Business

Andrew McCormick
Andrew McCormick
17,730 Points
Posted by Andrew McCormick
Andrew McCormick
17,730 Points

Customer Application Approval

I'm wondering if anyone has any set approval processes they follow when building out applications for their customers?
Obviously the customer needs to sign off on the design (fonts, colors, layouts, etc). What about interactions such as when you click a button where it takes you, or how the application would handle bad data attempts or errors in forms. Data storage and DB design?

How much of it do you really get a customer to sign off on before actually building out the application, and how strict are you on changes even after sign off? I would think there are somethings that we can be flexible on, but other more back-end stuff that would cause big headaches and thus we need to be strict on not changing later (at least not for free).

thanks for any ideas.

1 Answer

Daniel Noel-davies
Daniel Noel-davies
145 Points
Daniel Noel-davies
Daniel Noel-davies
145 Points

As a freelancer / business you should internally agree on a workflow, and also the number of free amendments that a client has. Each stage should include a deliverable set of resources that you can get approved (Such as Wireframes, User Stories, Designs, etc)

In regards to user interactions, you should look into user stories, these can be agreed upon.

A user story, as it's core, is as follows:

AS A [user_type] I WANT TO [action] SO THAT [business_achievement]

for example: As a user, I want to be able to fill in my username and password into the login form, and then press the login button, So that I can be taken to my user dashboard and review my account.

Andrew McCormick
Andrew McCormick
17,730 Points
Andrew McCormick
Andrew McCormick
17,730 Points

Thanks for the reply! We currently use wireframes and user narratives in the approval process for our websites and that's about it for the pre-development stages. As we move toward more application development (which seems to be more systematic, involve a lot more money, and also adds in data and scalability) I wanted to make sure we weren't leaving any loopholes or leaving out anything. I also didn't know if there were any kind of proven systems or theories to follow.