Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
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

Release cycles


It is said that the initial development of a typical software system only accounts for 20% of the total system, meaning that additional enhancements introduced after the first release can account for as much as an additional four times the amount of software development. For projects that are anything other than a simple straightforward system such as a brochure style website, this can become a serious issue because clients without an understanding of software release cycles will want everything in the first release. This can lead to over ambitious expectations, ongoing changes and constant additions to the specification that keep delaying the first release. Ultimately, this risks the system being released too late; whether in terms of the market opportunity already having passed or of the potential to make savings in the client's operations.

How often?

It's a fine balance when deciding how often to release new versions of the software you are being hired to develop. Getting...

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
Banner background image