Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Going IT Alone: The Handbook for Freelance and Contract Software Developers

You're reading from   Going IT Alone: The Handbook for Freelance and Contract Software Developers A detailed guide to self-employment for software and web developers - from identifying your target market, through to managing your time, finances, and client behavior

Arrow left icon
Product type Paperback
Published in Dec 2016
Publisher
ISBN-13 9781783001408
Length 376 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Leon Brown Leon Brown
Author Profile Icon Leon Brown
Leon Brown
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Going IT Alone: The Handbook for Freelance and Contract Software Developers
Credits
About the Author
Acknowledgements
About the Reviewer
Preface
1. Introducing Freelancing 2. Positioning Yourself in the Market FREE CHAPTER 3. Defining Your Business Model 4. Creating a Brand 5. Networking, Marketing, and Sales 6. An Introduction to Client Types 7. Managing Clients 8. Negotiation 9. Software Development Resources, Patterns and Strategies 10. Software Development Methodology 11. Creating Quotes and Estimates 12. Project Management Appendix

Analyzing the client


You can't assess the risk that a client can pose to your success and profitability on a project unless you have information beforehand about how they operate. Although there is no substitute for being able to measure a client from previous experiences of working with them, there are a number of ways that you can obtain an amount of information that will help you in estimating what risks a client will pose to any possible project and working relationship.

Commitment

A client's commitment to a project will often be a defining factor in a successful implementation—no matter how good your project management and technical skills are, your output will always rely on what the client inputs. There's an IT acronym known as GIGO (Garbage In Garbage Out) that accurately describes the issue in that if the client doesn't put the required effort into the project, then they wont get what they want out of the project.

Although it's difficult to see how important a client sees their project...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime