Add Product Development Agreement Template Byline with airSlate SignNow

Countersign product development agreement template

hi my name is Oleg I am a CEO of mobile dev today we are going to talk about fix it cost contracts what is that that's the type of collaboration between you and your software development partner where every scene is said beforehand all requirements are in place cost and schedule are clear and no really clarifications or changes are done within the course of the project so what projects will work well for fixed cost contracts typically it's a smaller projects for two or three months duration within this time frame it's possible to implement a small demo a limited version of MVP or it's possible to add new features to your existing product how does it work to start a fixed cost contract you come with three very important since its specification where all requirements are described in detail its mock-up a UI use design which is fully ready for implementation and it is acceptance criteria a checklist which will be used to test the product and it also defines what to treat as a ready product your software development partner will come up with an offer which includes one more options of implementation of your project it will also include schedule and cost the offer will also contain information about possible risks most of the risks are taken care of that's why you shouldn't worry at the same time some of the risks cannot be just handled by your software development partner these risks are typically connected with third party API or services or SDK even such widely used API as Google Facebook Twitter may change which will help influence in your project so time and cost may change if you are ready to start you make the prepayment typically it's a 50% of the project cost you're a software development partner will come up with a project plan and you will agree about the start date so you kick off the project the whole project is typically divided to several milestones at each milestone you'll get a build which helps you to track the progress during each milestone your software development partner will implement new features the last milestone is fully devoted to testing and polishing let's take an example a pizza-delivery application you use this app to select the pizza you want to make an order and to perform the payment so for example this project will be divided to four milestones within the first milestone the development team will implement logon screen will implement home screen within the second milestone the development team will work on selecting and ordering process and the third milestone will work for payment process so your development team will add new features you'll get built with more and more functionality in until at the result of the third milestone you'll get a build with all the functionality in of course there will be bugs which is okay and you'll be able to test this build and see if everything works and looks as you expected this build is called alpha version it is tweaked to work with a test server it may contain some test data and the users will be also not real what if something needs to be added within the course of the project it may be a small change like move a button from a bottom to the top of the screen or it could be something bigger like a new feature for instance let's take our Pizza Delivery application you may want to add a new feature of delivering pizza to your geolocation so pizza can be delivered to your office or the park where you are located this request is processed by the project manager and a special document called change request document is created this change request is estimated by development team so you get cost and time to make this change and you'll make a decision of whether you want to proceed with this feature or not if you want to proceed with it you make a payment and the development team will implement it for you during the milestone for your product is heavily tested and polished it is done on both your site and your software development partner side any issues which are found according to acceptance criteria are fixed at the end you'll get a final build which practically has no bugs and it's ready to be delivered to your target audience this build is typically called beta version and it's tweaked to work with production server real data and real users of course you want to make sure that your application works in the ways that you expected it to for that you get an acceptance period of five days depending on the project when the project is accepted you make the final payment you get a project sources and now you are ready to upload the application to the market places like Google Play or App Store voila your product is finally on the market place and the users will start getting it and they will come back to you with their feedback it could be suggestions for improvement or it could be some bugs found in different testing conditions what to do with this first run as you also may have some new ideas for features and how to evolve the product further first option you may collect this information and go to the next project stage second option you may buy a subscription of ten or twenty hours per month so the development team could make some smaller changes minor updates and bug fixes you select whatever suits best for you that's all for now see you soon Sincerely Yours MOBA Dev