Laserfiche WebLink
<br />PAGE 15 <br /> Coordinate s resources to confirm and support the Axon <br />DataStore , configuration of standard reports , and production <br />of agency -specific reports to support normal operations . <br /> <br />3.2 REQUIREMENTS PLANNING <br />All p roject requirements will be documented during the k ick -off and <br />d iscovery phases of the project . <br />Once the agency and Axon agree on all requirements, Axon’s p roject <br />m anager will work with the a gency’s p roject m anager to develop a <br />p roject p lan for Axon’s implementation. <br /> <br />3.3 CHANGE CONTROL <br />If any changes in the p roject cause a material increase or decrease in <br />fees , as determined by Axon, an adjustment in the fees will be agreed <br />upon between the a gency and Axon. All PCO forms must be approved <br />and signed by the a gency authority (Attachment_B ). <br />The a gency acknowledges a proposed change request might have an <br />impact on both scheduling and cost for the p roject that will be outlined <br />in the PCO form. <br /> <br />3.4 PROJECT METHODOL OGY <br />Axon utilizes a hybrid approach to project management, utilizing <br />aspects of both Agile and Waterfall methodologies. We use Waterfall for <br />the overall project, with respect to major milestones. We utilize Agile <br />during the configuration and build phases of the project. <br /> <br />3.5 MILESTONE COMPLETIO N REPORT (“MCR”) <br />Axon will submit an MCR to the a gency for approval upon completion of <br />a m ilestone. Milestone Completion Report included (Attachment A ). <br />Upon receiving an MCR, the a gen cy has 1 4 calendar days to approve the <br />m ilestone c ompletion. If the a gency has issues related to the m ilestone <br />c ompletion, the expectation is that the a gency will respond in writing to <br />Axon with any issues related to the MC R within the 14 calendar -day <br />wind ow. <br />DocuSign Envelope ID: A69C2874-A23C-4EBA-AE3F-17C057920A28