RoadTester Review Score Card

Hello,

colporteur said:

any member came across a page that provide RoadTest statics similar to a hockey sports page?

This doesn't exist at present. Let's have a look over, from a staff perspective, why:

colporteur said:

I'm not sure if this question would have fit better in the Feedback and Support page

It's fine that it isn't. This sounds like a wider discussion question anyway.

colporteur said:

RoadTest Description

We can probably pull this automatically into a 'widget' or 'list as we have that information available, which user has done a roadtest.

colporteur said:

Technology Groups

Not sure what this would be exactly, I suppose a category of what type of hardware it is? We don't have this readily available as I don't think it's stored against each roadtest at present.

colporteur said:

Kits

Yeah that would be available as each roadtest has a 'product' or 'products' against it, but arguably you could gleam this from the roadtest description.

colporteur said:

Applicants

We currently track that, so we could surface that info' - I'm not sure why that's valuable to an individual applicant that was successful?

colporteur said:

# Application short listed

I'm guessing this would be whether or not you were selected for the roadtest? Presumably we would only list roadtests in this list if you were short listed for it? Or is this something else?

colporteur said:

# Awarded Applications

This sounds similar to the previous one to me. From a roadtest content perspective I think this is now stored and could be surfaced automatically, because if you're not selected for a product then you're not allowed to produce a review.

colporteur said:

# Reviews submitted before deadline

This would have to be manually collected together, so is less likely to be done. We don't enforce an end date for posting a review in the platform (maybe we should to keep better track of it?) because ultimately we're happy when a review's posted at all and we are sometimes lenient, people have lives.

colporteur said:

# Reviews with extended deadlines

Same as previous one really.

colporteur said:

# Reviews that failed to meet deadline

I feel this isn't constructive, but if you wanted to keep track of what reviews you've managed to do before deadline, within an extended deadline, and failed to meet deadline, and that's useful to you, then it would have to be manually collated at present and isn't in the site. Personally I don't feel it's good to be reminded of where I haven't met an arbitrary deadline for something I'm doing almost voluntarily.

colporteur said:

# RoadTest Date Extended after release

We don't store the 'original date' vs the 'extended date' for a roadtest, so this would also be manual rather than automatically from the site.

I can see some merit to having summary statistics of what a member has done on the site and having it made sense of. Perhaps you have goals or want to manage your time. I'm also hesitant because it's easy to get over-neurotic about this sort of thing. I once worked with someone who'd hate me to assess what we were doing and go "Ok, we have 10 desks to re-wire, and we've done 2, 8 to go" because they simply wanted to get on with it and it stressed them otherwise. Where as I found it useful to gauge how much time I had left and what would need to be done the next day.

I challenge examining data points individually. This Approach waters down the value than when they are paired with other data points.

I discovered the value of data sets while working in digital television distribution. The system stored every channel change made by every customer. If you married that data with the knowledge of what content was on the channel at the time the channel was changed you create a data set for marketing. If I know a viewer watches sport fishing shows, than I groom your commercial stream to fishing products and reduce the home improvement content.

Take for example these data points.

Technology Groups
# Kits
# Applicants
# Application short listed
# Awarded Applications

What type of RoadTest Technology attracts the most applicants?

There is a Technologies Forum. I see some value in linking that to RoadTests. If I select FPGA in the forum, knowing there are specific RoadTest reviews that are in that technology group has merit.

I enjoy mining data. RoadTest Review is one of the places I like to have a few core samples.

I agree, and it's an underlying principle of what determines what's considered 'personally identifiable information' for example, alone an ip address doesn't mean anything, but as soon as you pair it with an e-mail address and a username, suddenly it's far more valuable.

colporteur said:

There is a Technologies Forum. I see some value in linking that to RoadTests.

You're right, especially if that's the first touch point for a person visiting the Community - there are a lot of 'missed' opportunities like this, and a difficulty we have is using the Verint platform to be able to do that, and other customers also have this problem, and Verint think they have a solution to it (they don't).

I seem to recall, I chimed in on a discussion on PII as it related new users. When the site was moved data that displayed when a user joined was no longer available because of privacy concerns. It no longer possible to identify newly minted members. In combining data PII needs to be addressed.

RoadTest reviews are like flypaper. Anything buzzing around that comes in contact with it gets stuck. The program coordinators have a tough job picking the beneficial bugs of the paper. I believe RoadTest reviews are a valuable component to the community and constantly looking to improve it is a must.

I appreciate the constraints for the site. Requirements developed post a project implementation may have value but can be hard to realize.

colporteur said:

It no longer possible to identify newly minted members.

The amount of points they have is a good indicator.

colporteur said:

Requirements developed post a project implementation may have value but can be hard to realize.

It's going to be easier when we've fixed the back-end reporting on these custom content types.

colporteur said:

Requirements developed post a project implementation may have value but can be hard to realize.

That is my daytime job. Scrum master for continuous improvements. This year most likely a few 100s .

My condolences on your career path:)

It is bad enough having to implement a project that has poor requirements, is not sufficiently funded, insufficient time allocated and limited resource. When the project is complete trying to add the stuff that got missed under the same constraints is near impossible.

colporteur said:

is near impossible.

I love it, it pays my food and I'll make it possible, and repeatable.

I personally have an Activity blog that I try to stay updated with all the Events (RoadTest, Design Challenges and Webinars) that I participate in. I use it to go back and reference what I have learnt here on element14. Sort of like a notebook to guide me on my Maker journey? This sounds like a good idea to me. and could alleviate trying to keep my activity blog up to date!

I have my own offline scorecard ... just for my own interest.

For the rest, I rely on my calendar to keep me paced as best as possible.

The metrics would be interesting in aggregate, but hardly a necessity in my opinion.

- Gough