|
1 | | -RNI Schedule Plotr |
| 1 | +Ushahidi Programs Plotr |
2 | 2 | =========== |
3 | | -[](https://bitdeli.com/free "Bitdeli Badge") |
4 | | - |
5 | | -This is a visualization of projects and milestones for RNI. |
6 | | - |
7 | | -Check out the [Pirate Plotr Render here](http://auremoser.github.io/pirateplotr/). |
| 3 | +This is a visualization tool for looking at key deliverables and milestones milestones for Ushahidi programs. You can see the [Plotr visualization here](http://?????) or [add dates and milesontes here](https://docs.google.com/spreadsheets/d/1NXG2znwFFdbyK83wHmN00AEp_t_OMAoRkShicl_y7Wk/edit#gid=0). See below for more information about how to interpret the visualization or enter data. |
8 | 4 |
|
9 | 5 | ### about |
10 | | -This simple sortable chart for viewing projects and tracking them on a timeline is primarily for coordination between RNI and the Rockefeller Foundation, including the 100 Resilient Cities team. It is useful for a quick global view of what's going on when and how the milestones/expectations/resourcing need to be managed. |
| 6 | +This is simple sortable chart for viewing and tracking programmatic deliverables and milestones on a timeline. It is primarily for coordination among Ushahidi programs: especially around shared goals such as trainings, volunteer engagement, and product releases. It is useful for a quick global view of what's going on when and how the milestones/expectations/resourcing need to be managed. This was originally developed by Aurelia Moser ([original repo here](https://github.com/auremoser/pirateplotr)) and I've adopted it for programmatic use. |
11 | 7 |
|
12 | 8 | ### how to |
13 | | -1. Edit data in the Google Spreadsheet [here](https://docs.google.com/a/ushahidi.com/spreadsheets/d/1C-s16NaQBkzZSHRl1SvFBjnvJ03GQ74yJ2-Bf5MW1u0/edit#gid=0). |
14 | | -2. Spreadsheet will update in the chart on a semi-frequent basis (depends on google, usually you can refresh the [RNI Schedule Plotr](XXXXXXXXX) every 5 minutes and it will show your changes); all changes will be checked and QAuto-integrated for Monday morning calls. |
15 | | -3. View and Sort the chart! [Check the RNI Schedule Plotr Render page.](XXXXXXXX) |
| 9 | +1. Edit data in the Google Spreadsheet [here](https://docs.google.com/spreadsheets/d/1NXG2znwFFdbyK83wHmN00AEp_t_OMAoRkShicl_y7Wk/edit#gid=0). See the key below for what information to enter in which columns. |
| 10 | +2. Spreadsheet will update in the chart on a semi-frequent basis, which depends on google. Usually you can refresh the [Plotr visualization](http://?????) every 5 minutes and it will show your changes. |
| 11 | +3. View and Sort the chart! [Plotr visualization here](http://?????) |
16 | 12 |
|
17 | | - |
| 13 | + |
18 | 14 |
|
19 | 15 | ### data |
20 | 16 | Data csv looks like this: |
21 | 17 |
|
22 | | - |
| 18 | + |
23 | 19 |
|
24 | | -Headers are static, but all values are editable in the data.csv file. |
| 20 | +Headers in the spreadsheet are static, but all values are editable in the data.csv file. |
25 | 21 |
|
26 | 22 | deliverable | priority | start_date | end_date | team | type |
27 | 23 | :---: | :----: | :--------: | :------: | :----: | :----: |
28 | | -project1 | value1 | date1 | date2 | [V3/CrisisNet/...] | external |
29 | | -project2 | value2 | date1 | date2 | [V3/CrisisNet/...] | core |
| 24 | +project1 | value1 | date1 | date2 | [DREAMS/Uchaguzi/...] | external |
| 25 | +project2 | value2 | date1 | date2 | [DREAMS/Uchaguzi/...] | core |
30 | 26 |
|
31 | 27 | #### key |
32 | | -* **deliverable** is project name |
33 | | -* **priority** is an arbitrary weight (price point? resources?)[2] |
34 | | -* **dates** are the start and end date of a project |
35 | | -* **team** is the name of the team responsible for the deliverable |
36 | | -* **type** is one of 4 categories for filtering purposes (core, external, ops, milestone)[3] |
37 | | - |
38 | | -This is spreadsheet-powered because that's a maintainable format for all contributors; easily editable/updatable. |
39 | | - |
40 | | -Yays thanks for reading! Shoot me questions if you have any: aurelia@ushahidi.com. |
41 | | - |
42 | | -[1]: Previously, I manually updated the /data/data.csv file and then populated that data in the chart. Now the chart is GDoc powered, to enable easier editing for all pirates in the party. :) |
43 | | - |
44 | | -[2]: We can decide what numerical value to prioritize by, I just wanted to log this as a sortable placeholder for future values we might want to track. |
| 28 | +* **deliverable** is _brief_ description of the deliverable. |
| 29 | +* **priority** is an arbitrary weight. This is a placeholder that was originally intended to be replaced by some numerical value that we might want to priotize by, such as cost, price, or resources. We can figure out how to use this... or leave it blank! |
| 30 | +* **dates** are the start and end date of a project. |
| 31 | +* **team** is the name of the team responsible for the deliverable. I've populated the spreadsheet with a drop-down menu for: Uchaguzi, DREAMS, COMRADES, and Platform. |
| 32 | +* **type** is one of 4 categories for filtering purposes (core, external, ops, milestone). I don't honestly remember what these different categories meant! So I'd be happy to change them. Right now, I'm using "core" as an internal deadline while "external" is something public facing. Milestones are vertical plum lines on the chart. You can draw a plum line, as opposed to a bar, by entering a deliverable name, start_date and type of project as "milestone"). Check the csv for examples of this. |
45 | 33 |
|
46 | | -[3]: Milestones are vertical plum lines on the chart. You can draw a plum line, as opposed to a bar, by entering a deliverable name, start_date and type of project as "milestone"). Check the csv for examples of this. |
| 34 | +Give me a shout if you have any further questions! |
47 | 35 |
|
48 | 36 |
|
49 | 37 |
|
|
0 commit comments