[{"data":1,"prerenderedAt":524},["ShallowReactive",2],{"document-agile-team-agreement-D13899":3},{"document":4,"label":23,"preview":11,"thumb":24,"thumb600":25,"description":5,"descriptionCustom":6,"apiDescription":5,"pages":8,"extension":10,"parents":26,"breadcrumb":30,"related":38,"customDescModule":176,"customdescription":6,"mdFm":177,"mdProseHtml":523},{"description":5,"descriptionCustom":6,"label":7,"pages":8,"size":9,"extension":10,"preview":11,"thumb":12,"svgFrame":13,"seoMetadata":14,"parents":16,"keywords":15},"AGILE TEAM AGREEMENT This Agile Team Agreement (the \"Agreement\") is made and effective this [DATE], BETWEEN: [COMPANY NAME] (the \" Company\"), a company organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], [COUNTRY], with its head office located at: [YOUR COMPLETE ADDRESS] AND: [TEAM MEMBER NAME] (the \" Team Member\"), an individual/company with their main address located at: [COMPLETE ADDRESS] WHEREAS, the Company desires to engage the Team Member as part of an Agile team to work on [PROJECT NAME]; WHEREAS, the Team Member agrees to participate in the Agile team and adhere to the terms and conditions set forth herein; IT IS HEREBY AGREED THAT: ROLE AND RESPONSIBILITIES 1.1 The Team Member agrees to fulfill the role of [ROLE] within the Agile team, adhering to the principles and practices of Agile methodology. 1.2 The Team Member commits to actively participating in all Agile ceremonies, including but not limited to, daily stand-ups, sprint planning, sprint reviews, and retrospectives. 1.3 The Team Member agrees to collaborate effectively with other team members, share knowledge, and contribute to the team's goals and objectives. 1.4 The Team Member will deliver tasks and user stories assigned within the agreed-upon sprint timelines, ensuring quality and adherence to acceptance criteria. 1.5 The Team Member will communicate any impediments or issues that may affect their work or the team's progress as soon as they arise. TERM 2.1 The term of this Agreement shall commence on [START DATE] and terminate on [END DATE], subject to any extensions agreed upon in writing by both parties. COMPENSATION 3.1 The Company agrees to pay the Team Member a fee of [AMOUNT] in [CURRENCY], payable as follows: [Payment Terms]. 3.2 Any additional costs incurred due to participation in the project, including but not limited to, travel and training, shall be borne by the Company. CONFIDENTIALITY 4",null,"Agile Team Agreement","3",513,"doc","https://templates.business-in-a-box.com/imgs/1000px/agile-team-agreement-D13899.png","https://templates.business-in-a-box.com/imgs/250px/13899.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#13899.xml",{"title":15,"description":6},"agile team agreement",[17,20],{"label":18,"url":19},"Business Plan Kit","/templates/business-plan-kit/",{"label":21,"url":22},"Board of Directors","/templates/board-of-directors/","Agile Team Agreement Template","https://templates.business-in-a-box.com/imgs/400px/13899.png","https://templates.business-in-a-box.com/imgs/600px/13899.png",[27,17,20],{"label":28,"url":29},"Templates","/templates/",[31,32,35],{"label":28,"url":29},{"label":33,"url":34},"Legal Agreements","/templates/business-legal-agreements/",{"label":36,"url":37},"Partnerships & Joint Ventures","/templates/partnerships-and-joint-ventures/",[39,43,47,51,55,59,63,67,71,75,79,83,87,102,118,133,147,164],{"label":40,"url":41,"thumb":42,"extension":10},"Team Agreement","/template/team-agreement-D13887","https://templates.business-in-a-box.com/imgs/250px/13887.png",{"label":44,"url":45,"thumb":46,"extension":10},"Team Work Agreement","/template/team-work-agreement-D13888","https://templates.business-in-a-box.com/imgs/250px/13888.png",{"label":48,"url":49,"thumb":50,"extension":10},"Team Charter","/template/team-charter-D13479","https://templates.business-in-a-box.com/imgs/250px/13479.png",{"label":52,"url":53,"thumb":54,"extension":10},"Outsourcing Your Team","/template/outsourcing-your-team-D12957","https://templates.business-in-a-box.com/imgs/250px/12957.png",{"label":56,"url":57,"thumb":58,"extension":10},"Remote Team Management","/template/remote-team-management-D12959","https://templates.business-in-a-box.com/imgs/250px/12959.png",{"label":60,"url":61,"thumb":62,"extension":10},"Team Building Guide","/template/team-building-guide-D12930","https://templates.business-in-a-box.com/imgs/250px/12930.png",{"label":64,"url":65,"thumb":66,"extension":10},"Team Building Exercises","/template/team-building-exercises-D13045","https://templates.business-in-a-box.com/imgs/250px/13045.png",{"label":68,"url":69,"thumb":70,"extension":10},"Building A Powerful Team Guide","/template/building-a-powerful-team-guide-D13087","https://templates.business-in-a-box.com/imgs/250px/13087.png",{"label":72,"url":73,"thumb":74,"extension":10},"Strategies For Improving Team Collaboration","/template/strategies-for-improving-team-collaboration-D12982","https://templates.business-in-a-box.com/imgs/250px/12982.png",{"label":76,"url":77,"thumb":78,"extension":10},"Team Assembler Job Description","/template/team-assembler-job-description-D11720","https://templates.business-in-a-box.com/imgs/250px/11720.png",{"label":80,"url":81,"thumb":82,"extension":10},"Virtual Team Building Activities","/template/virtual-team-building-activities-D13047","https://templates.business-in-a-box.com/imgs/250px/13047.png",{"label":84,"url":85,"thumb":86,"extension":10},"Non-Profit Partnership Agreement","/template/non-profit-partnership-agreement-D14023","https://templates.business-in-a-box.com/imgs/250px/14023.png",{"description":88,"descriptionCustom":6,"label":89,"pages":90,"size":91,"extension":10,"preview":92,"thumb":93,"svgFrame":94,"seoMetadata":95,"parents":96,"keywords":100,"url":101},"INDEPENDENT CONTRACTOR AGREEMENT This Independent Contractor Agreement (\"Agreement\") is made and effective [Date], BETWEEN: [INDEPENDENT CONTRACTOR NAME] (the \"Independent Contractor\"), a company organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] AND: [YOUR COMPANY NAME] (the \"Company\"), a company organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [YOUR COMPLETE ADDRESS] RECITALS Independent Contractor is engaged in providing [Describe] business services, its Employer Tax I.D. Number is [Insert], and its Business License Number is [insert]. Independent Contractor has complied with all Federal, State, and local laws regarding business permits, sales permits, licenses, reporting requirements, tax withholding requirements, and other legal requirements of any kind that may be required to carry out said business and the Scope of Work which is to be performed as an Independent Contractor pursuant to this Agreement. Independent Contractor is or remains open to conducting similar tasks or activities for clients other than the Company and holds themselves out to the public to be a separate business entity. Company desires to engage and contract for the services of the Independent Contractor to perform certain tasks as set forth below. Independent Contractor desires to enter into this Agreement and perform as an independent contractor for the company and is willing to do so on the terms and conditions set forth below. NOW, THEREFORE, in consideration of the above recitals and the mutual promises and conditions contained in this Agreement, the Parties agree as follows: TERMS This Agreement shall be effective commencing [Date], and shall continue until terminated at the completion of the Scope of Work which shall occur no later than [Date] or by either party as otherwise provided herein. STATUS OF INDEPENDENT CONTRACTOR This Agreement does not constitute a hiring by either party. It is the parties intentions that Independent Contractor shall have an independent contractor status and not be an employee for any purposes, including, but not limited to, [laws]. Independent Contractor shall retain sole and absolute discretion in the manner and means of carrying out their activities and responsibilities under this Agreement. This Agreement shall not be considered or construed to be a partnership or joint venture, and the Company shall not be liable for any obligations incurred by Independent Contractor unless specifically authorized in writing. Independent Contractor shall not act as an agent of the Company, ostensibly or otherwise, nor bind the Company in any manner, unless specifically authorized to do so in writing. TASKS, DUTIES, AND SCOPE OF WORK Independent Contractor agrees to devote as much time, attention, and energy as necessary to complete or achieve the following: [Describe]. The above to be referred to in this Agreement as the \"Scope of Work\". It is expected that the Scope of Work will completed by [Date]. Independent Contractor shall additionally perform any and all tasks and duties associated with the Scope of Work set forth above, including but not limited to, work being performed already or related change orders. Independent Contractor shall not be entitled to engage in any activities which are not expressly set forth by this Agreement. The books and records related to the Scope of Work set forth in this Agreement shall be maintained by the Independent Contractor at the Independent Contractor's principal place of business and open to inspection by Company during regular working hours. Documents to which Company will be entitled to inspect include, but are not limited to, any and all contract documents, change orders/purchase orders and work authorized by Independent Contractor or Company on existing or potential projects related to this Agreement. Independent Contractor shall be responsible to the management and directors of Company, but Independent Contractor will not be required to follow or establish a regular or daily work schedule. Supply all necessary equipment, materials and supplies. Independent Contractor will not rely on the equipment or offices of Company for completion of tasks and duties set forth pursuant to this Agreement. Any advice given Independent Contractors regarding the scope of work shall be considered a suggestion only, not an instruction. Company retains the right to inspect, stop, or alter the work of Independent Contractor to assure its conformity with this Agreement. ASSURANCE OF SERVICES Independent Contractor will assure that the following individuals (the \"Key Employees\") will be available to perform, and will perform, the Services hereunder until they are completed (identify by title and name as applicable): [Name of Key Employee, Title] [Name of Key Employee, Title] The Key Employees may be changed only with the prior written approval of the Company, which approval shall not be unreasonably withheld. COMPENSATION Independent Contractor shall be entitled to compensation for performing those tasks and duties related to the Scope of Work as follows: [Describe] Such compensation shall become due and payable to Independent Contractor in the following time, place, and manner: [Describe] NOTICE CONCERNING WITHHOLDING OF TAXES Independent Contractor recognizes and understands that it will receive a [specify tax] statement and related tax statements, and will be required to file corporate and/or individual tax returns and to pay taxes in accordance with all provisions of applicable Federal and State law. Independent Contractor hereby promises and agrees to indemnify the Company for any damages or expenses, including attorney's fees, and legal expenses, incurred by the Company as a result of independent contractor's failure to make such required payments. AGREEMENT TO WAIVE RIGHTS TO BENEFITS Independent Contractor hereby waives and foregoes the right to receive any benefits given by Company to its regular employees, including, but not limited to, health benefits, vacation and sick leave benefits, profit sharing plans, etc. This waiver is applicable to all non-salary benefits which might otherwise be found to accrue to the Independent Contractor by virtue of their services to Company, and is effective for the entire duration of Independent Contractor's agreement with Company. This waiver is effective independently of Independent Contractor's employment status as adjudged for taxation purposes or for any other purpose. Neither this Agreement, nor any duties or obligations under this Agreement may be assigned by either party without the consent of the other. TERMINATION This Agreement may be terminated prior to the completion or achievement of the Scope of Work by either party giving [number] days written notice. Such termination shall not prejudice any other remedy to which the terminating party may be entitled, either by law, in equity, or under this Agreement. NON-DISCLOSURE OF TRADE SECRETS, CUSTOMER LISTS AND OTHER PROPRIETARY INFORMATION Independent Contractor agrees not to disclose or communicate, in any manner, either during or after Independent Contractor's agreement with Company, information about Company, its operations, clientele, or any other information, that relate to the business of Company including, but not limited to, the names of its customers, its marketing strategies, operations, or any other information of any kind which would be deemed confidential, a trade secret, a customer list, or other form of proprietary information of Company. Independent Contractor acknowledges that the above information is material and confidential and that it affects the profitability of Company. ","Independent Contractor Agreement","6",62,"https://templates.business-in-a-box.com/imgs/1000px/independent-contractor-agreement-D160.png","https://templates.business-in-a-box.com/imgs/250px/160.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#160.xml",{"title":6,"description":6},[97],{"label":98,"url":99},"Consultant & Contractors","consulting-contractor-business","independent contractor agreement","/template/independent-contractor-agreement-D160",{"description":103,"descriptionCustom":6,"label":104,"pages":105,"size":106,"extension":10,"preview":107,"thumb":108,"svgFrame":109,"seoMetadata":110,"parents":111,"keywords":116,"url":117},"CUSTOM SOFTWARE DEVELOPMENT AGREEMENT This Custom Software Development Agreement (the \"Agreement\") is made and effective [DATE], BETWEEN: [CUSTOMER NAME] (the \"Customer\"), a corporation organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] AND: [YOUR COMPANY NAME] (the \"Developer\"), a corporation organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [YOUR COMPLETE ADDRESS] RECITALS WHEREAS Customer wishes to [DESCRIBE NEEDS TO BE ADDRESSED], and wants to hire Developer to develop these custom software packages, and; WHEREAS Developer desires to develop these custom software packages for Customer: NOW, THEREFORE, in consideration of the mutual covenants and agreements herein contained, the parties hereto, intending, to be legally bound, agree as follows: Purpose of Agreement Customer desires to retain Developer as an independent contractor to develop the computer software (the \"Software\") described in the Functional Specifications contained in Exhibit A attached to and made part of this Agreement. Developer is ready, willing and able to undertake the development of the Software and agrees to do so under the terms and conditions set forth in this Agreement. Preparation of Development Plan Developer shall prepare a development plan (\"Development Plan\") for the Software, satisfying the requirements set forth in the Functional Specifications. The Development Plan shall include: Detailed Specifications for the Software; A listing of all items to be delivered to Customer under this Agreement (\"Deliverables\"); A delivery schedule containing a delivery date for each Deliverable; and A payment schedule setting forth the amount and time of Developer's compensation. ACCEPTANCE OF DEVELOPMENT PLAN Developer shall deliver the Development Plan to Customer by [DEVELOPMENT PLAN DEADLINE]. Customer shall have [NUMBER] days to review the Development Plan. Upon approval of the Development Plan by Customer, it will be marked as Exhibit B and will be deemed by both parties to have become a part of this Agreement and will be incorporated by reference. Developer shall then commence development of Software that will substantially conform to the requirements set forth in the Development Plan. If the Development Plan is in Customer's reasonable judgment unsatisfactory in any material respect, Customer shall prepare a detailed written description of the objections. Customer shall deliver such objections to Developer within [NUMBER] days of receipt of the Development Plan. Developer shall then have [NUMBER] days to modify the Development Plan to respond to Customer's objections. Customer shall have [NUMBER] days to review the modified Development Plan. If Customer deems the modified Development Plan to be unacceptable, Customer has the option of terminating this Agreement upon written notice to Developer or permitting Developer to modify the Development Plan again under the procedure outlined in this paragraph. If this Agreement is terminated, the obligations of both parties under it shall end except for Customer's obligation to pay Developer all sums due for preparing the Development Plan and the ongoing obligations of confidentiality set forth in the provision of this Agreement entitled \"Confidentiality.\" Payment for Development Plan If the Development Plan is not accepted by Customer and Customer terminates this Agreement, Developer shall be entitled to compensation on a time and materials basis at an hourly rate of [HOURLY RATE] plus expenses to the date of termination. Developer shall submit an invoice detailing its time and expenses preparing the Development Plan. If the invoice amount is less than the amounts paid to Developer prior to termination, Developer shall promptly return the excess to Customer. If the invoice amount exceeds the amounts paid to Developer prior to termination, Customer shall promptly pay Developer the difference. However, Developer's total compensation for preparing the Development Plan shall not exceed [AMOUNT]. Payment [TIME AND MATERIALS AGREEMENT] Developer shall be compensated at the rate of [RATE] per hour [OR \"day,\" \"week,\" \"month\"]. Payment will be made within [NUMBER OF DAYS] days of Developer's submission of an invoice for work completed. [OPTIONAL: \"Unless otherwise agreed upon in writing by Customer, Customer's maximum liability for all services performed during the term of this Agreement shall not exceed [MAXIMUM AMOUNT].\"] OR [FIXED PRICE AGREEMENT] The total contract price shall be set forth in the Development Plan. Customer shall pay the Developer the sum of [INITIAL AMOUNT] upon execution of this Agreement and the sum of [AMOUNT IF PLAN APPROVED] upon Customer's approval of the Development Plan. The remainder of the contract price shall be payable in installments according to the payment schedule to be included in the Development Plan. Each installment shall be payable upon completion of each project phase by Developer and acceptance by Customer in accordance with the provision of this Agreement entitled \"Acceptance Testing of Software.\" Payment of Developer's Costs Customer shall reimburse Developer for all out-of-pocket expenses incurred by Developer in performing services under this Agreement. Such expenses include, but are not limited, to: All communications charges Costs for providing conversion services for converting Customer's database Media costs Travel expenses other than normal commuting, including airfares, rental vehicles, and highway mileage in company or personal vehicles at [cents per mile] Other expenses resulting from the work performed under this Agreement. Developer shall submit an itemized statement of Developer's expenses. Customer shall pay Developer within [NUMBER] days from the date of each statement. Late Fees Late payments by Customer shall be subject to late penalty fees of [%] per month from the due date until the amount is paid. Materials Customer shall make available to Developer, at Customer's expense, the following materials, facilities and equipment: [LIST] These items will be provided to Customer by [DATE]. Changes in Project Scope If at any time following acceptance of the Development Plan by Customer, Customer should desire a change in Developer's performance under this Agreement that will alter or amend the Specifications or other elements of the Development Plan, Customer shall submit to Developer a written proposal specifying the desired changes. Developer will evaluate each such proposal at its standard rates and charges. Developer shall submit to Customer a written response to each such proposal within [NUMBER] working days following receipt thereof. Developer's written response shall include a statement of the availability of Developer's personnel and resources, as well as any impact the proposed changes will have on the contract price, delivery dates or warranty provisions of this Agreement. Changes to the Development Plan shall be evidenced by a \"Development Plan Modification Agreement.\" The Development Plan Modification Agreement shall amend the Development Plan appropriately to incorporate the desired changes and acknowledge any effect of such changes on the provisions of this Agreement. The Development Plan Modification Agreement shall be signed by authorized representatives of Customer and Developer, whereupon Developer shall commence performance in accordance with it. Should Developer not approve the Development Plan Modification Agreement as written, Developer will so notify Customer within [NUMBER] working days of Developer's receipt of the Development Plan Modification Agreement. Developer shall not be obligated to perform any services beyond those called for in the Development Plan prior to its approval of the Development Plan Modification Agreement.","Custom Software Development Agreement","16",116,"https://templates.business-in-a-box.com/imgs/1000px/custom-software-development-agreement-D787.png","https://templates.business-in-a-box.com/imgs/250px/787.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#787.xml",{"title":6,"description":6},[112,115],{"label":113,"url":114},"Software & Technology","software-technology-business",{"label":113,"url":114},"custom software development agreement","/template/custom-software-development-agreement-D787",{"description":119,"descriptionCustom":6,"label":120,"pages":8,"size":9,"extension":10,"preview":121,"thumb":122,"svgFrame":123,"seoMetadata":124,"parents":126,"keywords":125,"url":132},"NON-DISCLOSURE AGREEMENT (NDA) This Non-Disclosure Agreement (the \"Agreement\") is made and effective [DATE], BETWEEN: [YOUR COMPANY NAME] (the \"Disclosing Party\"), a corporation organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [YOUR COMPLETE ADDRESS] AND: [RECEIVING PARTY NAME] (the \"Receiving Party\"), an individual with his main address located at OR a corporation organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] WHEREAS, Receiving Party has been or will be engaged in the performance of work on [DESCRIBE]; and in connection therewith will be given access to certain confidential and proprietary information; and WHEREAS, Receiving Party and Disclosing Party wish to evidence by this Agreement the manner in which said confidential and proprietary material will be treated. NOW, THEREFORE, it is agreed as follows: NON-DISCLOSURE OF CONFIDENTIAL INFORMATION Both Parties understand and agree that each Party may have access to the confidential information of the other party. For the purposes of this Agreement, \"Confidential Information\" means proprietary and confidential information about the Disclosing Party's (or it's suppliers') business or activities. Such information includes all business, financial, technical, and other information marked or designated by such Party as \"confidential\" or \"proprietary.\" Confidential Information also includes information which, by the nature of the circumstances surrounding the disclosure, ought in good faith to be treated as confidential. For the purposes of this Agreement, Confidential Information does not include: Information that is currently in the public domain or that enters the public domain after the signing of this Agreement. Information a Party lawfully receives from a third Party without restriction on disclosure and without breach of a non-disclosure obligation. Information that the Receiving Party knew prior to receiving any Confidential Information from the Disclosing Party. Information that the Receiving Party independently develops without reliance on any Confidential Information from the Disclosing Party. Each Party agrees that it will not disclose to any third Party or use any Confidential Information disclosed to it by the other Party except when expressly permitted in writing by the other Party. Each Party also agrees that it will take all reasonable measures to maintain the confidentiality of all Confidential Information of the other Party in its possession or control. TERM The term of this Agreement is [number] of [years/months] from the date of execution by both Parties. TITLE The Receiving Party agrees that all Confidential Information furnished by the Disclosing Party shall remain the sole property of the Disclosing Party. DISCLAIMER","Non Disclosure Agreement Nda","https://templates.business-in-a-box.com/imgs/1000px/non-disclosure-agreement-nda-D12692.png","https://templates.business-in-a-box.com/imgs/250px/12692.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#12692.xml",{"title":125,"description":6},"non disclosure agreement nda",[127,129],{"label":33,"url":128},"business-legal-agreements",{"label":130,"url":131},"Confidentiality Agreements","confidentiality-agreement","/template/non-disclosure-agreement-nda-D12692",{"description":134,"descriptionCustom":6,"label":135,"pages":136,"size":137,"extension":10,"preview":138,"thumb":139,"svgFrame":140,"seoMetadata":141,"parents":142,"keywords":145,"url":146},"JOINT VENTURE AGREEMENT This Joint Venture Agreement (the \"Agreement\") is effective [DATE], BETWEEN: [YOUR COMPANY NAME] (the \"First Joint Venturer\"), a corporation organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [YOUR COMPLETE ADDRESS] AND: [SECOND JOINT VENTURER NAME] (the \"Second Joint Venturer\"), a corporation organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] This Agreement is entered by First Joint Venturer and Second Joint Venturer, herein after collectively referred to as the \"Joint Venturers\", for the purpose of performing: [DESCRIBE JOINT VENTURE]. WITNESSETH: WHEREAS, the parties are desirous of forming a Joint Venture (the \"Venture\"), under the laws of the [State/Province] of [STATE/PROVINCE] by execution of this Agreement for the purposes set forth herein and are desirous of fixing and defining between themselves their respective responsibilities, interests, and liabilities in connection with the performance of the before mentioned project; and NOW, THEREFORE, in consideration of the mutual covenants and promises herein contained, the Parties herein agree to constitute themselves as Joint Venturers, henceforth, \"Venturers\" for the purposes before mentioned, and intending to be legally bound hereby, the parties hereto, after first being duly sworn, do covenant, agree and certify as follows: DEFINITIONS \"Affiliate\" shall refer to (i) any person directly or indirectly controlling, controlled by or under common control with another person, (ii) any person owning or controlling 10% or more of the outstanding voting securities of such other person, (iii) any officer, director or other partner of such person and (iv) if such other person is an officer, director, joint Venturer or partner, any business or entity for which such person acts in any such capacity. \"Venturers\" shall refer to [VENTURE NAME] Inc., and any successor(s) as may be designated and admitted to the Venture. \"Internal Revenue Code\", \"Code\" or \"I.R.C.\" shall refer to the current and applicable Internal Revenue Code. \"Net Profits and Net Losses\" means the taxable income and loss of the Venture, except as follows: [DESCRIBE] The \"Book\" value of an asset shall be substituted for its adjusted tax basis if the two differ, but otherwise Net Profits and Net Losses shall be determined in accordance with federal income tax principles. \"Project\" shall refer to that certain [DESCRIBE] project known as [NAME]. \"Treasury Regulations\" shall refer to those regulations promulgated by the Department of the Treasury with respect to certain provision of Internal Revenue Code. \"Percentage of Participation\" shall refer to that figure set forth in Exhibit A. FORMATION, NAME, AND PRINCIPLE PLACE OF BUSINESS Formation (a) The Venturers do hereby form a joint venture pursuant to the laws of the State of [STATE/PROVINCE] in order for the Venture to carry on the purposes for which provision is made herein. (b) The Ventures shall execute such certificates as may be required by the laws of the [State/Province] of [STATE/PROVINCE] or of any other state in order for the Venture to operate its business and shall do all other acts and things requisite for the continuation of the Venture as a joint venture pursuant to applicable law. Name The Name and style under which the Venture shall be conducted is: [DESCRIBE]. Principal place of business The Venture shall maintain its principal place of business at [FULL ADDRESS]. The Venture may re-locate its office from time to time or have additional offices as the Venturers may determine. PURPOSE OF THE JOINT VENTURE The business of the Venture shall be to perform: [DESCRIBE], a project having the Contract # , being entitled, and being in a dollar amount of [AMOUNT], in accordance with the contract documents for the Project and all such other business incidental to the general purposes herein set forth. TERM The term of the Venture shall commence as of the date hereof and shall be terminated and dissolved upon the earliest to occur of: (i) completion of the Project and receipt of all sums due the Venture by the Owner, [OWNER NAME] pursuant thereto and payment of all laborers and material men employed by the Venture in connection with the project; (ii) [DATE]; (iii) the unanimous agreement of the Ventures; or (iv) the order of a court of competent jurisdiction. PERCENTAGE OF PARTICIPATION Description Except as otherwise provided in sections 6.0 and 9.0 hereof, the interest of the Parties in any gross profits and their respective shares in any losses and/or liabilities that may result from the filing of a joint bid and/or the performance of the Construction Contract, and their interests in all property and equipment acquired and all money received in connection with the performance of the Contract shall be as follows: [Name Joint Venture Partner Percentage] Losses The Parties agree that in the event any losses arise out of or results from the performance of the Project, each Venturer shall assume and pay the share of the losses that is equal to the percentage of participation. Liabilities If for any reason, a Venturer sustains any liabilities or is required to pay any losses arising out of or directly connected with the Project, or the execution of any surety bonds or indemnity agreements in connection therewith, which are in excess of its Percentage of Participation, in the Joint Venture, the other Venturer shall promptly reimburse such Venturer this excess, so that each and every member of the Joint Venturer will then have paid its proportionate share of such losses to the full extent of its Percentage of Participation. Indemnities The Venturers agree to indemnify each other and to hold the other harmless from, any and all losses of the Joint Venture that are in excess of such other Venturer's Percentage of Participation. Provided that the provisions of this subsection shall be limited to losses that are directly connected with or arise out of the performance of the Project and/or the execution of any bonds or indemnity agreements in connection therewith and shall not be relate to or include any incidental, indirect or consequential losses that may be sustained or suffered by a Party. Duration The Parties shall from time to time execute such bonds and indemnity agreements, including applications there and other documents that may be necessary in connection with the performance of the Project. Provided however, that the liability of each of the Parties under any agreements to indemnify a surety company or surety companies shall be limited to the percentage of the total liability assumed by all the Parties under such indemnity agreements that is equal to the Party's Percentage of Participation. Initial contribution of the venture (a) The Venturers shall contribute the Property to the Venture and their Capital Account shall each be credited with the appropriate value of such contribution in accordance with their Venture interests. (b) Except as otherwise required by law or this Agreement, the Venturers shall not be required to make any further capital contributions to the Venture. Venture interests Upon execution of this Agreement, the Venturers shall each own the following interests in the Venture: Joint Venture Partner Percentage Return of capital contributions (a) No Venturer shall have the right to withdraw his capital contributions or demand or receive the return of his capital contributions or any part thereof, except as otherwise provided in this Agreement. (b) The Venturers shall not be personally liable for the return of capital contributions or any part thereof, except as otherwise provided in this Agreement. (c) The Venture shall not pay interest on capital contributions of any Venturer.","Joint Venture Agreement","7",70,"https://templates.business-in-a-box.com/imgs/1000px/joint-venture-agreement-D889.png","https://templates.business-in-a-box.com/imgs/250px/889.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#889.xml",{"title":6,"description":6},[143,144],{"label":33,"url":128},{"label":33,"url":128},"joint venture agreement","/template/joint-venture-agreement-D889",{"description":148,"descriptionCustom":6,"label":149,"pages":136,"size":9,"extension":10,"preview":150,"thumb":151,"svgFrame":152,"seoMetadata":153,"parents":155,"keywords":154,"url":163},"EMPLOYMENT AGREEMENT - AT WILL EMPLOYEE This Employment Agreement for \"At Will\" Employee (the \"Agreement\") is made and effective this [DATE], BETWEEN: [EMPLOYEE NAME] (the \"Employee\"), an individual with his main address at: [COMPLETE ADDRESS] AND: [YOUR COMPANY NAME] (the \"Corporation\"), an entity organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [YOUR COMPLETE ADDRESS] RECITALS In consideration of the covenants and agreements herein contained and the moneys to be paid hereunder, the Corporation hereby employs the Employee and the Employee hereby agrees to perform services as an employee of the Corporation, on an \"at will\" basis, upon the following terms and conditions: APPOINTMENT The Employee is hereby employed by the Corporation to render such services and to perform such tasks as may be assigned by the Corporation. The Corporation may, in its sole discretion, increase or reduce the duties, or modify the title and job description, of the Employee from time to time, and any such increase, reduction or modification shall not be deemed a termination of this Agreement. ACCEPTANCE OF EMPLOYMENT Employee accepts employment with the Corporation upon the terms set forth above and agrees to devote all Employee's time, energy and ability to the interests of the Corporation, and to perform Employee's duties in an efficient, trustworthy and business-like manner. DEVOTION OF TIME TO EMPLOYMENT The Employee shall devote the Employee's best efforts and substantially all of the Employee's working time to performing the duties on behalf of the Corporation. The Employee shall provide services during the hours that are scheduled by the Corporation management. The Employee shall be prompt in reporting to work at the assigned time. NO CONFLICT OF INTEREST Employee shall not engage in any other business while employed by the Corporation. Employee shall not engage in any activity that conflicts with the Employees duties to the Corporation. Employee shall not provide any service or lend any aid or assistance to any party that competes with the services offered by the Corporation. Employee shall not provide any services to clients or prospective clients of the Corporation outside of the provision of services for the Corporation, whether such services are provided with or without compensation or remuneration. CORPORATION PROPERTY Employee acknowledges and agrees that while employed by the Corporation the Employee may be provided with use of computer equipment and other property of the Corporation. The use and possession of the such items shall be subject to any policies, requirements or restrictions established by the Corporation. Such items may only be used in performance of the Employee's duties for the corporation. On request of the Corporation, the Employee shall immediately deliver any such items to the Corporation. Upon termination of employment, Employee shall have the affirmative duty to return any such item to the Corporation whether a request is made or not. The obligation to return Corporation property shall extend and include any and all work product, client property, proprietary rights, intangible property, and all other property of the corporation regardless of the form or medium. COMPENSATION The Corporation shall pay the Employee such hourly compensation as determined by the Corporation. Payment shall be at the same time as the Corporations usual payroll to other employees. BONUS & BENEFITS Payment of any bonuses shall be at the complete discretion of the Corporation. No guarantee or representation that any bonuses will be paid has been made to the Employee. Standard benefits that are provided to other non-management employees shall be offered to the Employee, subject to the Corporation's policies and the terms and conditions of such benefits. WITHHOLDING All sums payable to Employee under this Agreement will be reduced by all federal, state, local, and other withholdings and similar taxes and payments required by applicable law. QUALIFICATIONS OF EMPLOYEE The employee shall satisfy all of the qualification that are established by the Corporation. TERM OF AGREEMENT There shall be no guaranteed term of employment. Employer acknowledges and agrees that Employee shall be an \"At Will\" Employee and that Employee's employment may be terminated at any time by the Corporation, with or without cause. FEES FROM EMPLOYEE'S WORK The Corporation shall have exclusive authority to determine the fees, or a procedure for establishing the fees, to be charged to clients by the Corporation for services that are provided by the Employee. All sums paid to the Employee or the Corporation in the way of fees, in cash or in kind, or otherwise for services of the Employee, shall, except as otherwise specifically agreed by the Corporation, be and remain the property of the Corporation and shall be included in the Corporation's name in such checking account or accounts as the Corporation may from time to time designate. CLIENTS AND CLIENT RECORDS The Corporation shall have the authority to determine who will be accepted as clients of the Corporation, and the Employee recognizes that such clients accepted are clients of the Corporation and not the Employee. All client records and files of any type concerning clients of the Corporation shall belong to and remain the property of the Corporation, notwithstanding the subsequent termination of the employment. POLICIES AND PROCEDURES The Corporation shall have the authority to establish from time to time the policies and procedures to be followed by the Employee in performing services for the Corporation. This may include, but is not necessarily limited to, employment policies, computer use policies, Internet access policies, email policies, and all other policies, procedures, directives, and mandates established by the Corporation, whether or not in written form or formally adopted. Employee shall abide by the provisions of any contract entered into by the Corporation under which the Employee provides services. Employee shall comply with the terms and conditions of any and all contracts entered by the Corporation. TERMINATION Employee acknowledges and agrees that Employee is an \"at will\" employee of the Corporation. As such, no term of employment is created hereby and employee may be terminated at any time in the sole discretion of the Corporation, whether there exists any cause for termination or not. CREATIONS AND INVENTIONS Employee acknowledges and agrees that any and all work product of the Employee that is conceived or created during the Employee's employment with the Corporation is the exclusive property of the Corporation. This shall include any and all copyrights, trade secrets, confidential information, patents, trademarks, trade dress, ideas, concepts, plans, business plans, business concepts, techniques, inventions, drawings, artwork, logos, graphics, web pages, databases, software, programs, CGI's, plug ins, applications, brochures, inventions, marketing plans and concepts, and all other ideas and work product of the Employee. The Employee acknowledges and agrees that all creations shall be \"works made for hire\" as defined in the [ACT OR CODE]. Notwithstanding the fact that this material may be considered to be a work made for hire, Employee agrees, during Employee's employment and thereafter, which covenant shall survive any termination of the employment relationship, to execute any and all documents requested by the Corporation to confirm the Corporation's ownership and control of all such material, including but not limited to assignments of copyright, confirmations of work for hire status, waivers of proprietary rights, copyright application, and any other documents requested by Corporation. RESTRICTIVE COVENANTS","Employment Agreement_At Will Employee","https://templates.business-in-a-box.com/imgs/1000px/employment-agreement_at-will-employee-D541.png","https://templates.business-in-a-box.com/imgs/250px/541.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#541.xml",{"title":154,"description":6},"employment agreement_at will employee",[156,159,162],{"label":157,"url":158},"Human Resources","human-resources",{"label":160,"url":161},"Hire an Employee","hire-employee",{"label":33,"url":128},"/template/employment-agreement_at-will-employee-D541",{"description":165,"descriptionCustom":6,"label":166,"pages":90,"size":9,"extension":10,"preview":167,"thumb":168,"svgFrame":169,"seoMetadata":170,"parents":172,"keywords":171,"url":175},"SERVICE AGREEMENT This SERVICE AGREEMENT (\"Agreement\") is effective [DATE], BETWEEN: [COMPANY NAME] (the \"Contractor\"), a company organized and existing under the laws of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] AND: [COMPANY NAME] (the \"Customer\"), a company organized and existing under the laws of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] (The Contractor and the Customer shall be individually referred to as a \"Party\" and collectively referred to as the \"Parties\", as the context may require). WHEREAS A. Contractor has experience and expertise in [DESCRIBE EXPERIENCE AND SERVICE]. B. Customer desires to have Contractor provide services for them. C. Contractor desires to provide services to Customer on the terms and conditions set forth herein (the \"Services\"). NOW THEREFORE, in consideration of the above recitals, the representations, warranties, and agreements contained in this Agreement and for other good and valuable consideration, the receipt and adequacy of which are now acknowledged, the Parties agree as follows: SERVICES PROVIDED Beginning on upon agreement to this contract, [CONTRACTOR] will provide to [CUSTOMER] the following service (collectively, the /Services\"): Description of the project: [DESCRIBE THE SERVICE REQUIRED]. SCOPE OF WORK Contractor agrees to provide Services pursuant to the Scope of Work set forth in Exhibit A attached hereto (the \"Scope of Work\"). TERM Unless both parties mutually agree on an extension, this contract will automatically terminate on [SPECIFY]. PERFORMANCE The parties agree to do everything possible to ensure that the terms of this Agreement take effect. PAYMENT FOR SERVICES In exchange for the Services rendered, a payment of [SPECIFY] will be made to the Contractor upon completion of the scheduled Services described in this Contract. If an invoice is not paid on the due date, interest will be added to the current balance. These amounts shall be payable, and the Customer shall pay all overdue amounts at the lesser of [SPECIFY] per cent per annum or the maximum percentage permitted by applicable law. Or Customer will pay Contractor as follows: [SPECIFY]. DELIVERY OF SERVICES The Contractor will exercise due diligence in the provision of services. However, the Customer acknowledges that the indicated delivery times and other payment milestones listed in Scope of Work are estimates and do not constitute final delivery dates. SECURITY The Contractor must make reasonable security arrangement to protect Material from unauthorized access, collection, use, alteration or disposal. OWNERSHIP RIGHT The Customer shall hold the copyright for the agreed version of the Services as delivered, and the Customer's copyright notice may be displayed in the final version. All works, ideas, discoveries, inventions, patents, products or other information that may be protected by copyright (collectively, the \"Work Product\" developed in whole or in part by the Contractor in connection with the Services, shall be the exclusive property of the Customer. Upon request, the Contractor shall execute all documents necessary to confirm or perfect the exclusive ownership of the Customer's \"Work Product\". The Contractor retains exclusive rights to pre-existing materials used in the Customer's projects. The Customer shall not have the right to reuse, resell or otherwise transfer material belonging to the contractor or third parties. The Contractor reserves the right to use the finished public product as an example of a product. RETURN OF PROPERTY Upon the expiry or termination of this Agreement, the Contractor will return to the Customer any property, documentation, records or Confidential Information which is the property of the Customer. COMPENSATION For all services rendered by the Contractor under this Agreement, the Customer shall indemnify the Contractor. In the event that the Customer fails to make any of the payments mentioned, the Contractor shall have the right, but shall not be obliged, to exercise any of the following remedies: ","Service Agreement","https://templates.business-in-a-box.com/imgs/1000px/service-agreement-D12711.png","https://templates.business-in-a-box.com/imgs/250px/12711.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#12711.xml",{"title":171,"description":6},"service agreement",[173,174],{"label":33,"url":128},{"label":33,"url":128},"/template/service-agreement-D12711",false,{"seo":178,"reviewer":190,"quick_facts":194,"at_a_glance":197,"personas":201,"variants":226,"glossary":252,"clauses":286,"how_to_fill":337,"common_mistakes":378,"faqs":403,"industries":431,"comparisons":456,"diy_vs_lawyer":468,"jurisdictions":481,"related_template_ids_curated":502,"schema":510,"classification":511},{"meta_title":179,"meta_description":180,"primary_keyword":181,"secondary_keywords":182},"Agile Team Agreement Template (Free Word)","Free Agile Team Agreement template for software and product teams. Covers roles, sprint cadence, IP, confidentiality, and dispute resolution. Free Word and PDF download.","agile team agreement template",[15,183,184,185,186,187,188,189],"agile working agreement template","scrum team agreement template","agile team contract template","team working agreement template word","agile team charter template","agile team agreement free download","software team agreement template",{"name":191,"credential":192,"reviewed_date":193},"Bruno Goulet","CEO, Business in a Box","2026-05-02",{"difficulty":195,"legal_review_recommended":196,"signature_required":196},"medium",true,{"what_it_is":198,"when_you_need_it":199,"whats_inside":200},"An Agile Team Agreement is a binding document that formalizes the operating rules, roles, responsibilities, and legal obligations of a cross-functional team working under an agile or scrum methodology. This free Word download lets you define sprint cadence, IP ownership, confidentiality, and dispute resolution in a single signed document you can edit online and export as PDF before a project kicks off.\n","Use it when assembling a new product or software development team that includes contractors, freelancers, or employees from different organizations — or any time multiple parties must share deliverables, IP, and decision-making authority under an iterative delivery framework.\n","Party identification and roles, sprint and ceremony cadence, definition of done, IP assignment, confidentiality obligations, change management process, dispute resolution, and governing law — covering both the operational norms and the legal obligations that hold the team accountable.\n",[202,206,210,214,218,222],{"title":203,"use_case":204,"icon_asset_id":205},"Product managers","Establishing enforceable ground rules before a multi-team product sprint begins","persona-product-manager",{"title":207,"use_case":208,"icon_asset_id":209},"Software development agencies","Formalizing client-facing delivery commitments and IP ownership on agile engagements","persona-agency",{"title":211,"use_case":212,"icon_asset_id":213},"Startup CTOs","Aligning a mixed team of employees and contractors under a single operating agreement","persona-cto",{"title":215,"use_case":216,"icon_asset_id":217},"Enterprise scrum masters","Documenting team norms and escalation paths for a scaled agile program","persona-operations-director",{"title":219,"use_case":220,"icon_asset_id":221},"Freelance developers and consultants","Clarifying IP, confidentiality, and billing terms before joining a client agile team","persona-freelancer",{"title":223,"use_case":224,"icon_asset_id":225},"IT project managers","Governing a cross-departmental agile delivery team within a regulated enterprise","persona-it-manager",[227,231,234,237,240,244,248],{"situation":228,"recommended_template":229,"slug":230},"Engaging an external agency to deliver a product on an agile sprint model","Software Development Agreement","custom-software-development-agreement-D787",{"situation":232,"recommended_template":89,"slug":233},"Formalizing a single freelancer's contribution to a scrum team","independent-contractor-agreement-D160",{"situation":235,"recommended_template":48,"slug":236},"Documenting team norms without legal enforcement (internal teams only)","team-charter-D13479",{"situation":238,"recommended_template":135,"slug":239},"Governing a multi-party joint venture building a shared product","joint-venture-agreement-D889",{"situation":241,"recommended_template":242,"slug":243},"Hiring a full-time scrum team member as a permanent employee","Employment Contract","employment-agreement_at-will-employee-D541",{"situation":245,"recommended_template":246,"slug":247},"Protecting shared IP and trade secrets across all team members","Non-Disclosure Agreement","non-disclosure-agreement-nda-D12692",{"situation":249,"recommended_template":250,"slug":251},"Defining service-level commitments in a client-facing agile engagement","Service Level Agreement","service-level-agreement-D778",[253,256,259,262,265,268,271,274,277,280,283],{"term":254,"definition":255},"Agile Methodology","An iterative approach to project delivery that breaks work into short cycles called sprints, prioritizes continuous feedback, and adapts scope based on learning.",{"term":257,"definition":258},"Sprint","A fixed-length development cycle — typically 1 to 4 weeks — during which a team commits to delivering a specific set of work items.",{"term":260,"definition":261},"Definition of Done","A shared, documented checklist that specifies the criteria a deliverable must meet before the team considers it complete and releasable.",{"term":263,"definition":264},"Product Backlog","An ordered list of all desired work items for a product, maintained by the product owner and continuously refined based on priority and feedback.",{"term":266,"definition":267},"Scrum Master","The team member responsible for facilitating agile ceremonies, removing blockers, and ensuring the team adheres to the agreed process.",{"term":269,"definition":270},"Intellectual Property Assignment","A contractual clause transferring ownership of work product, code, and inventions created by team members to a designated party — typically the client or employer.",{"term":272,"definition":273},"Velocity","The average amount of work a team completes in a sprint, measured in story points or hours, used to forecast delivery timelines.",{"term":275,"definition":276},"Retrospective","A ceremony held at the end of each sprint where the team reviews what went well, what didn't, and what process changes to implement next sprint.",{"term":278,"definition":279},"Acceptance Criteria","Specific, pre-agreed conditions that a deliverable must satisfy for the product owner or client to formally accept it as complete.",{"term":281,"definition":282},"Change Control","A formal process for evaluating, approving, and documenting any modifications to agreed scope, timeline, or budget during an agile engagement.",{"term":284,"definition":285},"Governing Law","The jurisdiction whose laws apply to interpret and enforce the agreement — typically the state, province, or country where the primary party operates.",[287,292,297,302,307,312,317,322,327,332],{"name":288,"plain_english":289,"sample_language":290,"common_mistake":291},"Parties, roles, and team composition","Identifies every party to the agreement — client, agency, individual contributors — and assigns a formal role (product owner, scrum master, developer) to each.","This Agile Team Agreement ('Agreement') is entered into on [DATE] between [CLIENT LEGAL NAME] ('Client') and [AGENCY / CONTRACTOR LEGAL NAME] ('Service Provider'). The team shall consist of the following roles: Product Owner — [NAME]; Scrum Master — [NAME]; Development Team — [NAMES OR TITLES].","Listing team members by first name only, without their legal entity or employment relationship. When a dispute arises, it becomes unclear which party bears responsibility for a specific contributor's work product or actions.",{"name":293,"plain_english":294,"sample_language":295,"common_mistake":296},"Scope of work and backlog ownership","Defines the initial product backlog, who owns and prioritizes it, and the boundaries of what is in and out of scope for the engagement.","The initial Product Backlog is set out in Schedule A. The Product Owner retains sole authority to re-prioritize backlog items between sprints. Work items outside Schedule A require a written Change Order signed by both parties before work begins.","Failing to attach the initial backlog as a schedule. Scope creep in agile engagements is the most common source of billing disputes, and an undefined starting backlog leaves no baseline to measure against.",{"name":298,"plain_english":299,"sample_language":300,"common_mistake":301},"Sprint cadence and delivery ceremonies","Sets the sprint length, the dates and format of planning, review, and retrospective ceremonies, and the team's standard working hours and communication channels.","Sprints shall run for [2] calendar weeks, commencing [DAY]. The following ceremonies are mandatory: Sprint Planning ([DAY, TIME, LOCATION/LINK]); Sprint Review ([DAY, TIME]); Retrospective ([DAY, TIME]). The team's core hours are [START TIME] to [END TIME] [TIMEZONE].","Treating ceremony schedules as informal — omitting them from the agreement entirely and relying on calendar invites. When a party claims the team failed to deliver reviews or planning sessions, there is nothing to point to as the agreed standard.",{"name":303,"plain_english":304,"sample_language":305,"common_mistake":306},"Definition of done and acceptance criteria","Documents the shared criteria that must be satisfied before any deliverable is considered complete, and the process for the client to formally accept or reject sprint output.","A deliverable is 'Done' when it meets all criteria in Schedule B ('Definition of Done'). The Product Owner shall provide written acceptance or rejection within [5] business days of a Sprint Review. Silence after [5] business days constitutes acceptance.","Omitting the acceptance window entirely. Without a defined deadline for client feedback, development teams are left in limbo — unable to invoice, close sprints, or move forward with dependent work.",{"name":308,"plain_english":309,"sample_language":310,"common_mistake":311},"Intellectual property assignment","Assigns ownership of all work product, code, designs, and deliverables created during the engagement to the designated party, effective upon full payment.","Upon receipt of full payment for each sprint, Service Provider irrevocably assigns to Client all right, title, and interest in and to all work product, code, and deliverables created under this Agreement, including all associated intellectual property rights.","Conditioning IP transfer on final project completion rather than sprint-by-sprint payment. If the engagement ends early, the client may have paid for months of work but received no assignable IP.",{"name":313,"plain_english":314,"sample_language":315,"common_mistake":316},"Confidentiality and data handling","Prohibits team members from disclosing the client's business information, source code, product roadmap, and customer data — during and after the engagement.","Each party shall hold in strict confidence all Confidential Information of the other party and shall not disclose it to any third party without prior written consent. 'Confidential Information' includes, without limitation, source code, product roadmaps, customer data, and financial information.","Using the same confidentiality clause for both a three-person internal team and a 20-person cross-company program. The clause should define who within each organization may access confidential information — a general 'employees only' carve-out is too broad for large distributed teams.",{"name":318,"plain_english":319,"sample_language":320,"common_mistake":321},"Change management and scope modification","Establishes the formal process for requesting, evaluating, pricing, and approving any changes to scope, timeline, or budget beyond the agreed backlog.","Either party may request a scope change by submitting a written Change Order to the other party. Change Orders must specify the requested modification, estimated effort in story points or hours, adjusted timeline, and additional fees. No change is effective until signed by both parties.","Allowing verbal change approvals during sprint planning calls. Verbal scope expansions are routinely disputed at invoicing; a signed Change Order requirement eliminates the ambiguity.",{"name":323,"plain_english":324,"sample_language":325,"common_mistake":326},"Fees, payment schedule, and invoicing","States the fee structure (fixed per sprint, time-and-materials, or retainer), the invoicing trigger, the payment window, and the late-fee penalty.","Client shall pay Service Provider [$X] per sprint, invoiced on the last day of each sprint. Payment is due within [15] business days of invoice. Overdue balances accrue interest at [1.5]% per month. Service Provider may suspend work after [10] business days of non-payment.","Tying invoicing to project milestones rather than sprint completion. Milestone-based billing in agile engagements routinely stalls because milestones shift — sprint-based billing keeps cash flow predictable for both parties.",{"name":328,"plain_english":329,"sample_language":330,"common_mistake":331},"Term, termination, and offboarding","Sets the agreement's duration, the notice required to terminate, what happens to in-progress sprints on termination, and the handover obligations of each party.","This Agreement commences on [START DATE] and continues until the Product Backlog is complete or either party provides [30] days' written notice of termination. On termination, Service Provider shall deliver all completed work product and documentation within [10] business days. Client shall pay for all work completed through the termination date.","No offboarding obligation clause. When an engagement ends abruptly, teams routinely leave without transferring code repositories, documentation, or credentials — creating weeks of recovery work and operational disruption for the client.",{"name":333,"plain_english":334,"sample_language":335,"common_mistake":336},"Governing law and dispute resolution","Specifies which jurisdiction's law governs the agreement and the mechanism for resolving disputes — typically negotiation, then mediation, then arbitration or litigation.","This Agreement is governed by the laws of [STATE/PROVINCE/COUNTRY]. Any dispute not resolved within [30] days of written notice shall be submitted to binding arbitration administered by [AAA/JAMS/ICAC] in [CITY]. Either party may seek injunctive relief in court without this requirement.","Selecting a governing jurisdiction with no connection to where either party operates or where the work is performed. Courts in some jurisdictions refuse to honor choice-of-law clauses that are purely strategic and lack any nexus to the parties or the work.",[338,343,348,353,358,363,368,373],{"step":339,"title":340,"description":341,"tip":342},1,"Identify all parties and assign formal roles","Enter the full legal name of every organization and individual contributor bound by the agreement. Assign a specific agile role — product owner, scrum master, developer, QA lead — to each party or representative.","For contractors and freelancers, confirm whether they are contracting individually or through a corporate entity — this determines which name appears on the agreement and who carries liability.",{"step":344,"title":345,"description":346,"tip":347},2,"Attach the initial product backlog as Schedule A","Export your current backlog from your project management tool (Jira, Linear, Trello) and attach it as Schedule A. At minimum, include the top 20 prioritized items with brief descriptions and estimated effort.","Mark Schedule A with the export date so both parties know the baseline scope at signing — any addition after that date requires a Change Order.",{"step":349,"title":350,"description":351,"tip":352},3,"Set the sprint cadence and ceremony schedule","Enter the sprint length (1, 2, or 4 weeks), the day sprints start and end, and the recurring dates, times, and video links for planning, review, and retrospective ceremonies.","Lock the sprint length for at least the first three sprints — teams that change sprint length mid-engagement consistently underperform on velocity predictability.",{"step":354,"title":355,"description":356,"tip":357},4,"Define the definition of done in Schedule B","List the specific criteria every deliverable must meet — code reviewed and merged, tests written and passing, documentation updated, product owner demo completed. Attach as Schedule B.","Write the definition of done in plain English, not engineering jargon, so the client can independently verify completion without a technical translator.",{"step":359,"title":360,"description":361,"tip":362},5,"Complete the IP assignment and payment linkage","Confirm that IP transfers sprint by sprint upon payment, not at project end. Enter the sprint fee, invoice trigger date, and the number of days the client has to pay before late fees accrue.","Sprint-level IP transfer creates a clear audit trail — if a dispute arises mid-project, each party knows exactly which deliverables are legally owned by whom.",{"step":364,"title":365,"description":366,"tip":367},6,"Tailor the confidentiality clause to team size","Define which team members on each side have access to confidential information and add a named-personnel list if the team is large or includes subcontractors.","If any team members are in the EU, add a GDPR-compliant data processing addendum — handling personal data without one exposes both parties to regulatory risk.",{"step":369,"title":370,"description":371,"tip":372},7,"Complete the termination and offboarding terms","Enter the notice period (30 days is standard), the sprint completion obligation on notice, and the specific deliverables required at offboarding — code repo access, credentials, documentation, and handover sessions.","Specify the exact format for credential handover (e.g., password manager export or designated handover meeting) to avoid disputes about whether handover was 'complete.'",{"step":374,"title":375,"description":376,"tip":377},8,"Sign before the first sprint begins","Both parties must execute the agreement before sprint day one. Unsigned agreements mean IP assignment and confidentiality clauses are unenforceable for any work already delivered.","Use an e-signature tool to timestamp execution and distribute signed copies automatically — execution delays are the single most common reason teams start work unprotected.",[379,383,387,391,395,399],{"mistake":380,"why_it_matters":381,"fix":382},"Starting the first sprint before the agreement is signed","Any work delivered before signing has no enforceable IP assignment, confidentiality protection, or payment obligation. A client who receives sprint output before signing can dispute ownership or refuse to pay with no binding recourse.","Treat the signed agreement as a prerequisite for sprint day one — block the first planning session in your calendar until execution is confirmed.",{"mistake":384,"why_it_matters":385,"fix":386},"No attached initial backlog","Without a documented baseline scope, every addition looks like a continuation of the original work rather than a change. Agencies routinely absorb months of unbilled scope expansion because they cannot prove what was in versus out of scope at signing.","Attach the backlog as Schedule A at signing, date-stamp it, and require a signed Change Order for any item added after that date.",{"mistake":388,"why_it_matters":389,"fix":390},"Verbal change approvals during sprint planning","Sprint planning calls are fast-moving — what sounds like a quick addition often represents hours of additional work. Verbal approvals are routinely disputed at invoicing, leaving the team unpaid for completed work.","Include an explicit clause requiring written Change Orders for all scope modifications and enforce it consistently from sprint one.",{"mistake":392,"why_it_matters":393,"fix":394},"IP transfer conditioned on final project completion","Agile engagements frequently end before full project completion. If IP only transfers at project end, a client who terminates mid-project has paid for delivered work but received no legally assignable assets.","Tie IP assignment to sprint-level payment so ownership transfers incrementally as work is delivered and paid for.",{"mistake":396,"why_it_matters":397,"fix":398},"Omitting the acceptance window for sprint deliverables","Without a defined deadline for the product owner to accept or reject sprint output, teams cannot close sprints, invoice, or begin the next sprint with confidence. Disputes about whether work was 'actually accepted' stall payment for weeks.","Set a specific acceptance window — typically 3 to 5 business days after the sprint review — and include a silence-equals-acceptance clause if the window lapses without response.",{"mistake":400,"why_it_matters":401,"fix":402},"No offboarding obligations clause","When an engagement ends, teams that have not contractually committed to handover routinely leave without transferring repositories, documentation, credentials, or institutional knowledge — costing the client weeks of recovery time.","Specify in the agreement exactly what must be transferred at offboarding, the format, and the deadline — typically 10 business days after the termination date.",[404,407,410,413,416,419,422,425,428],{"question":405,"answer":406},"What is an Agile Team Agreement?","An Agile Team Agreement is a binding contract that formalizes the operating rules, roles, and legal obligations of a team working under an agile or scrum framework. It covers sprint cadence, definition of done, IP ownership, confidentiality, change management, fees, and dispute resolution in a single signed document. Unlike an informal team charter, it creates enforceable obligations for all parties — including contractors, agencies, and client-side contributors.\n",{"question":408,"answer":409},"Is an Agile Team Agreement legally binding?","Yes, when properly executed, an Agile Team Agreement is generally enforceable as a contract in most jurisdictions. It must include the standard elements of a binding contract: offer, acceptance, and consideration — typically the exchange of services for fees. Signatures from authorized representatives of each party are required; e-signatures are generally accepted under laws such as the US ESIGN Act, Canada's PIPEDA, and the EU eIDAS Regulation.\n",{"question":411,"answer":412},"What is the difference between an Agile Team Agreement and a working agreement?","A working agreement is an informal set of team norms — communication preferences, meeting etiquette, and collaboration practices — that teams create collaboratively but typically do not sign. An Agile Team Agreement is a formal legal contract covering IP assignment, confidentiality, payment terms, and dispute resolution. Working agreements govern behavior; team agreements govern obligations. Teams that include contractors or external agencies need the legal contract; purely internal teams may find a working agreement sufficient.\n",{"question":414,"answer":415},"Who should sign an Agile Team Agreement?","Any party with a formal role and legal obligation under the engagement should sign — typically the client organization, the agency or primary contractor, and any key individual contributors who are not employees of either primary party. Employees of a signatory organization are bound through their employment relationship and generally do not need to sign separately, though adding a confidentiality acknowledgment for team members with access to sensitive data is a common practice.\n",{"question":417,"answer":418},"Does an Agile Team Agreement replace a Statement of Work or Service Agreement?","Not necessarily. An Agile Team Agreement governs the team's operating model, process norms, and legal obligations for the duration of the engagement. A Statement of Work (SOW) typically defines a specific deliverable, timeline, and price for a discrete project. For large engagements, both documents are used together — the master service agreement or Agile Team Agreement sets overarching terms, and individual SOWs define sprint-level or phase-level scope under those terms.\n",{"question":420,"answer":421},"How should intellectual property be handled in an Agile Team Agreement?","IP should transfer from the service provider to the client on a sprint-by-sprint basis, conditioned on full payment for that sprint. This protects both parties: the client receives assignable IP incrementally as they pay, and the service provider retains a lien on unpaid work. The agreement should also address pre-existing IP — tools, frameworks, and libraries the agency brings to the engagement — which typically remain with the service provider under a license grant to the client.\n",{"question":423,"answer":424},"What notice period is standard for terminating an Agile Team Agreement?","Thirty days is the most common notice period for agile engagements, aligning with typical two-week sprint cycles and allowing one full sprint to complete in-progress work and begin knowledge transfer. Some longer engagements use 60-day notice periods for senior or highly specialized team configurations. Either party should be able to terminate for material breach on shorter notice — typically 10 business days after written notice of breach if the breach is not cured.\n",{"question":426,"answer":427},"Can a client unilaterally change the product backlog during the engagement?","The product owner typically holds the right to re-prioritize backlog items between sprints, which is a core feature of agile methodology. However, adding significant new work items — beyond re-prioritizing existing ones — should require a signed Change Order. The agreement should distinguish between routine backlog refinement, which the product owner controls, and material scope additions, which require mutual written agreement and a fee adjustment.\n",{"question":429,"answer":430},"Do I need a lawyer to draft an Agile Team Agreement?","For straightforward domestic engagements between two parties with standard IP and payment terms, a high-quality template is typically sufficient. Legal review is advisable when the engagement involves parties in multiple jurisdictions, sensitive data subject to regulatory requirements (HIPAA, GDPR), significant IP value, or complex equity or revenue-sharing arrangements. A 1 to 2 hour lawyer review typically costs $300 to $600 and is worthwhile for engagements exceeding $50,000 in total contract value.\n",[432,436,440,444,448,452],{"industry":433,"icon_asset_id":434,"specifics":435},"Software and SaaS","industry-saas","Sprint-level IP assignment for proprietary code, pre-existing library license carve-outs, and data processing addenda for SaaS platforms handling user data.",{"industry":437,"icon_asset_id":438,"specifics":439},"Financial services","industry-fintech","Regulatory compliance obligations (SOC 2, PCI-DSS) referenced by the confidentiality clause, audit access rights for client security teams, and enhanced data handling restrictions.",{"industry":441,"icon_asset_id":442,"specifics":443},"Healthcare and MedTech","industry-healthtech","HIPAA Business Associate Agreement incorporated by reference, strict access controls on patient data, and FDA software validation obligations tied to the definition of done.",{"industry":445,"icon_asset_id":446,"specifics":447},"Professional services and consulting","industry-professional-services","Client non-solicitation of team members post-engagement, billing by story point or hour with sprint-level reconciliation, and deliverable-based acceptance tied to client sign-off.",{"industry":449,"icon_asset_id":450,"specifics":451},"E-commerce and retail technology","industry-ecommerce","Integration with third-party platforms (Shopify, Salesforce) governed by a sub-licensing clause, seasonal sprint velocity adjustments, and payment gateway security compliance.",{"industry":453,"icon_asset_id":454,"specifics":455},"Government and public sector","industry-government","Security clearance and background check requirements attached as conditions of team membership, mandatory open-source compliance, and procurement-compliant invoicing formats.",[457,459,462,465],{"vs":89,"vs_template_id":233,"summary":458},"An Independent Contractor Agreement governs the relationship between a single contractor and a client — covering deliverables, rate, IP, and termination for one individual. An Agile Team Agreement governs an entire multi-role team operating under a shared process framework. Use the contractor agreement for a sole contributor; use the team agreement when two or more parties must align on sprint norms, joint IP, and shared delivery obligations.",{"vs":229,"vs_template_id":460,"summary":461},"software-development-agreement-D13246","A Software Development Agreement defines the scope, price, and delivery terms for a specific software product — typically with fixed milestones and a defined acceptance process. An Agile Team Agreement is process-oriented, governing how an ongoing team operates across sprints rather than a single deliverable. For long-running agile engagements, the team agreement is the governing document; a software development agreement is better suited to fixed-scope, milestone-based projects.",{"vs":250,"vs_template_id":463,"summary":464},"D{SERVICE_LEVEL_AGREEMENT_ID}","A Service Level Agreement (SLA) quantifies uptime, response times, and performance standards for a delivered service — typically post-launch. An Agile Team Agreement governs the delivery process itself, not the operational performance of what is built. In practice, both documents are often used together: the team agreement covers the build phase, and the SLA governs the live product.",{"vs":135,"vs_template_id":466,"summary":467},"joint-venture-agreement-D182","A Joint Venture Agreement creates a new legal entity or formal profit-sharing arrangement between two organizations building something together. An Agile Team Agreement creates a working relationship with defined process norms and IP terms but does not create a new legal entity or shared ownership structure. If two companies are co-developing a product and intend to share revenue or equity, a joint venture agreement is the appropriate instrument.",{"use_template":469,"template_plus_review":473,"custom_drafted":477},{"best_for":470,"cost":471,"time":472},"Domestic single-jurisdiction engagements between two parties with standard IP and payment terms","Free","30 minutes",{"best_for":474,"cost":475,"time":476},"Engagements over $50,000, cross-border teams, or projects involving sensitive data under GDPR or HIPAA","$300–$600","1–3 days",{"best_for":478,"cost":479,"time":480},"Complex multi-party programs, joint IP development, revenue-sharing arrangements, or regulated industries requiring bespoke compliance clauses","$1,500–$4,000+","1–3 weeks",[482,487,492,497],{"code":483,"name":484,"flag_asset_id":485,"note":486},"us","United States","flag-us","IP assignment clauses must be explicit — courts in most states do not imply assignment from a work-for-hire relationship unless the contributor is a W-2 employee. California Labor Code §2870 limits the scope of IP assignment for work performed off company premises on personal time; tailor the clause if any team members are California-based. Non-solicitation clauses for team members are generally enforceable in most states but unenforceable in California.",{"code":488,"name":489,"flag_asset_id":490,"note":491},"ca","Canada","flag-ca","Canada's Copyright Act vests copyright in the creator by default for independent contractors — explicit written assignment is required to transfer ownership to the client. Provincial employment standards do not apply to independent contractors, but misclassification risk is significant; ensure the agreement clearly establishes the contractor relationship. Quebec law requires that contracts intended to bind Quebec parties be available in French.",{"code":493,"name":494,"flag_asset_id":495,"note":496},"uk","United Kingdom","flag-uk","Under the Copyright, Designs and Patents Act 1988, works created by employees in the course of employment automatically vest in the employer, but contractor-created work does not — written assignment is essential. IR35 rules may treat certain contractor arrangements as disguised employment, affecting tax obligations for both the engaging client and the contractor. Post-Brexit, GDPR equivalents under the UK GDPR apply to any personal data handled by the team.",{"code":498,"name":499,"flag_asset_id":500,"note":501},"eu","European Union","flag-eu","GDPR requires a Data Processing Agreement (DPA) whenever personal data is shared between parties — for agile teams handling user data, the DPA should be attached as a schedule to this agreement. IP assignment rules vary by member state; in Germany and France, moral rights cannot be fully waived, which may affect how deliverables are credited. The EU's Transparent and Predictable Working Conditions Directive may impose written information obligations for certain contractor relationships depending on the member state.",[233,230,247,239,243,503,504,505,506,507,508,509],"service-agreement-D12711","master-service-agreement-D12657","statement-of-work-D12981","intellectual-property-assignment-D5229","project-proposal-D12678","consulting-agreement-D13226","change-order-D13613",{"emit_how_to":196,"emit_defined_term":196},{"primary_folder":128,"secondary_folder":512,"document_type":513,"industry":514,"business_stage":515,"tags":516,"confidence":522},"partnerships-and-joint-ventures","agreement","general","all-stages",[517,518,519,520,521],"project-management","legal","agile","team-agreement","scrum",0.85,"\u003Ch2>What is an Agile Team Agreement?\u003C/h2>\n\u003Cp>An \u003Cstrong>Agile Team Agreement\u003C/strong> is a legally binding contract that formalizes the operating rules, roles, and mutual obligations of a cross-functional team working under an agile or scrum delivery framework. It goes beyond an informal set of team norms by establishing enforceable terms for IP ownership, confidentiality, sprint cadence, acceptance criteria, change management, fees, and dispute resolution — in a single document signed before the first sprint begins. Where an informal working agreement captures how a team prefers to collaborate, an Agile Team Agreement creates legal accountability for what is delivered, who owns it, how changes are governed, and what happens when the engagement ends.\u003C/p>\n\u003Ch2>Why You Need This Document\u003C/h2>\n\u003Cp>Without a signed Agile Team Agreement, every sprint your team completes creates unresolved legal exposure. IP produced by contractors does not automatically transfer to the client in most jurisdictions — work can be delivered, paid for, and still legally owned by the developer who wrote it. Scope creep goes unbilled because there is no baseline to measure against. Sprint output sits in a legal gray area until a product owner formally accepts it — and without a defined acceptance window, that moment never comes. When an engagement ends abruptly, teams leave without transferring repositories, credentials, or documentation because no handover obligation exists. Each of these gaps is a dispute waiting to happen. This template closes all of them before sprint one, giving both the client and the delivery team a clear, enforceable record of what was agreed — so the focus stays on shipping product rather than litigating who owns it.\u003C/p>\n",1781185995106]