Startup outsourcing 15 things that go with a good requirement specification!

  • 760 views
Uploaded on

Startup

Startup

More in: Business , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
760
On Slideshare
0
From Embeds
0
Number of Embeds
5

Actions

Shares
Downloads
17
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. STARTUP OUTSOURCING – 15 THINGS TO DO WHEN SPECIFYING REQUIREMENTS
  • 2. 1 Page > 100 Pages(Don’t send elaborate requirements to every vendor. Start with a 1-page overview)1
  • 3. Timeframe(Clearly communicate the start & end dates. Show that you have an urgency!)2
  • 4. Money(State that you’ve a source of funding for the project, even if it’s out of your pocket!)3
  • 5. Sell long-term(State briefly your plan for the next 2 years. You’re helping the vendor’s sales guypresent your case as a long term customer!)4
  • 6. Prepare(Have answers to all the questions. Where you don’t, find and get back!)5
  • 7. Communicate, visually(Verbal < Document < PowerPoint Mockup < Visual Prototype < Interactive HTML)6
  • 8. Don’t tell. Show(Pepper your document with links to what’s closer to your expectations.)7
  • 9. Title & number every mockup screen(Make it easy to refer a screen in a vendor’s estimate!)8
  • 10. Explain what you show!(Explain every detail that goes into your mockup and make it the detailed functionalrequirement document. Better yet, record it in your own voice and send it out alongwith your requirement document.)9
  • 11. Take expert help, for planning!(Get the technical, information and visual design done by someone you can sit acrossthe hall. Offshore the execution. Near shore the planning!)10
  • 12. Ask for scenario based estimates!(Ask for estimates that represent different tradeoffs between features count, depth orcost)11
  • 13. English (beep) English!(If you are a non-native English speaker and/or if your English is not good, proof-readyour requirements document with someone who is!)12
  • 14. Send a response template!(Avoid the nightmare of comparing proposals with diverse sections, depth and style. Make yourown template and share it with vendors.!)13
  • 15. Don’t be greedy!(You cannot get the best code at the cheapest price within the shortest time!)14
  • 16. Set Milestones(Make every vendor comply with milestones – For Questions, Case Studies, Estimations,Proposals and References. Ad hoc process would not allow you to compare vendors in everystage.)15
  • 17. Hard to remember all these points?Take ContractIQ’s hands-on vendor selection plan. We’d do it the right way for you!16http://www.contractiq.com