Project Management | Going IT Alone: The Handbook for Freelance and Contract Software Developers

Sign In Start Free Trial

Book Overview & Buying
Table Of Contents

Going IT Alone: The Handbook for Freelance and Contract Software Developers

By : Leon Brown

Going IT Alone: The Handbook for Freelance and Contract Software Developers

By: Leon Brown

Overview of this book

Going IT Alone: The Handbook for Freelance and Contract Software Developers

Going IT Alone: The Handbook for Freelance and Contract Software Developers

Credits

Credits

About the Author

About the Author

Acknowledgements

Acknowledgements

About the Reviewer

About the Reviewer

Preface

Preface

Free Chapter

Introducing Freelancing

Introducing Freelancing

The freelance lifestyle

Is freelancing for you?

Defining your motivations

Don't quit the day job

Legal entities

Home or away?

Summary

Positioning Yourself in the Market

Positioning Yourself in the Market

Market segments

Pricing yourself appropriately

Building quality for market segments

Market research

Summary

Defining Your Business Model

Defining Your Business Model

Types of business model for software

Software Development as a Service (SDaaS)

Software as a Product (SaaP)

Software as a Service (SaaS)

Software Supporting a Service

Business Model Canvas

Components

Canvas

Problem tools

Product life cycle

Five Forces Analysis

Seven Domains Assessment framework

The McKinsey 7S framework

Fitting everything together

The business descriptions

Comparison: McKinsey 7S framework

Comparison – Business Model Canvas

Comparison: conclusion

Summary

Creating a Brand

Creating a Brand

A brief definition of what branding is and isn't

Know your audience

Identify perceptions required for objectives

Specializing – becoming a domain expert

Generalizing – targeting a wider audience

Kick starting perceptions

Who do they think you are?

Summary

Networking, Marketing, and Sales

Networking, Marketing, and Sales

Understanding networking

Defining a networking strategy

Writing press releases

Open project sources

The sales process

Summary

An Introduction to Client Types

An Introduction to Client Types

The ethical client

The difficult client

The trusting client

The nasty client

The price-conscious client

Summary

Managing Clients

Managing Clients

Points of contact

Performing risk assessment of the project

Analyzing the client

Cash flow issues

Summary

Negotiation

Negotiation

The Winning Formula

Strategic Negotiation Phases

Summary

Software Development Resources, Patterns and Strategies

Software Development Resources, Patterns and Strategies

Software problems: A recap

Rescued by object oriented programming

Strategic efficiency with MVC

Strategic data management

API-oriented system architecture

Testing strategy

Security considerations

Version control

Summary

Software Development Methodology

Software Development Methodology

Social factors of software development

Features for preventing problems

Methodologies of interest

Designing your methodology

Summary

Creating Quotes and Estimates

Creating Quotes and Estimates

Maths to the rescue: The basics

Risk management

Recovering unaccounted costs

Maintaining estimation accuracy

Summary

Project Management

Project Management

Client perceptions

Methods of communication

Allocating the right people

Written agreements

Feature creep

Risk assessment

Defining a specification

Feedback

Release cycles

Summary

Appendix

Appendix

Interview 2

Interview 3

Interview 4

Interview 5

Interview 6

Written agreements

Most worthwhile projects will require some form of agreement to be signed, and even where this isn't the case, it's worthwhile having a set of your own terms and conditions written. Although a contract is technically considered to be in place where there is a payment and verbal or written agreement involved, only a written agreement gives both parties reliable evidence of what has been agreed. Aside from the issue of protection against future disagreements, having a written agreement is also a useful tool for making sure that there are no incorrect assumptions made by both parties, which themselves can lead to conflict that derails the project. The following are considerations to make when looking to write up and agree to any formal written agreements:

The ideal terms set for a project will be one that you have created yourself—this eliminates the possibility of you underestimating the definition of any clauses or requirements.
Never immediately accept terms for delivery...

CONTINUE READING

83

Tech Concepts

36

Programming languages

73

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

Going IT Alone: The Handbook for Freelance and Contract Software Developers

Search

Your notes and bookmarks