Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

ELI CoderDojo Final Report

583 Aufrufe

Veröffentlicht am

  • Als Erste(r) kommentieren

ELI CoderDojo Final Report

  1. 1. SAP Engaging For Local Impact - CoderDojo Foundation Kata Content Audit Report 12th June 2015 SAP Team Eoin Hurley Marian O’Connell John Keogh Michael Mulvey CoderDojo Team Laura Ivers
  2. 2. 1 Executive Summary The SAP ELI (Engaging for Local Impact) program is a unique, short-term and high- impact volunteering opportunity for SAP employees, who work together in cross- functional teams, to solve concrete business challenges for local non-profit organizations. The project scope defined by CoderDojo and the SAP team was to perform a content review and audit of their current MediaWiki based content system Kata. The team was also requested to advise on a more intuitive and user friendly structure to Kata. Kata is the backbone and presentation model that enables access to all the community acquired knowledge. It highlights member-projects, while providing the learning content in an open forum for the CoderDojo community to share resources, skills and experience with one another and work together to grow the knowledge of the members within the movement. While attending a Dojo, young people are given the opportunity to learn how to code, develop websites, apps, and more. Dojos are organized, run and taught by dedicated volunteers. The Dojo organizers invite guest speakers, organize events, and make learning to code a fun and sociable experience. In addition to learning to code, members meet like-minded people; show off their past projects, ongoing projects and innovative ideas. CoderDojo puts a strong emphasis on open source and free software, and has a strong network of members and volunteers globally. Our solution to resolve the navigation and interface issues for Kata is based on a simple yet innovative “3-Click” concept - from the homepage to find any type of information should take no more than 3 clicks. We also provided recommendations on improving the global reach of Kata, how to incorporate different languages and Dojo’s from all over the world plus how to balance community based vs. foundation created content.
  3. 3. 2 Contents 1. Introduction ............................................................................................................ 4 2. Project Method ....................................................................................................... 5 3. Understand............................................................................................................. 6 3.1 Needs Statement .............................................................................................. 6 3.2 CoderDojo Foundation Online Strategy ............................................................ 6 3.2.1 Main Website - CoderDojo.com ..................................................................... 7 3.2.2 Zen - zen.CoderDojo.com.............................................................................. 8 3.2.3 Future of CoderDojo.com............................................................................. 10 3.2.4 Future of Kata .............................................................................................. 10 3.3 Project Scope.................................................................................................. 12 3.3.1 In-Scope ................................................................................................... 12 3.3.2 Out of Scope............................................................................................. 12 3.4 Key Deliverables ............................................................................................. 12 4. Observe................................................................................................................ 13 4.1 Research Method............................................................................................ 13 4.2 Survey Results................................................................................................ 13 4.3 Interview Results............................................................................................. 16 4.4 Audit................................................................................................................ 17 4.4.1 Content Review............................................................................................ 17 4.4.2 Kata As-Is Data Flow Diagram..................................................................... 18 5. Point of View ........................................................................................................ 19 5.1 Kata To-Be...................................................................................................... 19 6. Ideate ................................................................................................................... 20 7. Prototype.............................................................................................................. 22 7.1 Recommendations .......................................................................................... 24 7.1.1 Technical/Structure................................................................................... 24 7.1.2 Sitemap..................................................................................................... 24 7.1.3 Organisers Section ................................................................................... 25 7.1.4 Community and Peer Review ................................................................... 26 7.1.5 Forum ....................................................................................................... 26 7.1.6 Promotion of Kata ..................................................................................... 26 7.1.7 Global Reach............................................................................................ 27
  4. 4. 3 8. Test ...................................................................................................................... 28 9. Predicted Impact for Kata and the CoderDojo Foundation ................................... 29 10. Conclusion ......................................................................................................... 30 11. Appendix A……………………………………………………………………………..31 12. Appendix B……………………………………………………………………………..32 13. Appendix C……………………………………………………………………………..53 14. Appendix D……………………………………………………………………………..56
  5. 5. 4 1. Introduction As part of SAP’s ongoing global CSR (Corporate Social Responsibility) initiatives, the ELI (Enable Local Impact) program was introduced in Ireland in 2015. For the four SAP employees participating in this project with CoderDojo, it provided a learning opportunity and a chance to grow personally while experiencing close customer engagement and the immediate impact of individual contribution. The opportunity to work within cross-functional teams provided a chance to build new networks in and beyond SAP, while also gaining valuable expertise on the concept of “run simple” and a deeper understanding of SAP CSR strategy. For SAP, it is an opportunity to improve brand reputation and extend its CSR footprint internally and externally while supporting social innovation at a local level. The initiative helps SAP employees to increase engagement, morale, understanding of customer needs and understanding of “run simple”. For the client it is an opportunity to address critical strategic challenges and access professional expertise and via cross collaboration will enable transfer of skills and expertise to their staff, which in turn will increase efficiency, efficacy and capacity. The SAP ELI puts driven SAP employees in facilitated opportunities to share skills and expertise to help solve a variety of challenges. This report outlines exactly how we achieved the objective using the Stanford D school design thinking method and how this audit together with the restructuring of Kata will support the CoderDojo foundation and the community as a whole.
  6. 6. 5 2. Project Method Design Thinking is an integral part of our work in SAP; therefore, when approaching CoderDojo project we decided to stick to the same project method. The D-School at Stanford1 consists of 6 stages which would help frame the problem, ask the right questions, create ideas and arrive at the best answers for CoderDojo. This process brought us through the following stages.  Understand  Observe  Point of View  Ideate  Prototype  Test 1 http://dschool.stanford.edu/redesigningtheater/the-design-thinking-process/
  7. 7. 6 3. Understand  Focus on understanding the issue, defining our audience and the metrics for success.  Defining the Mission Statement.  Increasing our knowledge of CoderDojo, Kata, Community Users, and the organisation acumen. 3.1 Needs Statement During the ELI Scopeathon on the 26th of April the needs statement for the project was defined and agreed up by CoderDojo and the SAP team. “Complete an entire audit of the current content available to the community via Kata. Provide recommendations for a more intuitive content structure. Identify redundant, irrelevant and non-value-adding content, as well as existing content gaps for each type of audience.” It was clear from an initial scan of the website that it was in need of an audit and restructuring but it was also necessary for the SAP team to gain an insight into how Kata would fit in the overall online CoderDojo Foundation Strategy. This insight would frame the project and allow SAP to make more suitable recommendations. 3.2 CoderDojo Foundation Online Strategy The CoderDojo Foundation is the administrative body of the CoderDojo movement. It is the central point of the 500+ clubs around the world. All the clubs are run autonomously but they sign a charter which ensures they are aligned with the CoderDojo ethos and philosophy. The level of interaction between the foundation and the clubs differs from club to club. Some clubs are very independent while others interact very often with the foundation especially during their initial set up phase. Each dojo is run by a community volunteer so the structure and operation of
  8. 8. 7 each CoderDojo may be different. The foundation offers best practices but there can be clashes in style and structure. Therefore Kata as the central content system needs to be flexible, directed by the community and stay relevant for a movement that is growing globally at a very fast pace. 3.2.1 Main Website - CoderDojo.com The main website was recently redesigned and restructured. It provides information about the movement and foundation, general news and how to get involved. It is the general landing page for the foundation and it is what the typical user/internet browser will be presented with first when searching for CoderDojo.
  9. 9. 8 3.2.2 Zen - zen.CoderDojo.com The foundation also provides information on each club and location on their Map based page which is the front end for the Zen system.
  10. 10. 9 This system allows each Dojo to update their exact location, information on the Dojo, timetables and general information for parents. It is also linked to Eventbrite which provides a ticketing system for each Dojo.
  11. 11. 10 3.2.3 Future of CoderDojo.com At present the foundation is reviewing their online presence and moving towards a platform/social media type structure where users and clubs can interact and share. This will be based around Zen and may allow CoderDojo members to receive badges and build up a coding CV or portfolio that can be used to further their career as they progress. The foundation is also working with Bridge 21 about ways to achieve and promote project based learning. 3.2.4 Future of Kata So how does the Kata system fit in to this structure and new plans? The foundation will keep Kata as the backend resource content site and use it to promote foundation created content. At the same time the Wiki nature of the site will allow the community to continue to upload new material and resources therefore continuing to direct the movement. Kata will be restructured and allow the foundation to achieve a more appropriate balance between community drive content and foundation created standard content.
  12. 12. 11 Clicking “Resources” on the main website brings you to Kata. The foundation will create Sushi cards in various programming languages and store them on Kata alongside community based content. For Kata they ideally want three different sections ninjas, learning resources and organisers. The new version of Kata needs to be more user-friendly and structured in a way that will achieve the balance between content types without becoming clustered and untidy again. The skin of the website will also be redone to reflect the primary colour scheme from the main website.
  13. 13. 12 3.3 Project Scope With the foundation’s online strategy and overview of current projects in mind, the scope of the Kata audit was defined. 3.3.1 In-Scope  Complete an audit of the current content available to the CoderDojo community via Kata.  Provide recommendations for a more intuitive content structure.  Identify redundant, irrelevant and non-value adding content as well as content gaps identified for each type of audience.  List potential solutions or approaches that will address the challenges and opportunities available to CoderDojo and Kata. 3.3.2 Out of Scope  Website functionality  Website design  Website coding and technical specifications 3.4 Key Deliverables  Research results  Survey analysis  Interview analysis  List of website content split up per new Kata sections (Ninjas, Learning Resources, Organizers, About)  New sitemap proposal  Recommendations list
  14. 14. 13 4. Observe  The most important step of the project.  Survey of Community users.  Interviews.  In-depth analysis of Kata in its current state (Kata As-Is) – duplication of information, redundant information, incorrect links on Kata, ill-structured material.  Pull all the links out of the site using a Python web spider.  Develop empathy and understanding to allow for effective and efficient project success.  Drew up a DFD map of the current site. 4.1 Research Method We chose survey and interview research methods so as to include as many global CoderDojo stakeholders as possible as well as being able to sit down and receive detailed feedback on Kata and how it should presented and used going forward. 4.2 Survey Results 16 CoderDojo Community Users took the time to complete our survey on Kata. The majority of our survey participants were Organisers of their local Dojo, with Parents, Mentors, and a Junior Mentor also providing vital feedback.
  15. 15. 14 Although majority of our participants were organisers, the results show that 60% did not use material from Kata when setting up their Dojo. The other 7% stated that Kata did not exist at the time they were setting up the Dojo, so they could not use it. Our survey revealed that participants were not currently using Kata on a regular basis with 62% visiting it only once a month and 13% never visiting Kata. When users do visit Kata, Learning Resources and Organiser are the most popular and useful by participants. From the participants that voted No section useful, we found that it was mostly due to outdated information on Kata and it is not user-friendly. 7 4 3 1 1 0 Champion (Lead Organiser) Champion & Mentor & Parent Champion & Mentor Mentor & Parent Junior Mentor Youth Attendee Participants Role 33% 60% 7% Was Kata used when setting up your Dojo? Yes No Other
  16. 16. 15 We found that the majority of our participants do not regularly upload material to Kata. While those that are uploading are doing so regularly, they are using .pdf documents, GitHub or other external amenities other than Kata. 2 of our participants included that they would like to upload material, but do not know how. Another question regarding the “CoderDojo for Girls” section on Kata revealed that 62% think there should not be a section just for girls. The consensus was that all Learning material is together and girls can choose what they want to learn. An individual section is not necessary and not required when encouraging girls to take part. While the 38% think that there is a place for girl specific content. 53% of participants would like to see Kata supporting their Dojo by providing a place to upload and share materials, while 20% need it to be more of a training portal and to help parents teach their children. 56% 19% 0% 25% Most useful section of Kata? Learning Resources Learning & Organisers Resources Community Resources None 38% 62% Should there be an expanded 'CoderDojo for Girls' section? Yes No
  17. 17. 16 The content users would like to see on Kata is a mix of Sample Projects, Game Development projects and Sushi Card hand-outs. See “Appendix A” for the raw survey data. 4.3 Interview Results We carried out interviews with CoderDojo Foundation staff, organisers and mentors. The interviews were not formal and the feedback was collected more as a result of a “free form” discussion on Kata and CoderDojo. The feedback was divided up into 7 sections:  Kata Structure  Kata Target Audience  Types of Content  Content Sharing  Peer Review  Forum/Community  Dojo Organization This information along with the survey informed both our audit and Kata structure proposal. The feedback was largely based on the structure of the site and what content should be made available to the community. See “Appendix B” for the raw interview data and transcripts. 53% 20% 13% 7% 7% How would you like Kata to support your Dojo Portal to upload and share materials As a training portal Portal to upload and share materials AND a training portal To help Parents Other
  18. 18. 17 4.4 Audit The actual audit of the current Kata took place concurrently with the survey and interviews. Using a Python based web spider we pulled out all the raw links from Kata and with these links we manually reviewed each page. We checked how exactly each page would be accessed and where the links from it lead to. We also paid special attention to the layout of each page. The result of our audit was in line with the survey and interview feedback. The site was cluttered and overtime had become badly structured and confusing. 4.4.1 Content Review We recorded all of our audit work in the Excel along with the To-Be sitemap. To see the detail of the audit please go to Appendix D and open the Excel file. Each tab represents a section of the site. The links have been categorised based on our Kata To-Be proposal which will be discussed further on in this report. Most links should have a comment beside them and a recommendation. If none exists then the page is deemed to be of sufficient standard for the new Kata.
  19. 19. 18 4.4.2 Kata As-Is Data Flow Diagram While we pulled all the links out for the audit will also built a Data Flow Diagram of the website as it is. See “Appendix C” for the full Data Flow Diagram of the current structure and flow of Kata. With this diagram it was easy to see why we had received such feedback in the survey and interview sessions. The website had many confusing redirect loops and in some places users would have to click 5, 6 or 7 times deep into the site to get the information they wanted (see example above).
  20. 20. 19 5. Point of View  Having gathered enough information from previous stage, we now have a real awareness of the problem and how it influences the users of Kata and CoderDojo Community Users  Time for us to discuss how Kata should look (Kata To-Be)  Time spent onsite allows us to build awareness of the restrictions/limitations within CoderDojo. Some ideas may not be feasible or possible for the organisation. 5.1 Kata To-Be A Meeting on Monday 12th May helped us to put the content review in context and provide a glimpse of the potential new Kata structure. It was clear that once the site was cleaned up we needed to avoid duplication of data/pages. This can be achieved by providing a certain amount of overlap between each section. For example the same learning resources could be accessed directly from both the “Ninjas” and “Learning Resources” section. The structure discussed that day can be seen below. Due to the restrictive timeline of the project this “Point of View” phase overlapped with the “Observe” phase. We were still observing, researching and auditing while keeping mind how we could use off this information to design the new version of Kata.
  21. 21. 20 6. Ideate  Time to brainstorm  This stage allows for creativity, suggestions, pushing boundaries, etc.  We start on stage 1 restructuring the website now the audit of each link is complete & redundant and irrelevant info has been identified  Discussion and Post-its  Suspension of judgement  The structure of the site and how it is sub-categorized is changed many times following further review & meetings with CoderDojo IT expert. On Thursday 14th of May we sat down to decide on the audit results and agree on the categories for the links from the website review. At this point we decided to ideate and begin designing the new sitemap. The results of this design thinking session can be seen below. We decided on a 3 clicks deep concept for the new Kata. This means that to find something you are looking for it should not take more than 3 clicks from the
  22. 22. 21 homepage to find that information. At the moment the user is presented with endless redirect loops and rabbit holes leading to confusion and frustration. The new Kata will funnel all data into clear sections and will allow the user to navigate the website with more ease avoiding links that they may find useless and obstructing. For example if I am a mentor and I want see information on Intermediate Python - Homepage -> (click1) Learning Resources -> (click2) Python -> (click3) Intermediate.
  23. 23. 22 7. Prototype  Time to fuse and refine from previous stage  We have now all agreed on the sub-sections of Kata  Time to decide how it should look and be presented  More post-its and we all sit down and decide on the structure of the website after heavy discussion & more meetings with CoderDojo IT expert.  Some votes take place when we can’t decide/agree  Always referring back to mission statement and interview/survey findings when need guidance also During the time away from CoderDojo back at SAP we continue to refine the above design thinking site map proposal and copied it into an excel complete with the audited website links from the pulled out by the web spider. See Appendix C “Kata To-Be Sitemap” for detailed view of the proposed new structure (embedded excel file). A helicopter view of the new sitemap can be seen below. Ninjas on the far left, Learning Resources in the middle and organisers on the right. Learning Resources and organisers should be split up by spoken language while the
  24. 24. 23 technical resources should be split up per programming language then by Sushi and experience level (beginner, intermediate, advanced). Ninjas & Learning Resources About & Organisers
  25. 25. 24 7.1 Recommendations During the onsite week and our meetings back at SAP we came up with a concise recommendations list that can be split up into 7 different sections. 7.1.1 Technical/Structure  Please see Appendix D “Kata To-Be Sitemap” excel to see what should be deleted  Better indexed site/Index map page - alphabetical  Funnel links from areas into core parts and let them overlap between each section.  Homepage to have 4 sections – Ninjas, Learning Resources, Organisers & About  Top 3 links placed under the picture of each section  Top 3 links based on review of Google Analytics (most clicks)  Reuse the bulk of content from the old Kata – while omitting any duplication.  All boxes in the Excel are to be rolled up into one page. User can choose what they want from this landing page.  Change the left hand tree functionality of Kata to be scrollable…easier for users to deepdive into Kata without many clicks 7.1.2 Sitemap  See Appendix D “Kata To-Be Sitemap” for detailed view of the proposed new structure (embedded excel file).  Keep link drill down to a maximum of three clicks. Avoid overuse of links so as not to create link loops.  Structure content by spoken languages first. (2nd Click)  Then within each spoken language section have sub-structure by coding languages. (3rd Click)  Within each code, language section structure by ability and include Sushi cards to assist project based learning. (Beginner - Intermediate – Advanced). (4th Click)  Within each ability section structure content by lessons or weeks etc.
  26. 26. 25  Where necessary within sections utilize handbooks of best practices (keeps content tidy e.g. setting up a Dojo for organisers).  Sitemap DFD needs to be updated and kept as live document. Changes added and recorded.  The new structure won’t provide a curriculum per se or advice against project based learning. It will be more like a “walled garden” - an area to play but the structure is subtly provided and the users are given more an advised lesson plan and access to different levels of material.  Sushi will be placed in alongside the community driven material and divided up per programming language.  Language Resources are included in the main page and split up by programming language. No big distinction between each dojo will be made.  The Kata structure suits two audiences - those in favour of games as the primary source of learning and those in favour of programming languages as the primary source.  If 1 area becomes overloaded with new material this will not effect and interrupt the flow of the rest of the site. It will be more like a “localised infection”. 7.1.3 Organisers Section  Create a manual of a quick checklist of how to create a Dojo  Create a manual of how a beginner kata editor can create content…guidelines, templates, specifications to be met  Create an array of sample letters/templates for new dojos to send to sponsors/approach venues  Create a Calendar for Organisers to refer to for "Calendar of upcoming events"  "Under the section 'About Kata' > How to Become a Kata Editor' have clear instructions/manual on how users can edit kata correctly and instructions on “how to upload to kata"
  27. 27. 26 7.1.4 Community and Peer Review  Formatting standards should be rolled out for uploads (Sushi – how to docs etc.)  Create a central content section that is only editable via the foundation members  Users can submit content in the form of projects, sushi cards for a peer review  Peer review of the content would come from 1 community member and 1 foundation member  Create a Kata manual which would be handbook of best practices 7.1.5 Forum  Add a forum or continue with google groups but add technical curation from the foundation and interaction  If users can get advice they will tend to get more involved and this will keep people using the site  If Dojos build trust on the forum this may stop any rivalry and make the competition healthier  If Dojos feel more connected they will be more likely to share 7.1.6 Promotion of Kata  There is currently a low site count on Kata  Kata needs a relaunch and should be promoted on social media and in community newsletters  Integrate Google Analytics for view on when and where site is being used. This will inform any changes that maybe required and if more promotion is required
  28. 28. 27 7.1.7 Global Reach  Create language sections in the Learning Resources and Organisers Resources parts of the website, ensuring that Kata is relevant for the foundation globally.  As a filter after learning resources - improve global reach of Kata by not hiding different languages in another part of the site  Material from different Dojos is also available in the same area as the foundation created content.
  29. 29. 28 8. Test  Next step for CoderDojo is to implement our recommended new structure, audit findings  Once new Kata is up and running we will wait for feedback from Community Users  After the new Kata is launched create a new survey and Compare results with the previous survey  Repeat the above steps at regular intervals in a PLAN – DO – CHECK – ACT cycle. In the final week of the project we handed all this work over to the foundation. The foundation itself will build the new version of Kata based on this audit and new sitemap proposal. We advise that a new version be built from scratch and the content from the old Kata copied over and restructured. We would advise once the relaunch is complete and a period of time has passed (e.g. 3 months) to rerun the survey and collect feedback from the previous participants to gauge improvement and also seek further improvement.
  30. 30. 29 9. Predicted Impact for Kata and the CoderDojo Foundation  Kata will be more user friendly and will be less cluttered  Kata will be structure more efficiently and is tidier overall  Combined with the forum and upcoming platform the above will encourage users to add their own content  There will be a place for CoderDojo own content  There will be a balance between community content and CoderDojo own content  It will be easier to keep track of the site - avoid situation occurring again  Easier to analyse the site and track its usage  Make it relevant for ninjas, organisers and mentors  This will all improve the global reach of Kata which in turn will support the global growth of CoderDojo
  31. 31. 30 10. Conclusion This project was a chance for us as SAP employees to bring our skills to the local environment and have an impact with a non-profit organisation. We feel that by researching the CoderDojo community and mapping this feedback to a new restructured sitemap we have assisted CoderDojo to relaunch a more intuitive and user friendly Kata system which will promote and support their evolving online strategy and global growth. It was our decision to go with a non-hierarchical structure and collaborate on an equal footing. Throughout the course of this project each individual naturally took a lead at different points when their particular strength or skillset was needed. In doing this we have learned the value of listening and considering each other’s view point even when it was not very clear what the outcome would be. While we were always aligned on the ultimate goal differing mind-sets and approaches at times lead us down parallel paths that in the end combined to a successful final result.
  32. 32. i 11. Appendix A Survey Results Survey Chart Results.pptx Double click and open….
  33. 33. 12. Appendix B Interviews Interviews with CoderDojo foundation employees and CoderDojo mentors & champions INTERVIEW CODING LEGEND .......................................................................................................................... ii INTERVIEW 1...................................................................................................................................................... iii INTERVIEW 2....................................................................................................................................................... v INTERVIEW 3..................................................................................................................................................... vii INTERVIEW 4...................................................................................................................................................... ix INTERVIEW 6.................................................................................................................................................... xiii INTERVIEW 7.....................................................................................................................................................xiv COLLATED FINDINGS .......................................................................................................................................xv a. Kata Structure .........................................................................................................................................xv b. Kata Target Audience............................................................................................................................xvi c. Types of Content ..................................................................................................................................xvii d. Content Sharing ...................................................................................................................................xviii e. Peer Review...........................................................................................................................................xix f. Forum/Community ..................................................................................................................................xx g. Dojo Organization ..................................................................................................................................xxi
  34. 34. ii INTERVIEW CODING LEGEND a Kata Structure b Kata Target Audience c Types of Content d Content Sharing e Peer Review f Forum/Community g Dojo Organization
  35. 35. iii INTERVIEW 1 Name : Christophe Stürzel Role within Coderdojo: Deansrath Champion & Mentor Date: 08/05/2015 11:00 - 12:00 Notes from interview HOW DID YOU START YOUR DOJO  2.5 years ago SAP colleagues worked with the Deansrath Family centre to open a CoderDojo  Received a subsidy as part of a Grant Cycle BEING A MENTOR  Learn by doing  Most of the kids use Scratch, HTML and Java  Deansrath maybe not a normal Dojo - kids move from topics here and there  Normally parent is with the child  Kids need a good base - basic tutorials  Code.org - hour of code is limited  Experience of other CoderDojos being reluctant to hand over their data/projects  Competition between Dojos - proud of their own work, reluctant to share  The hope is shared project learning  That is the ideal - not completion or prizes but that the kids learn how to code  Deansrath sessions are shorter than other ones/parents are not there KATA AS A TRAINING PORTAL  Could be for teachers and kids  Basic stuff + what’s the next level + nice clips/videos etc.  Really need good next level material beyond Scratch, especially for the older kids  Example projects would be very welcome; somewhere the kids can go and upload their projects/see what other kids are doing  Doesn’t need to be regulated/checked - no rating system here!  Other training material may need to be proofed  Keep in mind Kids have short attention spans - precise projects would be great  Example projects and maybe a list of what skills sets are needed  The training material could be peer reviewed by the community to reach certain standards  Basic Stuff can be uploaded  Approved material should be checked  Resources for training ninjas into mentors - section on how to move advanced kids into becoming mentors themselves  Found that section quite tough
  36. 36. iv  There is a sense of IP from each CoderDojo RESISTANCE FOR SHARING IN THE COMMUNITY  Share what they do with the documentation  Share their progress online - twitter not enough - paints a really happy positive picture  Nowhere to share concerns/worries and get answers  Scratch has online share/website share  Family Centre website gives information about the Dojo  Space to upload/manage your own projects?  Use it as a project repository - maybe have a work space on Kata for each Dojo  Badges - gamification  Community driven forum - get people to use KATA if they knew they could get help on it - very into it  FAQ/Surveys for different levels  Badges for different levels  Links for EU code week  Tuesday expect so much more - attention span is short - need to make it look really attractive  Thursday - older - more patience CODERDOJO FOR GIRLS?  Maybe for the younger girls - lower age group need to be encouraged to get into it  Tutorials would be great - Self learning  Can be frustrating for organizers  Room for improvement certainly - sharing would be great Christophe then took a look at the site and emailed some feedback  I have had a look at KATA. As mentioned I had never used this area but I found it quite useful although it is not really very structured and limited in content so far. It also shows that some CoderDojos share their experience although it is on a small scale so far considering the number of CoderDojos. So there is fantastic potential of input in this space.  One other thought I had not mentioned last Friday, you might know that some schools in Ireland start using Scratch to teach some Maths / Geometry … An idea could be to have a school area in KATA in which they highlight their work. Knowing that it would be ‘supervised’ by teachers the quality should be sort of ‘academic’ and the pride from one school to another (all around the globe of course) should be a good incentive for quality tutorials.  Not to mention that there is a big potential to open new CoderDojos in schools as they have PCs available. Especially in underprivileged areas Coderdojos in schools are a big plus as the kids don’t need to provide a laptop
  37. 37. v INTERVIEW 2 Name : Ademola Olajide Ajayi Role within Coderdojo: Deansrath Champion & Mentor Date: 08/05/2015 15:15 - 15:45 Notes from interview ABOUT KATA  Never heard of Kata  Had not used Kata as a resource when setting up the Deansrath Coderdojo.  Found it very hard to find information of what was required when setting up a Dojo.  There is no checklist of requirements, best practices, rules & regulations, how to approach sponsors, local community centers, etc, there is nothing from the Coderdojo foundation on this.  On first glance of Kata, there needs to be a kids/mentors/admin section. For the children, it needs to be structured. Start off lessons/tutorials for the children to begin with. ABOUT CODERDOJO  Currently the Coderdojo Foundation and the Coderdojo Movement have no relationship. There needs to be a relationship between these two.  There is no relationship between Dojo’s either. They are not working together to help each other.  Do they still do Coderdojo conferences? If not, they should WHAT WOULD BE NICE TO HAVE AS CHAMPIONS  A checklist or detailed instructions of how to set up a Dojo from scratch. Readable for people who know nothing about coding/Dojo/etc  Welcome pack which includes info on Kata & ways to encourage Dojo’s online visibility.  In welcome pack it could outline that if dojo has a lot of online visibility…then they will be visited by Coderdojo…encouraging online visibility.  Template documents to send to local sponsors, community centers, etc. For someone starting up from scratch, it can be daunting writing such a document. To have an initial template to work off of would be beneficial & look better. A ‘How to Approach’ or ‘templates’ section  Private section for champions to talk/raise questions/discuss best practices/ Q&A section. Possibly have a Coderdojo contact participating too. WEBSITES USED TO COMPARE  EV3lessons.com -> lessons section  Firstlegoleague.org  Lero -> best in Ireland for scratch resources
  38. 38. vi  Scratch.mit.edu CODERDOJO FOR GIRLS  Do not see this as a necessity.  Maybe it does not need to be sectioned off, include the tutorials with all other resources.  Ade also spoke about a tool he has seen some children using for school homework.  With this tool, the child is given scratch homework, such as a project to complete. The child does this for his/her homework and uploads it to an online account that only the teacher/child/parent can access (you need an account, not available to public).  Perhaps it could be incorporated to Kata  Ade will check the name of this tool & let us know for reference.
  39. 39. vii INTERVIEW 3 Name : Ursula Clarke Everett Role within Coderdojo: CoderDojo Foundation Technical Lead Date: 12/05/2015 11:00 - 12:00 Notes from interview ROLE AT CODERDOJO  In terms of Kata looking after new design for MediaWiki  The code base is not very tidy  25% of work on Kata  IBM team has been doing the new skin. Current content needs to be moved to the new skin  To get the skin working MediaWiki has to be upgraded to 1.24 which is 5 version higher  DB has to be upgraded as well which is not easy  Also working on Zen and the new social media type platform and ticketing system LEARNING RESOURCES  Mentors and kids don’t need really need to be in different categories. Beginner/Intermediate/Advanced is more important  Prerequisites for each level of programming language is needed as well  Technically hard to manage new content  Sometimes kids and mentors are at the same level or the mentor is only 1 step ahead  Material needs to be fun and technically correct  Content should be approved  CoderDojo should make their own content KATA STRUCTURE  Free flowing  Place for community comments  Keep links low - create a nice intuitive flow FORUM/COMMUNITY  They use Google Groups - the new platform will also integrate this  They also run community calls but these have stopped recently  Where do you go when you need help?
  40. 40. viii KATA IN AN IDEAL WORLD  List of programming languages  Straight into the actual resources - no messing around  Mentors & Kids is just tech - simple design - max 15 languages  Legal/main stuff moved out to the main site SUSHI IN ITS OWN SECTION  Featured Sushi on dojo page  Good quality Sushi that won’t change - influenced by community page MENTOR TRAINING  Technical forum to answer questions - google group already in place but maybe technical curation from the foundation should be implemented  Technical interaction  Kids DIY - sample project, place to upload their new stuff HTML 5  Is possible on MediaWiki REPORT  Give them options in the final report REGIONS  Not relevant in Kata structure really, don’t want to make the distinctions.  Kata is a global resource  Learning resources could be divided/filtered by language
  41. 41. ix INTERVIEW 4 Name : Giustina Mizzoni Role within Coderdojo: CoderDojo Foundation Development Lead Date: 13/05/2015 12:00 - 13:00 Notes from interview OPINION OF KATA  Kata is scary at the moment, so much in there and all over the place  Very messy, difficult to find structure  Content is not verified  Content could be just based on personal preferences rather than what the community needs CONTENT  Suggested content is needed - finished stuff for HTML and CSS  Easy to find basic material but the next step is difficult - foundation needs to suggest a path  Not a curriculum but some direction  Content could be verified by Kata editors, foundation staff  If you are editing Kata you are almost self-selecting yourself as someone who will publish quality material  Concerned about having a repeat of how Kata looks now  Checklist for when you are uploading material - does this meet the format? KATA IN AN IDEAL WORLD  One stop shop for material  Website contains organizational resources  Kata is more detailed and practical  Technical content is main focus  Course content not for kids specifically  Languages very important  Training mentors  Dojo Sushi big focus of Kata KIDS  Games wouldn’t be used by mentors in a Dojo. Kids might be well past these games CATEGORIZATION  Structure needs to be strong, need to be able to filter out what you don’t want  Less clicks to get where you need to go
  42. 42. x PEER REVIEW  Great idea, could mean its reviewed by staff and also a community member before it can go on the site  People would like to share it and their work published RIVALRY  Has not seen it with normal dojos but perhaps it exists with corporate run dojos. Microsoft, Salesforce and Mastercard all run dojos in the same business park in Dublin.  Healthy competition as part of coolest projects  IP is all done under creative commons  Would a forum get them talking and encourage trust and community ethic  Bigger dojos helping the smaller ones? MEDIAWIKI  Yes, it is wanted by the foundation to encourage community uploading and help  Review process has the potential to lead to a backlog of content waiting to be uploaded REGIONS  Filter for languages  Having a regional page or section is not relevant WHO OWNS KATA?  The community  But from the foundations perspective they need some more input  Concerned about backlash  Need to do what’s best for the community - standard content then peer review the rest
  43. 43. xi INTERVIEW 5 Name : Peter Wolf Role within Coderdojo: Richmond, Surrey, UK CoderDojo Champion & Mentor Date: 13/05/2015 14:00 - 14:30 Notes from interview RELATIONSHIP WITH CODERDOJO  Champion - set up and founded a community CoderDojo in Richmond, South West Surrey, UK  Used Kata a bit when he was setting up the dojo but depended on 1:1 on help with Eugene more  Did check with Kata when setting it up  Mentors know of it but they don’t use it a lot  He used it to find Scratch card, used it to gather info from dojos in ROI  HTML section used a lot, my first website used  He dips in and out of it OPINION OF KATA  Very clunky - wiki structure is fine if you have the experience  Hard to navigate, cumbersome SUBMISSIONS  Survey of participants - 40 regular kids  Wanted to know - feedback - get sense of changes with their structure  Survey forms would be of interest for other dojos PEER REVIEW  Neutral opinion of it, easier - send it to an editor and it is publisher - could be costly and time consuming  User friendly tools for submitting would be nice  Doesn’t feel strong about it  Pain of dealing with Kata is more important  If the foundation has the resources to curate it then it would be lead to more consistency and structure UNEDITABLE CONTENT  Reasonable to lock policy content  Project materials - no
  44. 44. xii FORMAT  Most materials are in PDF format - should be allowed to be changed - word or PowerPoint would be easier  At the moment he has to find the person that created the material and then ask them to send on the original  All adds time/hurdles for our volunteers KATA AUDIENCE  Mentors/organizers yes  Kids should have a separate page for their own resources
  45. 45. xiii INTERVIEW 6 Name : Noel King Role within Coderdojo: DCU Champion & Mentor Date: 14/05/2015 @ 14:00 - 14:30 Notes from interview ROLE IN CODERDOJO  Set up DCU CoderDojo in August 2012 - champion RELATIONSHIP WITH KATA  DCU was set up before kata therefore never used Kata at the start and doesn’t use it now.  DCU build a lot of their own stuff, they pick content that the young people want. Young people want to work towards a goal defined in a project  Doesn’t upload to Kata, they use their own GitHub. Never liked it - too disjointed  Would have no problem uploading the DCU material to it but would prefer something like code.org CONTENT  Sushi will be very successful  Creating MOOC for CoderDojo with help from Intel and Sligo IT  Prefers video based content  Kata needs more advanced content  Challenge is to create some sort of standardization in the movement  Quality of content needs to be verified  Curriculum is a “dirty” word in the movement but the focus needs to be on the core objectives - what will be learned in this - variables, loops, logic RURAL DOJOS/MENTORS  The hope is that for isolated Dojos and dojos that don’t have very technical mentors that Kata could fill the gap  Platform would lead the mentors. Mentors don’t have to be software engineers  Project/game driven learning has been very successful  Set number of projects - beginner/intermediate/advanced FORUMS  Haven’t worked yet  CoderDojo has been a massive organization to run  Possibly overwhelmed  1% reply rate typical on current forums
  46. 46. xiv INTERVIEW 7 Name : Prarie Nyx Role within Coderdojo: Des Moines, Iowa Champion & Mentor Date: 14/05/2015 16:00 - 16:30 Notes from interview OPINION OF KATA  Shared pile of resources put up in a haphazard manner  Ideal version of Kata would be a path through the same project but in done in different languages  Set curriculum of projects that let you do the same tasks in different languages so you can learn in parallel  HTML5 section was quite good - a lot of useful links  Path through the information is quite confusing STRUCTURE OF KATA  Emphasis should be placed of what kinds of tasks you can do with each language  Define common tasks that you can do with each - classic examples of what can be achieved with each  Then you can move from basic on towards intermediate and advanced  Wiki needs to be moderated  Would be nice to have a workspace for each language  Material needs to remain user editable CODERDOJO REACH  Great place to upload your material and leverage the CoderDojo global reach and position
  47. 47. xv COLLATED FINDINGS a. Kata Structure  It is quite useful although it is not really very structured  On first glance of Kata, there needs to be a kids/mentors/admin section. For the children, it needs to be structured. Start off lessons/tutorials for the children to begin with.  Mentors and kids don’t need really need to be in different categories. Beginner/Intermediate/Advanced is more important  Prerequisites for each level of programming language is needed as well  Free flowing  Place for community comments  Keep links low - create a nice intuitive flow  List of programming languages  Straight into the actual resources - no messing around  Mentors & Kids is just tech - simple design - max 15 languages  Legal/main stuff moved out to the main site  Featured Sushi on dojo page  Good quality Sushi that won’t change - influenced by community page  Regions are not relevant in Kata structure really; doesn’t want to make the distinctions.  Kata is a global resource  Learning resources could be divided/filtered by language  Kata is scary at the moment, so much in there and all over the place  Very messy, difficult to find structure  One stop shop for material  Structure needs to be strong, need to be able to filter out what you don’t want  Less clicks to get where you need to go  Filter for languages  Having a regional page or section is not relevant  Very clunky - wiki structure is fine if you have the experience  Hard to navigate, cumbersome  Doesn’t upload to Kata, they use their own GitHub. Never liked it - too disjointed  Would have no problem uploading the DCU material to it but Would prefer something like code.org  Set number of projects - beginner/intermediate/advanced  Shared pile of resources put up in a haphazard manner  Ideal version of Kata would be a path through the same project but in done in different languages  Set curriculum of projects that let you do the same tasks in different languages so you can learn in parallel  Path through the information is quite confusing  Emphasis should be placed of what kinds of tasks you can do with each language  Define common tasks that you can do with each - classic examples of what can be achieved with each  Then you can move from basic on towards intermediate and advanced  Wiki needs to be moderated  Would be nice to have a workspace for each language
  48. 48. xvi b. Kata Target Audience  Could be for teachers and kids  Keep in mind Kids have short attention spans - precise projects would be great  Maybe for the younger girls - lower age group need to be encouraged to get into it  Course content not for kids specifically  Training mentors  Mentors know of it but they don’t use it a lot  Mentors/organizers yes  Kids should have a separate page for their own resources  The hope is that for isolated Dojos and dojos that don’t have very technical mentors that Kata could fill the gap  Platform would lead the mentors. Mentors don’t have to be software engineers
  49. 49. xvii c. Types of Content  Most of the kids use Scratch, HTML and Java  Kids need a good base - basic tutorials  Code.org - hour of code is limited  Basic stuff + what’s the next level + nice clips/videos etc.  Really need good next level material beyond Scratch, especially for the older kids  Example projects would be very welcome; somewhere the kids can go and upload their projects/see what other kids are doing  Example projects and maybe a list of what skills sets are needed  Resources for training ninjas into mentors - section on how to move advanced kids into becoming mentors themselves  Use it as a project repository - maybe have a work space on Kata for each Dojo  Tutorials would be great - Self learning  One other thought I had not mentioned last Friday, you might know that some schools in Ireland start using Scratch to teach some Maths / Geometry … An idea could be to have a school area in KATA in which they highlight their work. Knowing that it would be ‘supervised’ by teachers the quality should be sort of ‘academic’ and the pride from one school to another (all around the globe of course) should be a good incentive for quality tutorials.  With this tool, the child is given scratch homework, such as a project to complete. The child does this for his/her homework and uploads it to an online account that only the teacher/child/parent can access (you need an account, not available to public).  Material needs to be fun and technically correct  Content should be approved  CoderDojo should make their own content  Suggested content is needed - finished stuff for HTML and CSS  Easy to find basic material but the next step is difficult - foundation needs to suggest a path  Not a curriculum but some direction  He used it to find Scratch card, used it to gather info from dojos in ROI  HTML section used a lot, my first website used  Most materials are in PDF format - should be allowed to be changed - word or PowerPoint would be easier  Sushi will be very successful  Prefers video based content  Kata needs more advanced content  Curriculum is a “dirty” word in the movement but the focus needs to be on the core objectives - what will be learned in this - variables, loops, logic
  50. 50. xviii d. Content Sharing  Experience of other CoderDojos being reluctant to hand over their data/projects  Competition between Dojos - proud of their own work, reluctant to share  The hope is shared project learning  That is the ideal - not completion or prizes but that the kids learn how to code  Share what they do with the documentation  There is a sense of IP from each CoderDojo  Share their progress online - twitter not enough - paints a really happy positive picture  There is no relationship between Dojo’s either. They are not working together to help each other.  Has not seen it with normal dojos but perhaps it exists with corporate run dojos. Microsoft, Salesforce and Mastercard all run dojos in the same business park in Dublin.  Healthy competition as part of coolest projects  IP is all done under creative commons  Would a forum get them talking and encourage trust and community ethic  Bigger dojos helping the smaller ones  DCU build a lot of their own stuff, they pick content that the young people want. Young people want to work towards a goal defined in a project  Doesn’t upload to Kata, they use their own GitHub. Never liked it - too disjointed  Would have no problem uploading the DCU material to it but would prefer something like code.org  Great place to upload your material and leverage the CoderDojo global reach and position
  51. 51. xix e. Peer Review  Doesn’t need to be regulated/checked - no rating system here!  Other training material may need to be proofed  The training material could be peer reviewed by the community to reach certain standards  Basic Stuff can be uploaded  Approved material should be checked  Content is not verified  Content could be just based on personal preferences rather than what the community needs  Content could be verified by Kata editors, foundation staff  If you are editing Kata you are almost self-selecting yourself as someone who will publish quality material  Concerned about having a repeat of how Kata looks now  Checklist for when you are uploading material - does this meet the format?  Great idea, could mean it’s reviewed by staff and also a community member before it can go on the site  People would like to share it and their work published  Need to do what’s best for the community - standard content then peer review the rest  Neutral opinion of it, easier - send it to an editor and it is publisher - could be costly and time consuming  User friendly tools for submitting would be nice  Doesn’t feel strong about it  Pain of dealing with Kata is more important  If the foundation has the resources to curate it then it would be lead to more consistency and structure  Quality of content needs to be verified
  52. 52. xx f. Forum/Community  Nowhere to share concerns/worries and get answers  Community driven forum - get people to use KATA if they knew they could get help on it - very into it  FAQ/Surveys for different levels  MEDIAWIKI  Yes, it is wanted by the foundation to encourage community uploading and help  Review process has the potential to lead to a backlog of content waiting to be uploaded  At the moment he has to find the person that created the material and then ask them to send on the original  Haven’t worked yet  CoderDojo has been a massive organization to run  Possibly overwhelmed  1% reply rate typical on current forums
  53. 53. xxi g. Dojo Organization  Found it very hard to find information of what was required when setting up a Dojo.  There is no checklist of requirements, best practices, rules & regulations, how to approach sponsors, local community centers, etc., there is nothing from the Coderdojo foundation on this.  A checklist or detailed instructions of how to set up a Dojo from scratch. Readable for people who know nothing about coding/Dojo/etc.  Welcome pack which includes info on Kata & ways to encourage Dojo’s online visibility.  In welcome pack it could outline that if dojo has a lot of online visibility…then they will be visited by Coderdojo…encouraging online visibility.  Template documents to send to local sponsors, community centers, etc. For someone starting up from scratch, it can be daunting writing such a document. To have an initial template to work off of would be beneficial & look better. A ‘How to Approach’ or ‘templates’ section  Private section for champions to talk/raise questions/discuss best practices/ Q&A section. Possibly have a Coderdojo contact participating too.
  54. 54. i 13. Appendix C Kata As-Is Data Flow Diagram  Wiki Main.sdr  About.sdr  Overview of Learning Resources.sdr  Organising a Dojo.sdr  CoderDojo Community.sdr  Become a Kata Editor  Sushi **Double click and open…. SDR files are SmartDraw drawing files To view files you may need to download Smart Draw http://www.openthefile.net/extension/sdr**
  55. 55. ii  CoderDojo Champion  Mentors and Volunteers.sdr  Venue.sdr  Dojo Operations.sdr  Belts.sdr  Advice from CoderDojo Champions.sdr  Guiding Principles and Philosophies.sdr  Sponsored Tools.sdr
  56. 56. iii  Community Support  Organisers Google Group.sdr  Dojo Groups.sdr  Community Calls.sdr  CoderDojo Community Committee.sdr  Coolest Projects.sdr  DojoCon.sdr Double click and open…. SDR files are SmartDraw drawing files To view files you may need to download Smart Draw http://www.openthefile.net/extension/sdr
  57. 57. i 14. Appendix D Kata Recommended Full Sitemap  Homepage  To-Be Sitemap  Ninja - Audited Links  Mentors - Audited Links  Organisers - Audited Links  About - Audited Links KATA Recommended Full Sitemap Final.xlsx Double click and open….

×