Skip to content
samuelmr edited this page Mar 14, 2013 · 2 revisions

Concept planning

  • Concept summary
  • Make user profiles document
  • Make use case description
  • Architecture draft
  • Tech spec

Add your ideas below. Please, do not overwrite.

  • Evaluation of related services
  • Review good ideas from existing planner and navigation apps
  • Review important shortcomings hindering earlier projects
  • Brainstorm ideas, features, existing code, new forms of data
  • Evaluate and select ideas based on utility/cost and risk
  • Check out both ideas and crowd sourcing methodology at Designing Chicago Urban Agent HQ
  • ...

Share information

  • OK Fest
  • Apps4Finland forums
  • Developer meeting (October?)
  • Open Knowledge Foundation working group on Open Transport
  • Code for Europe

Add your ideas below. Please, do not overwrite.

  • International collaboration?
  • jlf.fi?
  • ...

What development tools and resources are needed?

Add your ideas below. Please, do not overwrite.

How to get organized?

Possible roles:

  • Concept Director, HSL business view and user experience (Jari Honkonen)
  • Lead Developer, community coordination, any development tasks, code evaluation and version management, organise sprints (Tuukka Hastrup)
  • Team leader, shares tasks in teams
  • Contributor, anyone who contribute code or knowledge to tasks
  • Advisor, share knowledge

Add your ideas below. Please, do not overwrite.

  • Prototype developer, tests risky new ideas in practise
  • Graphical designer, creates the visual experience
  • Community builder, encourages and facilitates participation
  • Device enthusiast, ensures the app works great on a specific device
  • Early/technical user, tests usability, use cases and crowdsourcing
  • ...