Checkio Case

Executive Summary

First and foremost, Checkio started out as a small company with a simple goal to be the best website for programmers. Alex Lyabah, the company’s Chief Technological Officer, founded CheckiO originally in the Ukraine. The Checkio site was first seen as a hobby and a way for Alex to challenge himself and his friends with interesting programming and tasks using the programming language, Python. CheckiO began to see great success and began to sign up many users many of whom were active during a given month. In 2012 Lisa Avramenko was hired in the place of project manager for Checkio. By the time Avramenko was hired, Checkio had already acquired over 1500 registered users.

In short, Checkio has come across problems such as employment, language support, community building, and relationships with academia. Regarding language support, the Python language used by the company may be unfamiliar to potential users. The fact that this language is not widely used on the internet can cause complications for the company. The problem Checkio is having with community building is centered on their open source community format. The company wants to allow users to post their own challenging tasks to the site, but this is not an easy task. In order for users to accomplish this, they would have to not only be knowledgeable with the Python code language, but possess the skillset to design a task that has clear instructions, fits in with the theme of the website and free of bugs. Lastly, Checkio is faced with the decision to collaborate and form a relationship with academia. This would require revamping the whole entire site to be designed for a classroom and being able to introduce this to students.

To summarize, we would implement possible solutions by developing a required enrollement process for students, set up additional beginner islands and create a customized island specific to institutions/faculty that commit to enroll atleast ten classes, 200...