Generally I only apply for RoadTests that I can provide information that might be of benefit to someone else.
Sometimes I have a good use that might be slightly different from the normal.
It would be nice to treat them as a learning opportunity, but the reality is that 60 days is often a bit short for that, given the other tasks/workload.
Generally I only apply for RoadTests that I can provide information that might be of benefit to someone else.
Sometimes I have a good use that might be slightly different from the normal.
It would be nice to treat them as a learning opportunity, but the reality is that 60 days is often a bit short for that, given the other tasks/workload.
I would have similar sentiments. I would typically have an idea first about how I could develop something using this new untested technology and then take a view that I am documenting the learning experience for the benefit of others, as everyone has to go through this process when trying out any new technology. Then as you begin the roadtest process, it is a bit like any assignment with a deadline. You weigh up your idea against degree of effort and own abilities (or more likely your own familiarities), and adapt accordingly to hopefully provide a useful report for others to read and learn from.
I am sure others have been there before where someone in your organisation / business wants an idea implemented and you know what kit could be used but you and the team have limited experience implementing as not familiar with all or parts of the kit and the development platform. You are then put on the spot when pushed to give an assessment on when you would have something ready to demo to others. Either the kit fails or you as a team fail... or you get it right on the night.
So, I think the 60 days is fine as this gives a good indication as to how far you can get versus expectation.
Top Comments