Tom Ordonez

Friday, June 29, 2012 from 9:00 AM to 11:00 AM at 1871, Chicago

“by Sarah Gray and Corey Haines, Founders, Technical Advocates Getting your technical prototype built can be terrifying, draining, and expensive. Finding a developer is near impossible – and hiring one feels like a gamble. What if you could relax and focus on your business, knowing that you were equipped to make technical hiring decisions that would keep your company safe? In our “Faster Founder” workshop you’ll come away with guidance on:

• How to identify the type of technical solution that your business needs.
• What to look for–and what to avoid–in a software firm.
• How to talk—and not talk—to a developer.
• What questions to ask when hiring that will keep you from falling into common pitfalls.

We can’t guarantee you’ll make the right decision – but we can give you tips that will help you make the decision that will be best for your business. We can also answer your questions without making you feel stupid.”

How to identify the type of technical solution to your business needs

Are you a technology company or a company that can be supported with technology.

Non technology company Validate your business to find out what you need and what technology can you use to automate.

Technology company foursquare braintree

Their core competency is to build technology solutions.

If you are a technical company > Identify the innovation.

What to look for and avoid in a software firm

How does Feedback work?

Minimize the feedback cycle Automated testing See working code every week

Determining project scope

Fixed bid/varying scope Fixed bid/fixed scope Pay as you go

Some shops know how much effort and money a story could cost based on points. For example a story could be 5 points and they have $ rate for each point.

Evaluating firms

What are they communicating with me what language do they use with me express my idea in the easiest way with my user What is their change process when you need something new

Green Flags

Solving your problem Ownership of code Regular payments Showing you work Focus on user experience They want to meet with you in person

Red Flags

Strange agreements (non-libel) You feel off balance You feel technically intimidated

What you are looking for in a developer

They give you feedback on what you present, so you are sure they understand you You don’t want them to blindly implement what you tell them to do Communicative A complementary schedule

What a dev wants from you

you have an understanding of your product and business you present your goal, not your solution you ask for their input you treat them like a partner

What a dev fears from you

You treat them as an idea-implementor You offer equity only You are not clear on your project scope You don’t have a clear sense of feature priority

Questions to ask to avoid common pitfalls

How do you validate that your code works. (Don’t hire developers that don’t do TDD)

What acceptance testing framework do you use and why (It doesnt matter what the answer is, it matters that the developer has one, and has the thought about the reasons for it - Peter Bell, General Assembly)

What version control do you use and why

How are we going to be communicating

Explain the process of how to build the software How are you going to be showing me the work Whats the process we go through if I realize that was built is not what I wanted (What is the process when I have changes) How do I get my code THe importance of a code review If they make you feel stupid, it’s not the right fit

Resources

bit.ly/tech-guide bit.ly/8thlight-blog