Skip to content
This repository was archived by the owner on Jul 31, 2025. It is now read-only.

Class Activity: Roadmap

Jump to bottom
Nic edited this page May 4, 2017 · 3 revisions

Intro
A technical roadmap is a project management tool for planning a technical project. They can both document high level goals ("Complete a draft of final paper") as well as organize specific tasks that help you meet those goals ("Write abstract"). When done well, a roadmap will allow you to transparently track your progress towards meeting a goal. Roadmaps also create 'owners' of a specific task - so that

Goal
Develop a roadmap to complete your curation protocol. Create owners, create deadlines, and start deciding on data sources (datasets you will curate), and what form you want your final report to take *

Remember, at a bare minimum (aka you have to at least do this to pass)

  • Project definition, scope, and audience (Week 2)
  • User stories that define stakeholders (Week 4)
  • Justification for selecting repository software (the system design) (Week 3)
  • Metadata needs, and proposed schema (Week 5)
  • Deposit policies (who, what, size, formats, etc.) (Week 6)
  • Ingest, Transformation, Licensing, and Preservation Policies (Week 8)
  • Curated datasets (Week 7 we will do an exercise on this, but you will continue to work on this throughout the quarter)
  • Summative Evaluation You will be required to produce a written report that coherently brings together each of the pieces described above. How much you build and report on, and how much you choose to describe in a speculative (forward looking) way is up to you.

How

  • There is an excellent roadmap planning tool built into Github - see the tab Projects
  • Here you can create a "board" with all of the issues or tasks needed to complete your project.
  • When you create an issue you can add this to a column, and then move the issue back and forth between columns
  • There are a number of different ways to organize this - find what works best for your team.

** Let me make a pitch for building a 'GitBook' for your final deliverable. These are easy to make from your existing github documentation, and they are valuable for something like an online portfolio. If you need any help setting them up - please ask!

Clone this wiki locally