Learning to work with remote developers is a valuable skill that will have a positive impact on your business and your wallet. In previous articles in our working with developers series we’ve covered: Now we’re going to cover a rather sticky topic - but super important topic. Getting this right will give you an ongoing relationship with your expert that can even benefit your bank balance. We’re going to talk about scope creep. You may think that getting more from your money is a good thing, right? Nope. Stick with me, I’ll explain why actually scope creep is a bad thing not only for the expert but the client too. Then I’ll give you some tips on how to avoid scope creep from happening. The project scope is the work that the expert has agreed to do for you. This is not always the same as your project brief. The brief is the important first step, but after discussion with your expert what work that get's agreed upon may have changed. This agreed work will be put in writing, here on Codeable, it’s usually listed in the workroom. Scope creep is when the scope of the project gets bigger without any changes to the budget. The "creep" part is because
Share This

We are using cookies on our website

Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.