Before Starting A New Contract....
-
If this is the wrong forum, let me know and I'll move it. Before you start a new project/contract, what questions do you ask? Here's what I send my potential clients. I pre-filled some of it...
- Primary Point of Contact
a. Name, Company, Address, Office and Cell Phones, Email - Scope of the Project
a. Time & Cost
i. Expected Date of Completion
1. (Date goes here)
ii. Budget
1. (Amount Goes Here)
b. Infrastructure
i. Web Access
1. Does the app need to be able to remotely access the database?
a. Yes / No
ii. Development Platform
1. Microsoft C#.Net 4.0, Windows Presentation Foundation 4.0
iii. Target Hardware
1. (What kind of computers will the application run on? Desktop, Laptop, tablets, Phones, etc)
iv. Supported Operating Systems
1. Desktop/Tablet/Laptop/Phone Components
a. Microsoft Windows 7, Microsoft Windows 8
2. Server Components
a. Microsoft Window Server 2008 R2
v. Target Databases
1. (SQL Server, VFP, Access, NoSQL)
c. Requirements
i. See Requirements document
ii. Phases
iii. Deliverables
iv. Milestones
v. Interoperability with other applications
1. Will the software interact with other software applications?
2. Will the software use an third party components
vi. Source Code Control
vii. Testing
Do you guys use or do anything like this? Any thoughts on this? Amy I missing anything critical?
If it's not broken, fix it until it is
- Primary Point of Contact
-
If this is the wrong forum, let me know and I'll move it. Before you start a new project/contract, what questions do you ask? Here's what I send my potential clients. I pre-filled some of it...
- Primary Point of Contact
a. Name, Company, Address, Office and Cell Phones, Email - Scope of the Project
a. Time & Cost
i. Expected Date of Completion
1. (Date goes here)
ii. Budget
1. (Amount Goes Here)
b. Infrastructure
i. Web Access
1. Does the app need to be able to remotely access the database?
a. Yes / No
ii. Development Platform
1. Microsoft C#.Net 4.0, Windows Presentation Foundation 4.0
iii. Target Hardware
1. (What kind of computers will the application run on? Desktop, Laptop, tablets, Phones, etc)
iv. Supported Operating Systems
1. Desktop/Tablet/Laptop/Phone Components
a. Microsoft Windows 7, Microsoft Windows 8
2. Server Components
a. Microsoft Window Server 2008 R2
v. Target Databases
1. (SQL Server, VFP, Access, NoSQL)
c. Requirements
i. See Requirements document
ii. Phases
iii. Deliverables
iv. Milestones
v. Interoperability with other applications
1. Will the software interact with other software applications?
2. Will the software use an third party components
vi. Source Code Control
vii. Testing
Do you guys use or do anything like this? Any thoughts on this? Amy I missing anything critical?
If it's not broken, fix it until it is
Accounting department contact! I must admit I was never that organised when I was consulting, probably explains why I am a contractor!
Never underestimate the power of human stupidity RAH
- Primary Point of Contact
-
If this is the wrong forum, let me know and I'll move it. Before you start a new project/contract, what questions do you ask? Here's what I send my potential clients. I pre-filled some of it...
- Primary Point of Contact
a. Name, Company, Address, Office and Cell Phones, Email - Scope of the Project
a. Time & Cost
i. Expected Date of Completion
1. (Date goes here)
ii. Budget
1. (Amount Goes Here)
b. Infrastructure
i. Web Access
1. Does the app need to be able to remotely access the database?
a. Yes / No
ii. Development Platform
1. Microsoft C#.Net 4.0, Windows Presentation Foundation 4.0
iii. Target Hardware
1. (What kind of computers will the application run on? Desktop, Laptop, tablets, Phones, etc)
iv. Supported Operating Systems
1. Desktop/Tablet/Laptop/Phone Components
a. Microsoft Windows 7, Microsoft Windows 8
2. Server Components
a. Microsoft Window Server 2008 R2
v. Target Databases
1. (SQL Server, VFP, Access, NoSQL)
c. Requirements
i. See Requirements document
ii. Phases
iii. Deliverables
iv. Milestones
v. Interoperability with other applications
1. Will the software interact with other software applications?
2. Will the software use an third party components
vi. Source Code Control
vii. Testing
Do you guys use or do anything like this? Any thoughts on this? Amy I missing anything critical?
If it's not broken, fix it until it is
Don't be too demanding, contracting has two styles, code guru, and consultant. As a consultant it might be YOUR job to provide many of these answers. Many companies are in this situation, they just don't know what they need to get to where they want to be, and that's your job, to lay it out, to set expectations. I have been in many contracts like this, and only one that wasn't, so playing lose is IMO the best way to go about it. Communication is the key. And flexibility.
Sign a petition calling for the boycott of Israel until it returns to its legal 1967 borders.
- Primary Point of Contact
-
Don't be too demanding, contracting has two styles, code guru, and consultant. As a consultant it might be YOUR job to provide many of these answers. Many companies are in this situation, they just don't know what they need to get to where they want to be, and that's your job, to lay it out, to set expectations. I have been in many contracts like this, and only one that wasn't, so playing lose is IMO the best way to go about it. Communication is the key. And flexibility.
Sign a petition calling for the boycott of Israel until it returns to its legal 1967 borders.
In my 28 years of consulting, there is one thing that's true.... "The client doesn't know what they want, but they know that what you gave them isn't it"
If it's not broken, fix it until it is
-
If this is the wrong forum, let me know and I'll move it. Before you start a new project/contract, what questions do you ask? Here's what I send my potential clients. I pre-filled some of it...
- Primary Point of Contact
a. Name, Company, Address, Office and Cell Phones, Email - Scope of the Project
a. Time & Cost
i. Expected Date of Completion
1. (Date goes here)
ii. Budget
1. (Amount Goes Here)
b. Infrastructure
i. Web Access
1. Does the app need to be able to remotely access the database?
a. Yes / No
ii. Development Platform
1. Microsoft C#.Net 4.0, Windows Presentation Foundation 4.0
iii. Target Hardware
1. (What kind of computers will the application run on? Desktop, Laptop, tablets, Phones, etc)
iv. Supported Operating Systems
1. Desktop/Tablet/Laptop/Phone Components
a. Microsoft Windows 7, Microsoft Windows 8
2. Server Components
a. Microsoft Window Server 2008 R2
v. Target Databases
1. (SQL Server, VFP, Access, NoSQL)
c. Requirements
i. See Requirements document
ii. Phases
iii. Deliverables
iv. Milestones
v. Interoperability with other applications
1. Will the software interact with other software applications?
2. Will the software use an third party components
vi. Source Code Control
vii. Testing
Do you guys use or do anything like this? Any thoughts on this? Amy I missing anything critical?
If it's not broken, fix it until it is
I would never have done this in writing, always face to face if possible and over the phone if not. Dialogue is what I always found to be important - ask a question and 90% of clients won't know the answer, so will put down something they think is right, without too much thought. Once I've had discussions around all of this, I will confirm it to them in writing.
PooperPig - Coming Soon
- Primary Point of Contact
-
If this is the wrong forum, let me know and I'll move it. Before you start a new project/contract, what questions do you ask? Here's what I send my potential clients. I pre-filled some of it...
- Primary Point of Contact
a. Name, Company, Address, Office and Cell Phones, Email - Scope of the Project
a. Time & Cost
i. Expected Date of Completion
1. (Date goes here)
ii. Budget
1. (Amount Goes Here)
b. Infrastructure
i. Web Access
1. Does the app need to be able to remotely access the database?
a. Yes / No
ii. Development Platform
1. Microsoft C#.Net 4.0, Windows Presentation Foundation 4.0
iii. Target Hardware
1. (What kind of computers will the application run on? Desktop, Laptop, tablets, Phones, etc)
iv. Supported Operating Systems
1. Desktop/Tablet/Laptop/Phone Components
a. Microsoft Windows 7, Microsoft Windows 8
2. Server Components
a. Microsoft Window Server 2008 R2
v. Target Databases
1. (SQL Server, VFP, Access, NoSQL)
c. Requirements
i. See Requirements document
ii. Phases
iii. Deliverables
iv. Milestones
v. Interoperability with other applications
1. Will the software interact with other software applications?
2. Will the software use an third party components
vi. Source Code Control
vii. Testing
Do you guys use or do anything like this? Any thoughts on this? Amy I missing anything critical?
If it's not broken, fix it until it is
I don't handle this kind of stuff for my current business, but when I was self-employed, or if I were to go back to individual contracting, I'd be more flexible than this. If someone wants to bring a contractor in, it's probably because they don't know exactly what they want (otherwise they'd get code monkeys to just write it), so answering most of those points is part of the brief. I'd get a rough idea of what they wanted, how long they expected it to take to get there and how much money they were prepared to throw at me, and then if it seemed like a job worth taking I'd get into the details of platform, technology stack etc and what the requirements might be. If you nail everything down at the start you can guarantee it won't be like that any more by the middle, never mind the end. Better to clue the client in on that up front so you can work with changing requirements, not against them.
- Primary Point of Contact
-
I don't handle this kind of stuff for my current business, but when I was self-employed, or if I were to go back to individual contracting, I'd be more flexible than this. If someone wants to bring a contractor in, it's probably because they don't know exactly what they want (otherwise they'd get code monkeys to just write it), so answering most of those points is part of the brief. I'd get a rough idea of what they wanted, how long they expected it to take to get there and how much money they were prepared to throw at me, and then if it seemed like a job worth taking I'd get into the details of platform, technology stack etc and what the requirements might be. If you nail everything down at the start you can guarantee it won't be like that any more by the middle, never mind the end. Better to clue the client in on that up front so you can work with changing requirements, not against them.
I've been doing this for almost 30 years, most of it self employed. I totally disagree with you. First, there is NEVER flexibility. If the customer wants a change, they pay. As soon as they waiver from the contract or specs, they pay. I don't work for free, and I don't give away code. I learned this many years ago when customers started "moving target software" where they change their minds in mid development and don't think they should pay for it. If you don't charge for each change, they keep asking for more and bigger "freebies". I specify very clearly in my contracts that I will NOT develop any code other than what's in the specs. Second, I ask these question because you simply CANNOT write an app with a vague idea. If they don't know what they want, then we figure it our before we start. You CANNOT develop what the customer doesn't know. So I'm hoping to solicit more questions to ensure that I'm not missing something. I agree that you cannot "If you nail everything down at the start", but the questions I ask in that questionnaire are a real good starting point.
If someone wants to bring a contractor in, it's probably because they don't know exactly what they want "
Not true at all. Think about your statement. You just said "I'm not sure what I want, so I'll hire some guy who charges more than average to do it". There are many reasons clients use contractors, and never once did one of my clients call me to develop an app because they didn't know what they wanted. The primary reasons clients use customers are they don't need to hire someone full time for a one-and-done job.
I'd get a rough idea of what they wanted, how long they expected it to take to get there and how much money they were prepared to throw at me, and then if it seemed like a job worth taking I'd get into the details of platform, technology stack etc and what the requirements might be.
Totally backwards. How can you possibly discuss time & money when you don't know thing like the technology stack and don't know the requirements? At any rate, the point of my post was to see what other questions people out there ask.
If it's not broken, fix it until it is
-
I would never have done this in writing, always face to face if possible and over the phone if not. Dialogue is what I always found to be important - ask a question and 90% of clients won't know the answer, so will put down something they think is right, without too much thought. Once I've had discussions around all of this, I will confirm it to them in writing.
PooperPig - Coming Soon
This is just a guideline document I created to ensure I hit all the points I need. I go through this with my clients before each project.
If it's not broken, fix it until it is
-
I've been doing this for almost 30 years, most of it self employed. I totally disagree with you. First, there is NEVER flexibility. If the customer wants a change, they pay. As soon as they waiver from the contract or specs, they pay. I don't work for free, and I don't give away code. I learned this many years ago when customers started "moving target software" where they change their minds in mid development and don't think they should pay for it. If you don't charge for each change, they keep asking for more and bigger "freebies". I specify very clearly in my contracts that I will NOT develop any code other than what's in the specs. Second, I ask these question because you simply CANNOT write an app with a vague idea. If they don't know what they want, then we figure it our before we start. You CANNOT develop what the customer doesn't know. So I'm hoping to solicit more questions to ensure that I'm not missing something. I agree that you cannot "If you nail everything down at the start", but the questions I ask in that questionnaire are a real good starting point.
If someone wants to bring a contractor in, it's probably because they don't know exactly what they want "
Not true at all. Think about your statement. You just said "I'm not sure what I want, so I'll hire some guy who charges more than average to do it". There are many reasons clients use contractors, and never once did one of my clients call me to develop an app because they didn't know what they wanted. The primary reasons clients use customers are they don't need to hire someone full time for a one-and-done job.
I'd get a rough idea of what they wanted, how long they expected it to take to get there and how much money they were prepared to throw at me, and then if it seemed like a job worth taking I'd get into the details of platform, technology stack etc and what the requirements might be.
Totally backwards. How can you possibly discuss time & money when you don't know thing like the technology stack and don't know the requirements? At any rate, the point of my post was to see what other questions people out there ask.
If it's not broken, fix it until it is
-
Well, fine. I'm not sure why you made a post asking for thoughts if you're going to respond to my thoughts like that, though.
You should go back and re-read my post. I didn't ask anyone how to run a business. I asked if there were any technical questions other people ask.
If it's not broken, fix it until it is