HackMD
  • Prime
    Prime  Full-text search on all paid plans
    Search anywhere and reach everything in a Workspace with Prime plan.
    Got it
      • Create new note
      • Create a note from template
    • Prime  Full-text search on all paid plans
      Prime  Full-text search on all paid plans
      Search anywhere and reach everything in a Workspace with Prime plan.
      Got it
      • Sharing Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • More (Comment, Invitee)
      • Publishing
        Everyone on the web can find and read all notes of this public team.
        After the note is published, everyone on the web can find and read this note.
        See all published notes on profile page.
      • Commenting Enable
        Disabled Forbidden Owners Signed-in users Everyone
      • Permission
        • Forbidden
        • Owners
        • Signed-in users
        • Everyone
      • Invitee
      • No invitee
      • Options
      • Versions and GitHub Sync
      • Transfer ownership
      • Delete this note
      • Template
      • Save as template
      • Insert from template
      • Export
      • Dropbox
      • Google Drive
      • Gist
      • Import
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
      • Download
      • Markdown
      • HTML
      • Raw HTML
    Menu Sharing Create Help
    Create Create new note Create a note from template
    Menu
    Options
    Versions and GitHub Sync Transfer ownership Delete this note
    Export
    Dropbox Google Drive Gist
    Import
    Dropbox Google Drive Gist Clipboard
    Download
    Markdown HTML Raw HTML
    Back
    Sharing
    Sharing Link copied
    /edit
    View mode
    • Edit mode
    • View mode
    • Book mode
    • Slide mode
    Edit mode View mode Book mode Slide mode
    Note Permission
    Read
    Only me
    • Only me
    • Signed-in users
    • Everyone
    Only me Signed-in users Everyone
    Write
    Only me
    • Only me
    • Signed-in users
    • Everyone
    Only me Signed-in users Everyone
    More (Comment, Invitee)
    Publishing
    Everyone on the web can find and read all notes of this public team.
    After the note is published, everyone on the web can find and read this note.
    See all published notes on profile page.
    More (Comment, Invitee)
    Commenting Enable
    Disabled Forbidden Owners Signed-in users Everyone
    Permission
    Owners
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Invitee
    No invitee
       owned this note    owned this note      
    Published Linked with GitHub
    Like BookmarkBookmarked
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    --- title: Roadmap --- ## Roadmap ### Motivation This pattern shows how your group can define the scope of their project and make a realistic plan to address it. This pattern provides the backbone of our pattern language. It can be used to find a shared goal. ### Context [Peeragogy](http://peeragogy.github.io/pattern-peeragogy.html) has both distributed and centralized aspects. The discussants or contributors who collaborate on a project have different points of view and heterogeneous priorities, but they come together in conversations and joint activities. ### Forces > ![image](images/variety.png) **Variety**: people have different goals and interests in mind. > ![image](images/clarity.png) **Clarity**: some goals may be quite specific, and some rather vague. > ![image](images/coherence.png) **Coherence**: only some of these goals will be well-aligned. ### Problem In order to collaborate, people need a way to share current, though incomplete, understanding of the space they are working in, and to nurture relationships with one another and the other elements of this space. At the outset, there may not even be a coherent vision for a project – but a only loose collection of motivations and sentiments. Once the project is up and running, people are likely to pull in different directions. ### Solution Building a guide to the goals, activities, experiments and working methods can help <span><span>Newcomers</span></span> and old-timers alike understand their relationship with the project. It may combine features of a manifesto, a syllabus, and an issue tracker. It may be a design pattern or a pattern language <span class="citation">\[3\]</span>. The distinguishing qualities of a project Roadmap are that it should be adaptive to circumstances, and that it should ultimately get us from *here* to *there*. By this same token, any given version of the roadmap is seen as fallible. In lieu of widespread participation, the project’s <span><span>Wrapper</span></span> should attempt to synthesize an accurate roadmap that is informed by participants’ behavior, and should help moderate in case of conflict. Nevertheless, full consensus is not necessary: different goals, with different *heres* and *theres*, can be pursued separately, while maintaining communication. ### Rationale The group evolves from a less-sophisticated to a more-sophisticated manner of operating by using the roadmap. Using the roadmap builds a collective awareness of how things are working in practice. In the Peeragogy project our initial roadmap was a “crowdsourced” outline of the first edition of the *Peeragogy Handbook*. Later, it took the form of a schedule of meetings following a regular <span><span>Heartbeat</span></span>, supplemented by a list of upcoming deadlines. Most recently, our roadmap is expressed in the emergent objectives collected at the end of current paper. We have seen that a list of nice-to-have features created in a top-down fashion is comparatively unlikely to go anywhere! A backlog of tasks and a realistic plan for accomplishing them are vastly different things. An adaptive roadmap is an antidote to <span><span>Tunnel Vision</span></span> <span class="citation">\[1\]</span>. ### Resolution An emergent roadmap is rooted in real problems and justifiable solutions-in-progress in all their **variety** and communicates both resolution and follow-through. The process of meshing varied issues with one another requires thought and discussion, and this encourages **clarity**. The test of **coherence** is that contributed goals and ideas should be actionable. The ultimate quality-control test is if it worked, i.e., did it come to pass that the task(s) the roadmap was created to achieve ended up being achieved? If all of the issues that the roadmap outlines are not resolved, the roadmap itself should be revised. Without a roadmap, we would never know. ### Example 1 The *Help* link present on every Wikipedia page could be seen as a localized <span><span>Roadmap</span></span> for individual user engagement: it tells users what they can do with the site, and gives instructions on how to do it.[^fn1] someone who knows what they’re doing, there are around 30 pages listing articles with various kinds of problems, for example articles tagged with style issues, or “orphaned” articles (i.e., articles with no links from other pages in the encyclopedia).[^fn2]<sup>,</sup>[^fn3]<sup>,</sup>[^fn4] In 2010-2011, Wikimedia developed a strategic plan drawing on community input <span class="citation">\[2\]</span>. In 2015, a two-week Community Consultation was carried out; synthesis resulted in “a direction that will guide the decisions for the organization.”[^fn5] Community-organized WikiProjects often invite and guide involvement on <span><span>A specific project</span></span>. ### Example 2 In a future university run in a peer produced manner, a fancy President’s Residence presumably wouldn’t be needed. Leadership would be carried out in a more collaborative and distributed fashion. However, depending on just how distributed things are, it may turn out to be useful for project facilitators to gather at a University Hall. Whereas there is strength in numbers, there is leverage in organization. This is what the <span><span>Roadmap</span></span> provides. ![image](images/alabama-small.jpg) *President's Residence, University of Alabama.* ### What’s Next in the Peeragogy Project If it becomes clear that something needs to change about the project, that is a clue that we might need to revise our patterns or record a new one. We can use the names of the patterns to tag our upcoming tasks. ### References 1. David M. Dikel, David Kane, and James R. Wilson. 2001. *Software architecture: Organizational principles and patterns*. Pearson Education. 2. Eugene Eric Kim and others. 2011. *Wikimedia Strategic Plan: A collaborative vision for the movement through 2015*. Wikimedia Foundation. 3. Christian Kohls. 2010. The structure of patterns. *Proceedings of the 17th Conference on Pattern Languages of Programs*, ACM, 12. ------------------------------------------------------------------------ [^fn1]: <https://en.wikipedia.org/wiki/Help:Contents> [^fn2]: <https://en.wikipedia.org/wiki/Category:Wikipedia_article_cleanup> [^fn3]: <https://en.wikipedia.org/wiki/Category:Wikipedia_articles_with_style_issues> [^fn4]: <https://en.wikipedia.org/wiki/Category:All_orphaned_articles> [^fn5]: <https://blog.wikimedia.org/2015/02/23/strategy-consultation/> [^fn6]: <https://blog.wikimedia.org/2015/08/27/strategy-potential-mobile-multimedia-translation/>

    Import from clipboard

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lost their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template is not available.


    Upgrade

    All
    • All
    • Team
    No template found.

    Create custom template


    Upgrade

    Delete template

    Do you really want to delete this template?

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Tutorials

    Book Mode Tutorial

    Slide Mode Tutorial

    YAML Metadata

    Contacts

    Facebook

    Twitter

    Feedback

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions

    Versions and GitHub Sync

    Sign in to link this note to GitHub Learn more
    This note is not linked with GitHub Learn more
     
    Add badge Pull Push GitHub Link Settings
    Upgrade now

    Version named by    

    More Less
    • Edit
    • Delete

    Note content is identical to the latest version.
    Compare with
      Choose a version
      No search result
      Version not found

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub

        Please sign in to GitHub and install the HackMD app on your GitHub repo. Learn more

         Sign in to GitHub

        HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Available push count

        Upgrade

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Upgrade

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully