Evidence: Generally you will use sections to summarize the results of testing which do not include the potentially hundreds of detailed results, however, you should include all detailed testing results in an appendix or an attachment.Ideally, the technology spike digs into a number of technical questions and gets answers so that the broader project team can then come back together and agree on an appropriate course forward. Fact-Finding: The goal of a spike should be fact-finding, not decision-making or recommendation.The technology needs to be tested on a new platform.A new version of the technology has been released.There are many reasons that the evaluation environment may need to be rebuilt. so that testing could be performed again. If any testing is performed, make sure to include the scripts, links to the applications, configuration options, etc. required to build the environment that was used for evaluation and testing. Make sure it is repeatable: Detail the components used, installation instructions, configuration, etc. This is helpful to ensure that the technical spike was productive and advanced the overall project in some way.
Problem Statement/Goals: Be sure to include a section that clearly details why an evaluation is being done and what the outcome of this evaluation should be.The specifics contained in the document will vary, but there are some general principles that might be helpful. Generally the deliverable from a Technical Spike should be a document detailing what was evaluated and the outcome of that evaluation. A functional spike is used to determine the interaction with a new feature or implementation.Įngineering feasibility spikes can also be conducted to de-risk an engagement and increase the team's understanding.
The technical spike is used more often for evaluating the impact new technology has on the current implementation. Spike tests can also be used to mitigate future risk, and may uncover additional issues that have escaped notice.Ī distinction can be made between technical spikes and functional spikes.To analyze a problem thoroughly and assist in properly dividing work among separate team members.
WORK SPIKE MEANING SOFTWARE
0 kommentar(er)
