http://wiki.carlmontrobotics.org/api.php?action=feedcontributions&user=DBrettle&feedformat=atomDeep Blue Robotics Wiki - User contributions [en]2024-03-28T08:56:24ZUser contributionsMediaWiki 1.26.4http://wiki.carlmontrobotics.org/index.php?title=Team_Dashboard&diff=2198Team Dashboard2016-12-13T02:39:56Z<p>DBrettle: Added public calendar</p>
<hr />
<div>{{#widget:Google Calendar<br />
|id=qe00842sq89075ub4n9l3lhai4@group.calendar.google.com<br />
|color=528800<br />
|id=1ammtst2iopqspnr6k93lsjhes@group.calendar.google.com<br />
|color=528800<br />
|id=usa@holiday.calendar.google.com<br />
|color=B1440E<br />
|title=Carlmont Robotics Team Calendar and US Holidays<br />
}}</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Project_planning_tool_evaluations&diff=1735Project planning tool evaluations2016-10-20T17:30:27Z<p>DBrettle: Documented what I remember from evaluating various project planning tools</p>
<hr />
<div><br />
== Criteria ==<br />
<br />
<br />
=== Supports resource management/leveling ===<br />
<br />
The primary challenge we face when trying to plan/schedule projects is that many team members have skills in several different areas and only a handful of team members have skill in some areas. It can require considerable experimentation with resource allocation (assigning team members to tasks) to ensure that projects are completed as quickly as possible and with the most efficient use of our team members. Many project management tools allow resources to be allocated to different tasks and then allow the user to manually schedule the tasks and see whether resource conflicts occur. However, with many tasks and resources it is incredibly time consuming to do this for each resource allocation under consideration. We need a tool which automates this process by providing a way (sometimes called resource leveling) to click a button and have the tasks rescheduled so that dependencies are satisfied and no resource is overscheduled. <br />
<br />
=== Collaborative ===<br />
<br />
Subteam leads should be able to provide estimates concurrently and it should be easy for anyone to be able to see the latest schedule. This implies that the tool is an online/collaborative tool.<br />
<br />
=== Cost ===<br />
<br />
Should cost less than $200/year for all of leadership and most mentors (~20 people) to be able to edit and all team members (~75 people) to be able to view the schedule. This typically rules out any tool that has per-user pricing. GoDaddy provides some tools for free and allows installation of some other tools, though not ones that require long running processes (e.g. ones based on Java). In some cases self-hosting at Digital Ocean may be practical/affordable.<br />
<br />
=== Usable from mobile devices ===<br />
<br />
Many team members find it more convenient to to use their phones than a desktop app.<br />
<br />
=== Open source ===<br />
<br />
Avoids vendor lock-in.<br />
<br />
== Tools evaluated ==<br />
<br />
=== [http://gantter.com Gantter] ===<br />
<br />
This is what we've ended up going with. Only downsides are that it is not open source and does not have a working mobile app for Android and [https://itunes.apple.com/us/app/gantter-vu/id704683884?mt=8 the $5 iOS app has received very negative reviews].<br />
<br />
=== [http://www.libreplan.org/home/ LibrePlan] ===<br />
<br />
Supposedly supports resource leveling and is collaborative and open source. However, we would need to self-host and there does not appear to be mobile support. There is an Android app but it doesn't look like it only supports time tracking, not planning.<br />
<br />
=== MS Project ===<br />
<br />
Supports resource leveling but the desktop version is not collaborative and the online version is too expensive. Also, not open source.<br />
<br />
=== [http://www.calligra.org/plan/ Calligra Plan] ===<br />
<br />
Supports resource leveling and is open source, but is desktop only and support for Windows/Mac is preliminary. No mobile support.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Project_planning_tool_evaluations&diff=1734Project planning tool evaluations2016-10-20T17:07:42Z<p>DBrettle: /* Criteria */</p>
<hr />
<div><br />
== Criteria ==<br />
<br />
<br />
=== Supports resource management/leveling ===<br />
<br />
The primary challenge we face when trying to plan/schedule projects is that many team members have skills in several different areas and only a handful of team members have skill in some areas. It can require considerable experimentation with resource allocation (assigning team members to tasks) to ensure that projects are completed as quickly as possible and with the most efficient use of our team members. Many project management tools allow resources to be allocated to different tasks and then allow the user to manually schedule the tasks and see whether resource conflicts occur. However, with many tasks and resources it is incredibly time consuming to do this for each resource allocation under consideration. We need a tool which automates this process by providing a way (sometimes called resource leveling) to click a button and have the tasks rescheduled so that dependencies are satisfied and no resource is overscheduled. <br />
<br />
=== Collaborative ===<br />
<br />
Subteam leads should be able to provide estimates concurrently and it should be easy for anyone to be able to see the latest schedule. This implies that the tool is an online/collaborative tool.<br />
<br />
=== Usable from mobile devices ===<br />
<br />
Many team members find it more convenient to to use their phones than a desktop app.<br />
<br />
=== Open source ===<br />
<br />
Avoids vendor lock-in.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Project_planning_tool_evaluations&diff=1733Project planning tool evaluations2016-10-20T16:45:29Z<p>DBrettle: Created page with " == Criteria == Supports resource management/leveling - The primary challenge we face when trying to plan/schedule projects is that many team members have skills in several..."</p>
<hr />
<div><br />
== Criteria ==<br />
<br />
<br />
Supports resource management/leveling - The primary challenge we face when trying to plan/schedule projects is that many team members have skills in several different areas and only a handful of team members have skill in some areas. It can require considerable experimentation with resource allocation (assigning team members to tasks) to ensure that projects are completed as quickly as possible and with the most efficient use of our team members. Many project management tools allow resources to be allocated to different tasks and then allow the user to manually schedule the tasks and see whether resource conflicts occur. However, with many tasks and resources it is incredibly time consuming to do this for each resource allocation under consideration. We need a tool which automates this process by providing a way (sometimes called resource leveling) to click a button and have the tasks rescheduled so that dependencies are satisfied and no resource is overscheduled. <br />
<br />
Collaborative - Subteam leads should be able to provide estimates concurrently and it should be easy for anyone to be able to see the latest schedule. This implies that the tool is an online/collaborative tool.<br />
<br />
Usable from mobile devices - Many team members find it more convenient to to use their phones than a desktop app.<br />
<br />
Open source - Avoids vendor lock-in.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Information_Technology&diff=1732Information Technology2016-10-20T16:28:59Z<p>DBrettle: </p>
<hr />
<div><br />
[[Adding_extensions_to_the_wiki|Adding extensions to the wiki]]<br />
<br />
[[Task tracking tool evaluations]]<br />
<br />
[[Project planning tool evaluations]]</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1691Task tracking tool evaluations2016-10-13T05:19:29Z<p>DBrettle: Added link to Trello<->Slack integration</p>
<hr />
<div>== Features ==<br />
See below for a description of the features.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Supports_checklists|Supports checklists]]<br />
![[#Can_duplicate_objects|Can duplicate objects]]<br />
![[#Clear_terminology|Clear terminology]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|<br />
|<br />
|<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes<br />
|No<br />
|No<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only and all notifications for a Taiga project (which might contain all of our projects) go to the same channel. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| + Custom fields<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[https://github.com/mayflower/PHProjekt PHProjekt]<br />
|No<br />
|<br />
|<br />
|<br />
|Not tested<br />
|Free<br />
|No<br />
|Yes. Infinite depth<br />
|No<br />
|Yes but see notes.<br />
| + Easy to install from GoDaddy CPanel<br />
- Project is unmaintained since 2013<br />
<br />
- Website is unreachable<br />
<br />
|-<br />
|[http://www.thebuggenie.com/ BugGenie]<br />
|Yes<br />
|Yes<br />
|<br />
|Yes<br />
|Yes but ''very'' clunky. No drag/drop. Need to refresh to see changes.<br />
|Free on GoDaddy.<br />
|No.<br />
|Yes. Infinite depth. Terminology seems flexible.<br />
|Notifications only via [http://www.thebuggenie.com/addons/slack addon] (not evaluated). Notifications for different projects can be sent to different channels.<br />
|Yes<br />
|<nowiki>+ Supports swimlanes for different categories, types, or priorities.</nowiki>+ Custom task types, fields, and work flows<br />
<br />
- Sluggish UI<br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|<br />
|<br />
|<br />
|Yes, via apps for Android and iOS<br />
|Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|Yes, though the default configuration is a bit limiting. There are [http://www.pivotaltracker.com/help/articles/tracker_and_kanban/ workarounds and add-ons] to make it more general purpose.<br />
|<br />
|Cards<br />
|No<br />
|Yes, via apps for "alpha" Android and iOS.<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|No. <br />
|Yes. Projects > epics > user stories > tasks<br />
|[https://t199tst.slack.com/apps/A0F82E7H8-pivotal-tracker Notifications only] (not evaluated).<br />
|No<br />
| + Responsive UI<br />
|-<br />
|Trello<br />
|Yes.<br />
|<br />
|Cards and lists<br />
|Yes. Neutral terminology.<br />
|Yes, via apps for Android and iOS<br />
|Free<br />
|No. However there is a [https://github.com/BeIntrepid/Trello-Card-Dependencies Chrome extension that adds dependency support] (not evaluated)<br />
|Yes. Lists > cards > checklists<br />
|[http://help.trello.com/article/1049-slack-app Yes] but somewhat limited. 1-to-1 linking between channels and boards, which is not ideal if we have multiple projects on one board.<br />
|No.<br />
| + Very responsive UI on web and mobile.<br />
<br />
- Limited ability to manage permissions<br />
|-<br />
|JIRA<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|Per user pricing but might qualify for free [https://www.atlassian.com/survey/classroom-license-request.jsp classroom license] or [https://www.atlassian.com/software/views/open-source-license-request open source license].<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Kanboard<br />
|Yes.<br />
|<br />
|Cards<br />
|Yes.<br />
|Yes via clunky mobile-ready web UI. No drag and drop<br />
|Free if we host it ourselves. Cheap otherwise (no per-user pricing)<br />
|No<br />
|Yes. Projects > lists > tasks > subtasks<br />
|<br />
|Yes<br />
| <br />
|-<br />
|Wekan.io<br />
|Yes<br />
|No<br />
|None<br />
|Yes. Neutral terminology.<br />
|<br />
|Free if we host it.<br />
|<br />
|Yes. Lists > Cards<br />
|<br />
|Yes<br />
| <br />
|-<br />
|Restya.com<br />
|Yes<br />
|Yes<br />
|Cards only<br />
|Yes. Neutral terminology.<br />
|Yes via clunky mobile-ready web UI. No drag and drop<br />
|Free if we host it<br />
|No<br />
|Yes. Lists > Cards > checklists<br />
|[http://restya.com/board/integrations/slack Maybe via Zapier] (not evaluated, not well documented)<br />
|Yes<br />
| + Supposedly good permissions management<br />
- No Google login<br />
|-<br />
|Freedcamp<br />
|Yes, but seems limited to 3 columns (No Progress, In Progress, Completed).<br />
|Yes<br />
|No<br />
|Mostly. To get all projects on one task board, there would be one Freedcamp project that would correspond to our entire year and each of our projects would correspond to a task group.<br />
|Yes via clunky mobile-ready web UI. No drag and drop. iOS app released in 9/2016. Android app expected by end of 2016.<br />
|Free, unless we need more storage or special apps<br />
|No<br />
|Yes. Projects > task groups > tasks > subtasks<br />
|No<br />
|No<br />
| + Supports swimlanes in the form of task groups. Could use one task group for each of our projects.<br />
- No labels/tags<br />
<br />
- Task board seems to require a refresh to see changes by other users<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Supports checklists ==<br />
Checklists on a card can be used to enforce quality control procedures.<br />
<br />
== Can duplicate objects ==<br />
The ability to duplicate checklists, cards, lists, and/or boards is very useful for ensuring processes are followed. Sets of objects that we treat as templates can be used to document the processes.<br />
<br />
== Clear terminology ==<br />
Many task board tools are focused on agile/scrum software development methodologies. Those methodologies introduce new terms like User Story and Epic, and use terms like Task and Project in ways that are different from the way we use those terms internally. A tool which uses either our terminology or neutral terminology (e.g. boards, lists, cards, and checklists) would reduce confusion and speed/simplify adoption.<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1689Task tracking tool evaluations2016-10-11T22:16:40Z<p>DBrettle: Evaluated Freedcamp</p>
<hr />
<div>== Features ==<br />
See below for a description of the features.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Supports_checklists|Supports checklists]]<br />
![[#Can_duplicate_objects|Can duplicate objects]]<br />
![[#Clear_terminology|Clear terminology]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|<br />
|<br />
|<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes<br />
|No<br />
|No<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only and all notifications for a Taiga project (which might contain all of our projects) go to the same channel. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| + Custom fields<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[https://github.com/mayflower/PHProjekt PHProjekt]<br />
|No<br />
|<br />
|<br />
|<br />
|Not tested<br />
|Free<br />
|No<br />
|Yes. Infinite depth<br />
|No<br />
|Yes but see notes.<br />
| + Easy to install from GoDaddy CPanel<br />
- Project is unmaintained since 2013<br />
<br />
- Website is unreachable<br />
<br />
|-<br />
|[http://www.thebuggenie.com/ BugGenie]<br />
|Yes<br />
|Yes<br />
|<br />
|Yes<br />
|Yes but ''very'' clunky. No drag/drop. Need to refresh to see changes.<br />
|Free on GoDaddy.<br />
|No.<br />
|Yes. Infinite depth. Terminology seems flexible.<br />
|Notifications only via [http://www.thebuggenie.com/addons/slack addon] (not evaluated). Notifications for different projects can be sent to different channels.<br />
|Yes<br />
|<nowiki>+ Supports swimlanes for different categories, types, or priorities.</nowiki>+ Custom task types, fields, and work flows<br />
<br />
- Sluggish UI<br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|<br />
|<br />
|<br />
|Yes, via apps for Android and iOS<br />
|Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|Yes, though the default configuration is a bit limiting. There are [http://www.pivotaltracker.com/help/articles/tracker_and_kanban/ workarounds and add-ons] to make it more general purpose.<br />
|<br />
|Cards<br />
|No<br />
|Yes, via apps for "alpha" Android and iOS.<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|No. <br />
|Yes. Projects > epics > user stories > tasks<br />
|[https://t199tst.slack.com/apps/A0F82E7H8-pivotal-tracker Notifications only] (not evaluated).<br />
|No<br />
| + Responsive UI<br />
|-<br />
|Trello<br />
|Yes.<br />
|<br />
|Cards and lists<br />
|Yes. Neutral terminology.<br />
|Yes, via apps for Android and iOS<br />
|Free<br />
|No. However there is a [https://github.com/BeIntrepid/Trello-Card-Dependencies Chrome extension that adds dependency support] (not evaluated)<br />
|Yes. Lists > cards > checklists<br />
|Not included in free plan. Must pay $9.99/user/month<br />
|No.<br />
| + Very responsive UI on web and mobile.<br />
<br />
- Limited ability to manage permissions<br />
|-<br />
|JIRA<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|Per user pricing but might qualify for free [https://www.atlassian.com/survey/classroom-license-request.jsp classroom license] or [https://www.atlassian.com/software/views/open-source-license-request open source license].<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Kanboard<br />
|Yes.<br />
|<br />
|Cards<br />
|Yes.<br />
|Yes via clunky mobile-ready web UI. No drag and drop<br />
|Free if we host it ourselves. Cheap otherwise (no per-user pricing)<br />
|No<br />
|Yes. Projects > lists > tasks > subtasks<br />
|<br />
|Yes<br />
| <br />
|-<br />
|Wekan.io<br />
|Yes<br />
|No<br />
|None<br />
|Yes. Neutral terminology.<br />
|<br />
|Free if we host it.<br />
|<br />
|Yes. Lists > Cards<br />
|<br />
|Yes<br />
| <br />
|-<br />
|Restya.com<br />
|Yes<br />
|Yes<br />
|Cards only<br />
|Yes. Neutral terminology.<br />
|Yes via clunky mobile-ready web UI. No drag and drop<br />
|Free if we host it<br />
|No<br />
|Yes. Lists > Cards > checklists<br />
|[http://restya.com/board/integrations/slack Maybe via Zapier] (not evaluated, not well documented)<br />
|Yes<br />
| + Supposedly good permissions management<br />
- No Google login<br />
|-<br />
|Freedcamp<br />
|Yes, but seems limited to 3 columns (No Progress, In Progress, Completed).<br />
|Yes<br />
|No<br />
|Mostly. To get all projects on one task board, there would be one Freedcamp project that would correspond to our entire year and each of our projects would correspond to a task group.<br />
|Yes via clunky mobile-ready web UI. No drag and drop. iOS app released in 9/2016. Android app expected by end of 2016.<br />
|Free, unless we need more storage or special apps<br />
|No<br />
|Yes. Projects > task groups > tasks > subtasks<br />
|No<br />
|No<br />
| + Supports swimlanes in the form of task groups. Could use one task group for each of our projects.<br />
- No labels/tags<br />
<br />
- Task board seems to require a refresh to see changes by other users<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Supports checklists ==<br />
Checklists on a card can be used to enforce quality control procedures.<br />
<br />
== Can duplicate objects ==<br />
The ability to duplicate checklists, cards, lists, and/or boards is very useful for ensuring processes are followed. Sets of objects that we treat as templates can be used to document the processes.<br />
<br />
== Clear terminology ==<br />
Many task board tools are focused on agile/scrum software development methodologies. Those methodologies introduce new terms like User Story and Epic, and use terms like Task and Project in ways that are different from the way we use those terms internally. A tool which uses either our terminology or neutral terminology (e.g. boards, lists, cards, and checklists) would reduce confusion and speed/simplify adoption.<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1688Task tracking tool evaluations2016-10-10T22:23:45Z<p>DBrettle: Links to new criteria</p>
<hr />
<div>== Features ==<br />
See below for a description of the features.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Supports_checklists|Supports checklists]]<br />
![[#Can_duplicate_objects|Can duplicate objects]]<br />
![[#Clear_terminology|Clear terminology]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|<br />
|<br />
|<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes<br />
|No<br />
|No<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only and all notifications for a Taiga project (which might contain all of our projects) go to the same channel. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| + Custom fields<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[https://github.com/mayflower/PHProjekt PHProjekt]<br />
|No<br />
|<br />
|<br />
|<br />
|Not tested<br />
|Free<br />
|No<br />
|Yes. Infinite depth<br />
|No<br />
|Yes but see notes.<br />
| + Easy to install from GoDaddy CPanel<br />
- Project is unmaintained since 2013<br />
<br />
- Website is unreachable<br />
<br />
|-<br />
|[http://www.thebuggenie.com/ BugGenie]<br />
|Yes<br />
|Yes<br />
|<br />
|Yes<br />
|Yes but ''very'' clunky. No drag/drop. Need to refresh to see changes.<br />
|Free on GoDaddy.<br />
|No.<br />
|Yes. Infinite depth. Terminology seems flexible.<br />
|Notifications only via [http://www.thebuggenie.com/addons/slack addon] (not evaluated). Notifications for different projects can be sent to different channels.<br />
|Yes<br />
|<nowiki>+ Supports swimlanes for different categories, types, or priorities.</nowiki>+ Custom task types, fields, and work flows<br />
<br />
- Sluggish UI<br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|<br />
|<br />
|<br />
|Yes, via apps for Android and iOS<br />
|Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|Yes, though the default configuration is a bit limiting. There are [http://www.pivotaltracker.com/help/articles/tracker_and_kanban/ workarounds and add-ons] to make it more general purpose.<br />
|<br />
|Cards<br />
|No<br />
|Yes, via apps for "alpha" Android and iOS.<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|No. <br />
|Yes. Projects > epics > user stories > tasks<br />
|[https://t199tst.slack.com/apps/A0F82E7H8-pivotal-tracker Notifications only] (not evaluated).<br />
|No<br />
| + Responsive UI<br />
|-<br />
|Trello<br />
|Yes.<br />
|<br />
|Cards and lists<br />
|Yes. Neutral terminology.<br />
|Yes, via apps for Android and iOS<br />
|Free<br />
|No. However there is a [https://github.com/BeIntrepid/Trello-Card-Dependencies Chrome extension that adds dependency support] (not evaluated)<br />
|Yes. Lists > cards > checklists<br />
|Not included in free plan. Must pay $9.99/user/month<br />
|No.<br />
| + Very responsive UI on web and mobile.<br />
<br />
- Limited ability to manage permissions<br />
|-<br />
|JIRA<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|Per user pricing but might qualify for free [https://www.atlassian.com/survey/classroom-license-request.jsp classroom license] or [https://www.atlassian.com/software/views/open-source-license-request open source license].<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Kanboard<br />
|Yes.<br />
|<br />
|Cards<br />
|Yes.<br />
|Yes via clunky mobile-ready web UI. No drag and drop<br />
|Free if we host it ourselves. Cheap otherwise (no per-user pricing)<br />
|No<br />
|Yes. Projects > lists > tasks > subtasks<br />
|<br />
|Yes<br />
| <br />
|-<br />
|Wekan.io<br />
|Yes<br />
|No<br />
|None<br />
|Yes. Neutral terminology.<br />
|<br />
|Free if we host it.<br />
|<br />
|Yes. Lists > Cards<br />
|<br />
|Yes<br />
| <br />
|-<br />
|Restya.com<br />
|Yes<br />
|Yes<br />
|Cards only<br />
|Yes. Neutral terminology.<br />
|Yes via clunky mobile-ready web UI. No drag and drop<br />
|Free if we host it<br />
|No<br />
|Yes. Lists > Cards > checklists<br />
|[http://restya.com/board/integrations/slack Maybe via Zapier] (not evaluated, not well documented)<br />
|Yes<br />
| + Supposedly good permissions management<br />
- No Google login<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Supports checklists ==<br />
Checklists on a card can be used to enforce quality control procedures.<br />
<br />
== Can duplicate objects ==<br />
The ability to duplicate checklists, cards, lists, and/or boards is very useful for ensuring processes are followed. Sets of objects that we treat as templates can be used to document the processes.<br />
<br />
== Clear terminology ==<br />
Many task board tools are focused on agile/scrum software development methodologies. Those methodologies introduce new terms like User Story and Epic, and use terms like Task and Project in ways that are different from the way we use those terms internally. A tool which uses either our terminology or neutral terminology (e.g. boards, lists, cards, and checklists) would reduce confusion and speed/simplify adoption.<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1687Task tracking tool evaluations2016-10-10T22:17:52Z<p>DBrettle: Added criteria for checklist support, ability to duplicate objects, and terminology</p>
<hr />
<div>== Features ==<br />
See below for a description of the features.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![http://wiki.carlmontrobotics.org/Task_tracking_tool_evaluations#Supports_checklists Supports checklists]<br />
!Can duplicate objects<br />
!Clear terminology<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|<br />
|<br />
|<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes<br />
|No<br />
|No<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only and all notifications for a Taiga project (which might contain all of our projects) go to the same channel. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| + Custom fields<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[https://github.com/mayflower/PHProjekt PHProjekt]<br />
|No<br />
|<br />
|<br />
|<br />
|Not tested<br />
|Free<br />
|No<br />
|Yes. Infinite depth<br />
|No<br />
|Yes but see notes.<br />
| + Easy to install from GoDaddy CPanel<br />
- Project is unmaintained since 2013<br />
<br />
- Website is unreachable<br />
<br />
|-<br />
|[http://www.thebuggenie.com/ BugGenie]<br />
|Yes<br />
|Yes<br />
|<br />
|Yes<br />
|Yes but ''very'' clunky. No drag/drop. Need to refresh to see changes.<br />
|Free on GoDaddy.<br />
|No.<br />
|Yes. Infinite depth. Terminology seems flexible.<br />
|Notifications only via [http://www.thebuggenie.com/addons/slack addon] (not evaluated). Notifications for different projects can be sent to different channels.<br />
|Yes<br />
|<nowiki>+ Supports swimlanes for different categories, types, or priorities.</nowiki>+ Custom task types, fields, and work flows<br />
<br />
- Sluggish UI<br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|<br />
|<br />
|<br />
|Yes, via apps for Android and iOS<br />
|Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|Yes, though the default configuration is a bit limiting. There are [http://www.pivotaltracker.com/help/articles/tracker_and_kanban/ workarounds and add-ons] to make it more general purpose.<br />
|<br />
|Cards<br />
|No<br />
|Yes, via apps for "alpha" Android and iOS.<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|No. <br />
|Yes. Projects > epics > user stories > tasks<br />
|[https://t199tst.slack.com/apps/A0F82E7H8-pivotal-tracker Notifications only] (not evaluated).<br />
|No<br />
| + Responsive UI<br />
|-<br />
|Trello<br />
|Yes.<br />
|<br />
|Cards and lists<br />
|Yes. Neutral terminology.<br />
|Yes, via apps for Android and iOS<br />
|Free<br />
|No. However there is a [https://github.com/BeIntrepid/Trello-Card-Dependencies Chrome extension that adds dependency support] (not evaluated)<br />
|Yes. Lists > cards > checklists<br />
|Not included in free plan. Must pay $9.99/user/month<br />
|No.<br />
| + Very responsive UI on web and mobile.<br />
<br />
- Limited ability to manage permissions<br />
|-<br />
|JIRA<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|Per user pricing but might qualify for free [https://www.atlassian.com/survey/classroom-license-request.jsp classroom license] or [https://www.atlassian.com/software/views/open-source-license-request open source license].<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Kanboard<br />
|Yes.<br />
|<br />
|Cards<br />
|Yes.<br />
|Yes via clunky mobile-ready web UI. No drag and drop<br />
|Free if we host it ourselves. Cheap otherwise (no per-user pricing)<br />
|No<br />
|Yes. Projects > lists > tasks > subtasks<br />
|<br />
|Yes<br />
| <br />
|-<br />
|Wekan.io<br />
|Yes<br />
|No<br />
|None<br />
|Yes. Neutral terminology.<br />
|<br />
|Free if we host it.<br />
|<br />
|Yes. Lists > Cards<br />
|<br />
|Yes<br />
| <br />
|-<br />
|Restya.com<br />
|Yes<br />
|Yes<br />
|Cards only<br />
|Yes. Neutral terminology.<br />
|Yes via clunky mobile-ready web UI. No drag and drop<br />
|Free if we host it<br />
|No<br />
|Yes. Lists > Cards > checklists<br />
|[http://restya.com/board/integrations/slack Maybe via Zapier] (not evaluated, not well documented)<br />
|Yes<br />
| + Supposedly good permissions management<br />
- No Google login<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Supports checklists ==<br />
Checklists on a card can be used to enforce quality control procedures.<br />
<br />
== Can duplicate objects ==<br />
The ability to duplicate checklists, cards, lists, and/or boards is very useful for ensuring processes are followed. Sets of objects that we treat as templates can be used to document the processes.<br />
<br />
== Clear terminology ==<br />
Many task board tools are focused on agile/scrum software development methodologies. Those methodologies introduce new terms like User Story and Epic, and use terms like Task and Project in ways that are different from the way we use those terms internally. A tool which uses either our terminology or neutral terminology (e.g. boards, lists, cards, and checklists) would reduce confusion and speed/simplify adoption.<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1686Task tracking tool evaluations2016-10-10T21:52:00Z<p>DBrettle: Restya slack integration evaluated</p>
<hr />
<div>== Features ==<br />
See below for a description of the features.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only and all notifications for a Taiga project (which might contain all of our projects) go to the same channel. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| + Custom fields<br />
- Nomenclature will be confusing because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> Taiga project<br />
* Our project (led by a misnamed "task team lead") -> Taiga epic<br />
* Our task -> Taiga user story<br />
* Our checklist item -> Taiga task<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[https://github.com/mayflower/PHProjekt PHProjekt]<br />
|No<br />
|Not tested<br />
|Free<br />
|No<br />
|Yes. Infinite depth<br />
|No<br />
|Yes but see notes.<br />
| + Easy to install from GoDaddy CPanel<br />
- Project is unmaintained since 2013<br />
<br />
- Website is unreachable<br />
<br />
|-<br />
|[http://www.thebuggenie.com/ BugGenie]<br />
|Yes<br />
|Yes but ''very'' clunky. No drag/drop. Need to refresh to see changes.<br />
|Free on GoDaddy.<br />
|No.<br />
|Yes. Infinite depth. Terminology seems flexible.<br />
|Notifications only via [http://www.thebuggenie.com/addons/slack addon] (not evaluated). Notifications for different projects can be sent to different channels.<br />
|Yes<br />
|<nowiki>+ Supports swimlanes for different categories, types, or priorities.</nowiki>+ Custom task types, fields, and work flows<br />
<br />
- Sluggish UI<br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|Yes, via apps for Android and iOS<br />
|Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|Yes, though the default configuration is a bit limiting. There are [http://www.pivotaltracker.com/help/articles/tracker_and_kanban/ workarounds and add-ons] to make it more general purpose.<br />
|Yes, via apps for "alpha" Android and iOS.<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|No. <br />
|Yes. Projects > epics > user stories > tasks<br />
|[https://t199tst.slack.com/apps/A0F82E7H8-pivotal-tracker Notifications only] (not evaluated).<br />
|No<br />
|<nowiki>+ Can easily clone user stories</nowiki><br />
<br />
+ Responsive UI<br />
<br />
- Nomenclature will be confusing <br />
<br />
because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> project<br />
* Our project (led by a misnamed "task team lead") -> epic<br />
* Our task -> user story<br />
* Our checklist item -> task<br />
|-<br />
|Trello<br />
|Yes.<br />
|Yes, via apps for Android and iOS<br />
|Free<br />
|No. However there is a [https://github.com/BeIntrepid/Trello-Card-Dependencies Chrome extension that adds dependency support] (not evaluated)<br />
|Yes. Lists > cards > checklists<br />
|Not included in free plan. Must pay $9.99/user/month<br />
|No.<br />
|<nowiki>+ Can easily copy lists and cards</nowiki><br />
<br />
+ Very responsive UI on web and mobile.<br />
<br />
- Limited ability to manage permissions<br />
|-<br />
|JIRA<br />
|<br />
|<br />
|Per user pricing but might qualify for free [https://www.atlassian.com/survey/classroom-license-request.jsp classroom license] or [https://www.atlassian.com/software/views/open-source-license-request open source license].<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Kanboard<br />
|Yes.<br />
|Yes via clunky mobile-ready web UI. No drag and drop<br />
|Free if we host it ourselves. Cheap otherwise (no per-user pricing)<br />
|No<br />
|Yes. Projects > lists > tasks > subtasks<br />
|<br />
|Yes<br />
| + Can duplicate tasks<br />
|-<br />
|Wekan.io<br />
|Yes<br />
|<br />
|Free if we host it.<br />
|<br />
|Yes. Lists > Cards<br />
|<br />
|Yes<br />
| - Can't duplicate tasks<br />
- No checklists<br />
|-<br />
|Restya.com<br />
|Yes<br />
|Yes via clunky mobile-ready web UI. No drag and drop<br />
|Free if we host it<br />
|No<br />
|Yes. Lists > Cards > checklists<br />
|[http://restya.com/board/integrations/slack Maybe via Zapier] (not evaluated, not well documented)<br />
|Yes<br />
| + Can duplicate cards<br />
+ Supposedly good permissions management<br />
- Duplicating lists does not appear to be working<br />
<br />
- No Google login<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1685Task tracking tool evaluations2016-10-10T21:38:43Z<p>DBrettle: </p>
<hr />
<div>== Features ==<br />
See below for a description of the features.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only and all notifications for a Taiga project (which might contain all of our projects) go to the same channel. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| + Custom fields<br />
- Nomenclature will be confusing because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> Taiga project<br />
* Our project (led by a misnamed "task team lead") -> Taiga epic<br />
* Our task -> Taiga user story<br />
* Our checklist item -> Taiga task<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[https://github.com/mayflower/PHProjekt PHProjekt]<br />
|No<br />
|Not tested<br />
|Free<br />
|No<br />
|Yes. Infinite depth<br />
|No<br />
|Yes but see notes.<br />
| + Easy to install from GoDaddy CPanel<br />
- Project is unmaintained since 2013<br />
<br />
- Website is unreachable<br />
<br />
|-<br />
|[http://www.thebuggenie.com/ BugGenie]<br />
|Yes<br />
|Yes but ''very'' clunky. No drag/drop. Need to refresh to see changes.<br />
|Free on GoDaddy.<br />
|No.<br />
|Yes. Infinite depth. Terminology seems flexible.<br />
|Notifications only via [http://www.thebuggenie.com/addons/slack addon] (not evaluated). Notifications for different projects can be sent to different channels.<br />
|Yes<br />
|<nowiki>+ Supports swimlanes for different categories, types, or priorities.</nowiki>+ Custom task types, fields, and work flows<br />
<br />
- Sluggish UI<br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|Yes, via apps for Android and iOS<br />
|Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|Yes, though the default configuration is a bit limiting. There are [http://www.pivotaltracker.com/help/articles/tracker_and_kanban/ workarounds and add-ons] to make it more general purpose.<br />
|Yes, via apps for "alpha" Android and iOS.<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|No. <br />
|Yes. Projects > epics > user stories > tasks<br />
|[https://t199tst.slack.com/apps/A0F82E7H8-pivotal-tracker Notifications only] (not evaluated).<br />
|No<br />
|<nowiki>+ Can easily clone user stories</nowiki><br />
<br />
+ Responsive UI<br />
<br />
- Nomenclature will be confusing <br />
<br />
because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> project<br />
* Our project (led by a misnamed "task team lead") -> epic<br />
* Our task -> user story<br />
* Our checklist item -> task<br />
|-<br />
|Trello<br />
|Yes.<br />
|Yes, via apps for Android and iOS<br />
|Free<br />
|No. However there is a [https://github.com/BeIntrepid/Trello-Card-Dependencies Chrome extension that adds dependency support] (not evaluated)<br />
|Yes. Lists > cards > checklists<br />
|Not included in free plan. Must pay $9.99/user/month<br />
|No.<br />
|<nowiki>+ Can easily copy lists and cards</nowiki><br />
<br />
+ Very responsive UI on web and mobile.<br />
<br />
- Limited ability to manage permissions<br />
|-<br />
|JIRA<br />
|<br />
|<br />
|Per user pricing but might qualify for free [https://www.atlassian.com/survey/classroom-license-request.jsp classroom license] or [https://www.atlassian.com/software/views/open-source-license-request open source license].<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Kanboard<br />
|Yes.<br />
|Yes via clunky mobile-ready web UI. No drag and drop<br />
|Free if we host it ourselves. Cheap otherwise (no per-user pricing)<br />
|No<br />
|Yes. Projects > lists > tasks > subtasks<br />
|<br />
|Yes<br />
| + Can duplicate tasks<br />
|-<br />
|Wekan.io<br />
|Yes<br />
|<br />
|Free if we host it.<br />
|<br />
|Yes. Lists > Cards<br />
|<br />
|Yes<br />
| - Can't duplicate tasks<br />
- No checklists<br />
|-<br />
|Restya.com<br />
|Yes<br />
|Yes via clunky mobile-ready web UI. No drag and drop<br />
|Free if we host it<br />
|No<br />
|Yes. Lists > Cards > checklists<br />
|<br />
|Yes<br />
| + Can duplicate cards<br />
+ Supposedly good permissions management<br />
- Duplicating lists does not appear to be working<br />
<br />
- No Google login<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1684Task tracking tool evaluations2016-10-10T21:36:49Z<p>DBrettle: Evaluated Restya.com</p>
<hr />
<div>== Features ==<br />
See below for a description of the features.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only and all notifications for a Taiga project (which might contain all of our projects) go to the same channel. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| + Custom fields<br />
- Nomenclature will be confusing because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> Taiga project<br />
* Our project (led by a misnamed "task team lead") -> Taiga epic<br />
* Our task -> Taiga user story<br />
* Our checklist item -> Taiga task<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[https://github.com/mayflower/PHProjekt PHProjekt]<br />
|No<br />
|Not tested<br />
|Free<br />
|No<br />
|Yes. Infinite depth<br />
|No<br />
|Yes but see notes.<br />
| + Easy to install from GoDaddy CPanel<br />
- Project is unmaintained since 2013<br />
<br />
- Website is unreachable<br />
<br />
|-<br />
|[http://www.thebuggenie.com/ BugGenie]<br />
|Yes<br />
|Yes but ''very'' clunky. No drag/drop. Need to refresh to see changes.<br />
|Free on GoDaddy.<br />
|No.<br />
|Yes. Infinite depth. Terminology seems flexible.<br />
|Notifications only via [http://www.thebuggenie.com/addons/slack addon] (not evaluated). Notifications for different projects can be sent to different channels.<br />
|Yes<br />
|<nowiki>+ Supports swimlanes for different categories, types, or priorities.</nowiki>+ Custom task types, fields, and work flows<br />
<br />
- Sluggish UI<br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|Yes, via apps for Android and iOS<br />
|Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|Yes, though the default configuration is a bit limiting. There are [http://www.pivotaltracker.com/help/articles/tracker_and_kanban/ workarounds and add-ons] to make it more general purpose.<br />
|Yes, via apps for "alpha" Android and iOS.<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|No. <br />
|Yes. Projects > epics > user stories > tasks<br />
|[https://t199tst.slack.com/apps/A0F82E7H8-pivotal-tracker Notifications only] (not evaluated).<br />
|No<br />
|<nowiki>+ Can easily clone user stories</nowiki><br />
<br />
+ Responsive UI<br />
<br />
- Nomenclature will be confusing <br />
<br />
because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> project<br />
* Our project (led by a misnamed "task team lead") -> epic<br />
* Our task -> user story<br />
* Our checklist item -> task<br />
|-<br />
|Trello<br />
|Yes.<br />
|Yes, via apps for Android and iOS<br />
|Free<br />
|No. However there is a [https://github.com/BeIntrepid/Trello-Card-Dependencies Chrome extension that adds dependency support] (not evaluated)<br />
|Yes. Lists > cards > checklists<br />
|Not included in free plan. Must pay $9.99/user/month<br />
|No.<br />
|<nowiki>+ Can easily copy lists and cards</nowiki><br />
<br />
+ Very responsive UI on web and mobile.<br />
<br />
- Limited ability to manage permissions<br />
|-<br />
|JIRA<br />
|<br />
|<br />
|Per user pricing but might qualify for free [https://www.atlassian.com/survey/classroom-license-request.jsp classroom license] or [https://www.atlassian.com/software/views/open-source-license-request open source license].<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Kanboard<br />
|Yes.<br />
|Yes via clunky mobile-ready web UI. No drag and drop<br />
|Free if we host it ourselves. Cheap otherwise (no per-user pricing)<br />
|No<br />
|Yes. Projects > lists > tasks > subtasks<br />
|<br />
|Yes<br />
| + Can duplicate tasks<br />
|-<br />
|Wekan.io<br />
|Yes<br />
|<br />
|Free if we host it.<br />
|<br />
|Yes. Lists > Cards<br />
|<br />
|Yes<br />
| - Can't duplicate tasks<br />
- No checklists<br />
|-<br />
|Restya.com<br />
|Yes<br />
|Yes via clunky mobile-ready web UI. No drag and drop<br />
|Free if we host it<br />
|No<br />
|Yes. Lists > Cards > checklists<br />
|<br />
|Yes<br />
| + Can duplicate cards<br />
- Duplicating lists does not appear to be working<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1683Task tracking tool evaluations2016-10-10T20:24:40Z<p>DBrettle: Added initial evaluations of Kanboard and Wekan.io</p>
<hr />
<div>== Features ==<br />
See below for a description of the features.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only and all notifications for a Taiga project (which might contain all of our projects) go to the same channel. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| + Custom fields<br />
- Nomenclature will be confusing because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> Taiga project<br />
* Our project (led by a misnamed "task team lead") -> Taiga epic<br />
* Our task -> Taiga user story<br />
* Our checklist item -> Taiga task<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[https://github.com/mayflower/PHProjekt PHProjekt]<br />
|No<br />
|Not tested<br />
|Free<br />
|No<br />
|Yes. Infinite depth<br />
|No<br />
|Yes but see notes.<br />
| + Easy to install from GoDaddy CPanel<br />
- Project is unmaintained since 2013<br />
<br />
- Website is unreachable<br />
<br />
|-<br />
|[http://www.thebuggenie.com/ BugGenie]<br />
|Yes<br />
|Yes but ''very'' clunky. No drag/drop. Need to refresh to see changes.<br />
|Free on GoDaddy.<br />
|No.<br />
|Yes. Infinite depth. Terminology seems flexible.<br />
|Notifications only via [http://www.thebuggenie.com/addons/slack addon] (not evaluated). Notifications for different projects can be sent to different channels.<br />
|Yes<br />
|<nowiki>+ Supports swimlanes for different categories, types, or priorities.</nowiki>+ Custom task types, fields, and work flows<br />
<br />
- Sluggish UI<br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|Yes, via apps for Android and iOS<br />
|Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|Yes, though the default configuration is a bit limiting. There are [http://www.pivotaltracker.com/help/articles/tracker_and_kanban/ workarounds and add-ons] to make it more general purpose.<br />
|Yes, via apps for "alpha" Android and iOS.<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|No. <br />
|Yes. Projects > epics > user stories > tasks<br />
|[https://t199tst.slack.com/apps/A0F82E7H8-pivotal-tracker Notifications only] (not evaluated).<br />
|No<br />
|<nowiki>+ Can easily clone user stories</nowiki><br />
<br />
+ Responsive UI<br />
<br />
- Nomenclature will be confusing <br />
<br />
because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> project<br />
* Our project (led by a misnamed "task team lead") -> epic<br />
* Our task -> user story<br />
* Our checklist item -> task<br />
|-<br />
|Trello<br />
|Yes.<br />
|Yes, via apps for Android and iOS<br />
|Free<br />
|No. However there is a [https://github.com/BeIntrepid/Trello-Card-Dependencies Chrome extension that adds dependency support] (not evaluated)<br />
|Yes. Lists > cards > checklists<br />
|Not included in free plan. Must pay $9.99/user/month<br />
|No.<br />
|<nowiki>+ Can easily copy lists and cards</nowiki><br />
<br />
+ Very responsive UI on web and mobile.<br />
<br />
- Limited ability to manage permissions<br />
|-<br />
|JIRA<br />
|<br />
|<br />
|Per user pricing but might qualify for free [https://www.atlassian.com/survey/classroom-license-request.jsp classroom license] or [https://www.atlassian.com/software/views/open-source-license-request open source license].<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Kanboard<br />
|Yes.<br />
|Yes via clunky mobile-ready web UI. No drag and drop<br />
|Free if we host it ourselves. Cheap otherwise (no per-user pricing)<br />
|No<br />
|Yes. Projects > lists > tasks > subtasks<br />
|<br />
|Yes<br />
| + Can duplicate tasks<br />
|-<br />
|Wekan.io<br />
|Yes<br />
|<br />
|Free if we host it.<br />
|<br />
|Yes. Lists > Cards<br />
|<br />
|Yes<br />
| - Can't duplicate tasks<br />
- No checklists<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1682Task tracking tool evaluations2016-10-10T18:07:51Z<p>DBrettle: Evaluated Trello</p>
<hr />
<div>== Features ==<br />
See below for a description of the features.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only and all notifications for a Taiga project (which might contain all of our projects) go to the same channel. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| + Custom fields<br />
- Nomenclature will be confusing because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> Taiga project<br />
* Our project (led by a misnamed "task team lead") -> Taiga epic<br />
* Our task -> Taiga user story<br />
* Our checklist item -> Taiga task<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[https://github.com/mayflower/PHProjekt PHProjekt]<br />
|No<br />
|Not tested<br />
|Free<br />
|No<br />
|Yes. Infinite depth<br />
|No<br />
|Yes but see notes.<br />
| + Easy to install from GoDaddy CPanel<br />
- Project is unmaintained since 2013<br />
<br />
- Website is unreachable<br />
<br />
|-<br />
|[http://www.thebuggenie.com/ BugGenie]<br />
|Yes<br />
|Yes but ''very'' clunky. No drag/drop. Need to refresh to see changes.<br />
|Free on GoDaddy.<br />
|No.<br />
|Yes. Infinite depth. Terminology seems flexible.<br />
|Notifications only via [http://www.thebuggenie.com/addons/slack addon] (not evaluated). Notifications for different projects can be sent to different channels.<br />
|Yes<br />
|<nowiki>+ Supports swimlanes for different categories, types, or priorities.</nowiki>+ Custom task types, fields, and work flows<br />
<br />
- Sluggish UI<br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|Yes, via apps for Android and iOS<br />
|Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|Yes, though the default configuration is a bit limiting. There are [http://www.pivotaltracker.com/help/articles/tracker_and_kanban/ workarounds and add-ons] to make it more general purpose.<br />
|Yes, via apps for "alpha" Android and iOS.<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|No. <br />
|Yes. Projects > epics > user stories > tasks<br />
|[https://t199tst.slack.com/apps/A0F82E7H8-pivotal-tracker Notifications only] (not evaluated).<br />
|No<br />
|<nowiki>+ Can easily clone user stories</nowiki><br />
<br />
+ Responsive UI<br />
<br />
- Nomenclature will be confusing <br />
<br />
because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> project<br />
* Our project (led by a misnamed "task team lead") -> epic<br />
* Our task -> user story<br />
* Our checklist item -> task<br />
|-<br />
|Trello<br />
|Yes.<br />
|Yes, via apps for Android and iOS<br />
|Free<br />
|No. However there is a [https://github.com/BeIntrepid/Trello-Card-Dependencies Chrome extension that adds dependency support] (not evaluated)<br />
|Yes. Lists > cards > checklists<br />
|Not included in free plan. Must pay $9.99/user/month<br />
|No.<br />
|<nowiki>+ Can easily copy lists and cards</nowiki><br />
<br />
+ Very responsive UI on web and mobile.<br />
<br />
- Limited ability to manage permissions<br />
|-<br />
|JIRA<br />
|<br />
|<br />
|Per user pricing but might qualify for free [https://www.atlassian.com/survey/classroom-license-request.jsp classroom license] or [https://www.atlassian.com/software/views/open-source-license-request open source license].<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1681Task tracking tool evaluations2016-10-10T17:12:47Z<p>DBrettle: Started evaluating Trello and JIRA</p>
<hr />
<div>== Features ==<br />
See below for a description of the features.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only and all notifications for a Taiga project (which might contain all of our projects) go to the same channel. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| + Custom fields<br />
- Nomenclature will be confusing because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> Taiga project<br />
* Our project (led by a misnamed "task team lead") -> Taiga epic<br />
* Our task -> Taiga user story<br />
* Our checklist item -> Taiga task<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[https://github.com/mayflower/PHProjekt PHProjekt]<br />
|No<br />
|Not tested<br />
|Free<br />
|No<br />
|Yes. Infinite depth<br />
|No<br />
|Yes but see notes.<br />
| + Easy to install from GoDaddy CPanel<br />
- Project is unmaintained since 2013<br />
<br />
- Website is unreachable<br />
<br />
|-<br />
|[http://www.thebuggenie.com/ BugGenie]<br />
|Yes<br />
|Yes but ''very'' clunky. No drag/drop. Need to refresh to see changes.<br />
|Free on GoDaddy.<br />
|No.<br />
|Yes. Infinite depth. Terminology seems flexible.<br />
|Notifications only via [http://www.thebuggenie.com/addons/slack addon] (not evaluated). Notifications for different projects can be sent to different channels.<br />
|Yes<br />
|<nowiki>+ Supports swimlanes for different categories, types, or priorities.</nowiki>+ Custom task types, fields, and work flows<br />
<br />
- Sluggish UI<br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|Yes, via apps for Android and iOS<br />
|Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|Yes, though the default configuration is a bit limiting. There are [http://www.pivotaltracker.com/help/articles/tracker_and_kanban/ workarounds and add-ons] to make it more general purpose.<br />
|Yes, via apps for "alpha" Android and iOS.<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|No. <br />
|Yes. Projects > epics > user stories > tasks<br />
|[https://t199tst.slack.com/apps/A0F82E7H8-pivotal-tracker Notifications only] (not evaluated).<br />
|No<br />
|<nowiki>+ Can easily clone user stories</nowiki><br />
<br />
+ Responsive UI<br />
<br />
- Nomenclature will be confusing <br />
<br />
because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> project<br />
* Our project (led by a misnamed "task team lead") -> epic<br />
* Our task -> user story<br />
* Our checklist item -> task<br />
|-<br />
|Trello<br />
|Yes.<br />
|Yes, via apps for Android and iOS<br />
|Free<br />
|<br />
|<br />
|Not included in free plan. Must pay $9.99/user/month<br />
|No.<br />
|<br />
|-<br />
|JIRA<br />
|<br />
|<br />
|Per user pricing but might qualify for free [https://www.atlassian.com/survey/classroom-license-request.jsp classroom license] or [https://www.atlassian.com/software/views/open-source-license-request open source license].<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1680Task tracking tool evaluations2016-10-10T16:54:59Z<p>DBrettle: Clarified situation with Pivotal task board.</p>
<hr />
<div>== Features ==<br />
See below for a description of the features.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only and all notifications for a Taiga project (which might contain all of our projects) go to the same channel. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| + Custom fields<br />
- Nomenclature will be confusing because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> Taiga project<br />
* Our project (led by a misnamed "task team lead") -> Taiga epic<br />
* Our task -> Taiga user story<br />
* Our checklist item -> Taiga task<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[https://github.com/mayflower/PHProjekt PHProjekt]<br />
|No<br />
|Not tested<br />
|Free<br />
|No<br />
|Yes. Infinite depth<br />
|No<br />
|Yes but see notes.<br />
| + Easy to install from GoDaddy CPanel<br />
- Project is unmaintained since 2013<br />
<br />
- Website is unreachable<br />
<br />
|-<br />
|[http://www.thebuggenie.com/ BugGenie]<br />
|Yes<br />
|Yes but ''very'' clunky. No drag/drop. Need to refresh to see changes.<br />
|Free on GoDaddy.<br />
|No.<br />
|Yes. Infinite depth. Terminology seems flexible.<br />
|Notifications only via [http://www.thebuggenie.com/addons/slack addon] (not evaluated). Notifications for different projects can be sent to different channels.<br />
|Yes<br />
|<nowiki>+ Supports swimlanes for different categories, types, or priorities.</nowiki>+ Custom task types, fields, and work flows<br />
<br />
- Sluggish UI<br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|Yes, via apps for Android and iOS<br />
|Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|Yes, though the default configuration is a bit limiting. There are [http://www.pivotaltracker.com/help/articles/tracker_and_kanban/ workarounds and add-ons] to make it more general purpose.<br />
|Yes, via apps for "alpha" Android and iOS.<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|No. <br />
|Yes. Projects > epics > user stories > tasks<br />
|[https://t199tst.slack.com/apps/A0F82E7H8-pivotal-tracker Notifications only] (not evaluated).<br />
|No<br />
|<nowiki>+ Can easily clone user stories</nowiki><br />
<br />
+ Responsive UI<br />
<br />
- Nomenclature will be confusing <br />
<br />
because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> project<br />
* Our project (led by a misnamed "task team lead") -> epic<br />
* Our task -> user story<br />
* Our checklist item -> task<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1679Task tracking tool evaluations2016-10-10T16:16:46Z<p>DBrettle: PivotalTracker evaluation</p>
<hr />
<div>== Features ==<br />
See below for a description of the features.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only and all notifications for a Taiga project (which might contain all of our projects) go to the same channel. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| + Custom fields<br />
- Nomenclature will be confusing because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> Taiga project<br />
* Our project (led by a misnamed "task team lead") -> Taiga epic<br />
* Our task -> Taiga user story<br />
* Our checklist item -> Taiga task<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[https://github.com/mayflower/PHProjekt PHProjekt]<br />
|No<br />
|Not tested<br />
|Free<br />
|No<br />
|Yes. Infinite depth<br />
|No<br />
|Yes but see notes.<br />
| + Easy to install from GoDaddy CPanel<br />
- Project is unmaintained since 2013<br />
<br />
- Website is unreachable<br />
<br />
|-<br />
|[http://www.thebuggenie.com/ BugGenie]<br />
|Yes<br />
|Yes but ''very'' clunky. No drag/drop. Need to refresh to see changes.<br />
|Free on GoDaddy.<br />
|No.<br />
|Yes. Infinite depth. Terminology seems flexible.<br />
|Notifications only via [http://www.thebuggenie.com/addons/slack addon] (not evaluated). Notifications for different projects can be sent to different channels.<br />
|Yes<br />
|<nowiki>+ Supports swimlanes for different categories, types, or priorities.</nowiki>+ Custom task types, fields, and work flows<br />
<br />
- Sluggish UI<br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|Yes, via apps for Android and iOS<br />
|Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|Yes.<br />
|Yes, via apps for "alpha" Android and iOS.<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|No. <br />
|Yes. Projects > epics > user stories > tasks<br />
|[https://t199tst.slack.com/apps/A0F82E7H8-pivotal-tracker Notifications only] (not evaluated).<br />
|No<br />
|<nowiki>+ Can easily clone user stories</nowiki><br />
<br />
+ Responsive UI<br />
<br />
- Nomenclature will be confusing <br />
<br />
because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> project<br />
* Our project (led by a misnamed "task team lead") -> epic<br />
* Our task -> user story<br />
* Our checklist item -> task<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1678Task tracking tool evaluations2016-10-10T05:03:42Z<p>DBrettle: </p>
<hr />
<div>== Features ==<br />
See below for a description of the features.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only and all notifications for a Taiga project (which might contain all of our projects) go to the same channel. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| + Custom fields<br />
- Nomenclature will be confusing because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> Taiga project<br />
* Our project (led by a misnamed "task team lead") -> Taiga epic<br />
* Our task -> Taiga user story<br />
* Our checklist item -> Taiga task<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[https://github.com/mayflower/PHProjekt PHProjekt]<br />
|No<br />
|Not tested<br />
|Free<br />
|No<br />
|Yes. Infinite depth<br />
|No<br />
|Yes but see notes.<br />
| + Easy to install from GoDaddy CPanel<br />
- Project is unmaintained since 2013<br />
<br />
- Website is unreachable<br />
<br />
|-<br />
|[http://www.thebuggenie.com/ BugGenie]<br />
|Yes<br />
|Yes but ''very'' clunky. No drag/drop. Need to refresh to see changes.<br />
|Free on GoDaddy.<br />
|No.<br />
|Yes. Infinite depth. Terminology seems flexible.<br />
|Notifications only via [http://www.thebuggenie.com/addons/slack addon] (not evaluated). Notifications for different projects can be sent to different channels.<br />
|Yes<br />
|<nowiki>+ Supports swimlanes for different categories, types, or priorities.</nowiki>+ Custom task types, fields, and work flows<br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|Yes, via apps for Android and iOS<br />
|Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|<br />
|<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1677Task tracking tool evaluations2016-10-10T04:45:11Z<p>DBrettle: Eliminate difference between BugGenie Enterprise and Open Source because the functionality appears to be the same despite what the website says.</p>
<hr />
<div>== Features ==<br />
See below for a description of the features.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only and all notifications for a Taiga project (which might contain all of our projects) go to the same channel. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| - Nomenclature will be confusing because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> Taiga project<br />
* Our project (led by a misnamed "task team lead") -> Taiga epic<br />
* Our task -> Taiga user story<br />
* Our checklist item -> Taiga task<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[https://github.com/mayflower/PHProjekt PHProjekt]<br />
|No<br />
|Not tested<br />
|Free<br />
|No<br />
|Yes. Infinite depth<br />
|No<br />
|Yes but see notes.<br />
| + Easy to install from GoDaddy CPanel<br />
- Project is unmaintained since 2013<br />
<br />
- Website is unreachable<br />
<br />
|-<br />
|[http://www.thebuggenie.com/ BugGenie]<br />
|Yes<br />
|Yes but ''very'' clunky. No drag/drop. Need to refresh to see changes.<br />
|Free on GoDaddy.<br />
|No.<br />
|Yes. Infinite depth. Terminology seems flexible.<br />
|Notifications only via [http://www.thebuggenie.com/addons/slack addon] (not evaluated). Notifications for different projects can be sent to different channels.<br />
|Yes<br />
|<nowiki>+ Supports swimlanes for different categories, types, or priorities.</nowiki><br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|Yes, via apps for Android and iOS<br />
|Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|<br />
|<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1676Task tracking tool evaluations2016-10-09T21:42:55Z<p>DBrettle: More BugGenie Enterprise evaluation</p>
<hr />
<div>== Features ==<br />
See below for a description of the features.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only and all notifications for a Taiga project (which might contain all of our projects) go to the same channel. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| - Nomenclature will be confusing because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> Taiga project<br />
* Our project (led by a misnamed "task team lead") -> Taiga epic<br />
* Our task -> Taiga user story<br />
* Our checklist item -> Taiga task<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[https://github.com/mayflower/PHProjekt PHProjekt]<br />
|No<br />
|Not tested<br />
|Free<br />
|No<br />
|Yes. Infinite depth<br />
|No<br />
|Yes but see notes.<br />
| + Easy to install from GoDaddy CPanel<br />
- Project is unmaintained since 2013<br />
<br />
- Website is unreachable<br />
<br />
|-<br />
|[http://www.thebuggenie.com/ BugGenie Enterprise]<br />
|Yes<br />
|Yes but ''very'' clunky. No drag/drop. Need to refresh to see changes.<br />
|Free hosting for open source projects. Would need to apply.<br />
|No.<br />
|Yes. Infinite depth. Terminology seems flexible.<br />
|Notifications only via [http://www.thebuggenie.com/addons/slack addon] (not evaluated). Notifications for different projects can be sent to different channels.<br />
|No<br />
|<nowiki>+ Supports swimlanes for different categories, types, or priorities.</nowiki><br />
|-<br />
|[http://www.thebuggenie.org/ BugGenie Open Source]<br />
|No<br />
|No<br />
|Free<br />
|<br />
|<br />
|Notifications only via [http://www.thebuggenie.com/addons/slack addon] (not evaluated). Notifications for different projects can be sent to different channels.<br />
|Yes<br />
|<nowiki>+ Easy to install from GoDaddy CPanel</nowiki><br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|Yes, via apps for Android and iOS<br />
|Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|<br />
|<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1675Task tracking tool evaluations2016-10-09T20:50:19Z<p>DBrettle: Continued BugGenie Enterprise evaluation.</p>
<hr />
<div>== Features ==<br />
See below for a description of the features.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only and all notifications for a Taiga project (which might contain all of our projects) go to the same channel. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| - Nomenclature will be confusing because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> Taiga project<br />
* Our project (led by a misnamed "task team lead") -> Taiga epic<br />
* Our task -> Taiga user story<br />
* Our checklist item -> Taiga task<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[https://github.com/mayflower/PHProjekt PHProjekt]<br />
|No<br />
|Not tested<br />
|Free<br />
|No<br />
|Yes. Infinite depth<br />
|No<br />
|Yes but see notes.<br />
| + Easy to install from GoDaddy CPanel<br />
- Project is unmaintained since 2013<br />
<br />
- Website is unreachable<br />
<br />
|-<br />
|[http://www.thebuggenie.com/ BugGenie Enterprise]<br />
|Yes<br />
|Yes via preview release of [http://www.thebuggenie.com/addons/mobile addon] (not evaluated)<br />
|Free hosting for open source projects. Would need to apply.<br />
|<br />
|Yes. Terminology seems flexible.<br />
|Notifications only via [http://www.thebuggenie.com/addons/slack addon] (not evaluated). Notifications for different projects can be sent to different channels.<br />
|No<br />
|<br />
|-<br />
|[http://www.thebuggenie.org/ BugGenie Open Source]<br />
|No<br />
|No<br />
|Free<br />
|<br />
|<br />
|Notifications only via [http://www.thebuggenie.com/addons/slack addon] (not evaluated). Notifications for different projects can be sent to different channels.<br />
|Yes<br />
|<nowiki>+ Easy to install from GoDaddy CPanel</nowiki><br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|Yes, via apps for Android and iOS<br />
|Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|<br />
|<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1674Task tracking tool evaluations2016-10-09T07:02:16Z<p>DBrettle: Started BugGenie evaluation</p>
<hr />
<div>== Features ==<br />
See below for a description of the features.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only and all notifications for a Taiga project (which might contain all of our projects) go to the same channel. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| - Nomenclature will be confusing because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> Taiga project<br />
* Our project (led by a misnamed "task team lead") -> Taiga epic<br />
* Our task -> Taiga user story<br />
* Our checklist item -> Taiga task<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[https://github.com/mayflower/PHProjekt PHProjekt]<br />
|No<br />
|Not tested<br />
|Free<br />
|No<br />
|Yes. Infinite depth<br />
|No<br />
|Yes but see notes.<br />
| + Easy to install from GoDaddy CPanel<br />
- Project is unmaintained since 2013<br />
<br />
- Website is unreachable<br />
<br />
|-<br />
|BugGenie<br />
|<br />
|Yes via preview release of [http://www.thebuggenie.com/addons/mobile addon] (not evaluated)<br />
|Free<br />
|<br />
|<br />
|Notifications only via [http://www.thebuggenie.com/addons/slack addon] (not evaluated). Notifications for different projects can be sent to different channels.<br />
|Yes<br />
|<nowiki>+ Easy to install from GoDaddy CPanel</nowiki><br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|Yes, via apps for Android and iOS<br />
|No. Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|<br />
|<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1673Task tracking tool evaluations2016-10-09T06:47:20Z<p>DBrettle: Evaluated PHProjekt</p>
<hr />
<div>== Features ==<br />
See below for a description of the features.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| - Nomenclature will be confusing because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> Taiga project<br />
* Our project (led by a misnamed "task team lead") -> Taiga epic<br />
* Our task -> Taiga user story<br />
* Our checklist item -> Taiga task<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[https://github.com/mayflower/PHProjekt PHProjekt]<br />
|No<br />
|Not tested<br />
|Free<br />
|No<br />
|Yes. Infinite depth<br />
|No<br />
|Yes but see notes.<br />
| + Easy to install from GoDaddy CPanel<br />
- Project is unmaintained since 2013<br />
<br />
- Website is unreachable<br />
<br />
|-<br />
|BugGenie<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|Yes, via apps for Android and iOS<br />
|No. Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|<br />
|<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1672Task tracking tool evaluations2016-10-09T05:12:30Z<p>DBrettle: </p>
<hr />
<div>== Features ==<br />
See below for a description of the features.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| - Nomenclature will be confusing because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> Taiga project<br />
* Our project (led by a misnamed "task team lead") -> Taiga epic<br />
* Our task -> Taiga user story<br />
* Our checklist item -> Taiga task<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PHProjekt<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|BugGenie<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|Yes, via apps for Android and iOS<br />
|No. Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|<br />
|<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1671Task tracking tool evaluations2016-10-09T05:11:44Z<p>DBrettle: Finished Taiga.io evaluation and most of Asana evaluation</p>
<hr />
<div>See below for a description of the criteria.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Slack channel > task<br />
|Notifications and task creation, modification, etc.<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. projects > epics > user stories > tasks.<br />
|Notifications only. There are well documented APIs for both Slack and Taiga, so we could conceivably roll our own better Slack integration.<br />
|Yes<br />
| - Nomenclature will be confusing because user stories are what are displayed on the kanban board. Terminology translation:<br />
* Our year -> Taiga project<br />
* Our project (led by a misnamed "task team lead") -> Taiga epic<br />
* Our task -> Taiga user story<br />
* Our checklist item -> Taiga task<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PHProjekt<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|BugGenie<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Asana<br />
|No. Though [http://www.asanban.com/ Asanban] supposedly provides one.<br />
|Yes, via apps for Android and iOS<br />
|No. Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|No.<br />
|Yes. Projects > sections > tasks > subtasks<br />
|<br />
|No.<br />
| + Already being used for many business tasks<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|<br />
|<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1670Task tracking tool evaluations2016-10-09T02:58:14Z<p>DBrettle: Start of Taiga.io evaluation</p>
<hr />
<div>See below for a description of the criteria.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Via slack channels.<br />
|Yes<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|Yes<br />
|Yes. Mobile-ready web interface. Dragging cards is a bit slow.<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|No<br />
|Yes. Epics contain user stories and user stories can contain subtasks.<br />
|<br />
|Yes<br />
| - Nomenclature may be confusing.<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PHProjekt<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|BugGenie<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Asana<br />
|<br />
|<br />
|No. Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|<br />
|<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1669Task tracking tool evaluations2016-10-09T02:54:22Z<p>DBrettle: Added Kyber notes.</p>
<hr />
<div>See below for a description of the criteria.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Via slack channels.<br />
|Yes<br />
|No<br />
|<nowiki>+ You can easily see tasks you've assigned to others and click a "Follow Up" button to request a status update.</nowiki><br />
<br />
+ Integration with calendars (not evaluated)<br />
<br />
+ Automation possibilities with [https://IFTTT.com IFTTT] (not evaluated)<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|<br />
|<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PHProjekt<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|BugGenie<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Asana<br />
|<br />
|<br />
|No. Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|<br />
|<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1668Task tracking tool evaluations2016-10-09T02:47:53Z<p>DBrettle: </p>
<hr />
<div>See below for a description of the criteria.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
!Other Notes<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Via slack channels.<br />
|Yes<br />
|No<br />
|<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|<br />
|<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PHProjekt<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|BugGenie<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Asana<br />
|<br />
|<br />
|No. Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|<br />
|<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1667Task tracking tool evaluations2016-10-09T02:47:08Z<p>DBrettle: Add links to criteria descriptions</p>
<hr />
<div>See below for a description of the criteria.<br />
{| class="wikitable"<br />
!Tool<br />
![[#Task_board|Task board]]<br />
![[#Mobile Support|Mobile support]]<br />
![[#Cost|Cost]]<br />
![[#Task_Dependencies|Task dependencies]]<br />
![[#Task_Groups|Task groups]]<br />
![[#Slack_Integration|Slack integration]]<br />
![[#Open_Source|Open source]]<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Via slack channels.<br />
|Yes<br />
|No<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|<br />
|<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PHProjekt<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|BugGenie<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Asana<br />
|<br />
|<br />
|No. Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|<br />
|<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open Source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1666Task tracking tool evaluations2016-10-09T02:41:47Z<p>DBrettle: </p>
<hr />
<div>See below for a description of the criteria.<br />
{| class="wikitable"<br />
!Tool<br />
![[Task tracking tool evaluations|Task board]]<br />
!Mobile support<br />
!Cost<br />
!Task dependencies<br />
!Task groups<br />
!Slack integration<br />
!Open source<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Via slack channels.<br />
|Yes<br />
|No<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|<br />
|<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PHProjekt<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|BugGenie<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Asana<br />
|<br />
|<br />
|No. Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|<br />
|<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1665Task tracking tool evaluations2016-10-09T02:34:34Z<p>DBrettle: </p>
<hr />
<div>{| class="wikitable"<br />
!Tool<br />
![[Task tracking tool evaluations|Task board]]<br />
!Mobile support<br />
!Cost<br />
!Task dependencies<br />
!Task groups<br />
!Slack integration<br />
!Open source<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Via slack channels.<br />
|Yes<br />
|No<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|<br />
|<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PHProjekt<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|BugGenie<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Asana<br />
|<br />
|<br />
|No. Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|<br />
|<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1664Task tracking tool evaluations2016-10-09T00:31:09Z<p>DBrettle: </p>
<hr />
<div>== Evaluation Matrix ==<br />
See below for a description of the criteria in each column.<br />
{| class="wikitable"<br />
!Tool<br />
!Task board<br />
!Mobile support<br />
!Cost<br />
!Task dependencies<br />
!Task groups<br />
!Slack integration<br />
!Open source<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Via slack channels.<br />
|Yes<br />
|No<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|<br />
|<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PHProjekt<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|BugGenie<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Asana<br />
|<br />
|<br />
|No. Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|<br />
|<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1663Task tracking tool evaluations2016-10-09T00:22:29Z<p>DBrettle: Added descriptions of criteria</p>
<hr />
<div>{| class="wikitable"<br />
!Tool<br />
!Task board<br />
!Mobile support<br />
!Cost<br />
!Task dependencies<br />
!Task groups<br />
!Slack integration<br />
!Open source<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Via slack channels.<br />
|Yes<br />
|No<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|<br />
|<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PHProjekt<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|BugGenie<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Asana<br />
|<br />
|<br />
|No. Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|<br />
|<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Task board ==<br />
The tool should provide a single view (sometimes called a task board, a WIP board (work in progress board), or a [https://en.wikipedia.org/wiki/Kanban_board kanban board]) for the entire team to visualize the state of all tasks. At a minimum there are columns for tasks in each of the following states: to do, in progress, done. Ideally, the tool provides a way to add columns corresponding to states like "blocked" or "under review".<br />
<br />
== Mobile Support ==<br />
It should be easy for a user to use a smart phone to select a task to work on and change the state of task. Ideally the user can also use a smartphone to add/change information associated with the task (e.g. add comments, change the task description, etc).<br />
<br />
== Cost ==<br />
Should cost less than $500/year to use. Many task tracking tools are priced on a per-user basis. With over 50 potential users, even a price of $1/user/month is too expensive, and all tools with per-user pricing that I've seen are more expensive than that. Some tools are free for public projects which should work for us. Some tools offer discounts or are free for academic institutions or non-profits. These might be worth investigating, but given the time-critical nature of getting a tool in place, we might not be able to get approved for such treatment soon enough for it to be useful.<br />
<br />
== Task Dependencies ==<br />
Ideally, there should be a way to indicated that one task can not start until another one is complete, and such a dependency should be made visible and should prevent users from choosing a task which is blocked for that reason.<br />
<br />
== Task Groups ==<br />
The tool should allow tasks to be grouped so that we can distinguish between tasks associated with different projects. The groups might be called projects, epics, or they might go by some other name.<br />
<br />
The tool should also allow tasks to at least have basic checklist-style subtasks to assist with implement quality control procedures.<br />
<br />
== Slack Integration ==<br />
The tool should have a way to notify relevant users via slack when the state of a task changes or new tasks are created.<br />
<br />
Ideally, the tool should also allow the user to use slack to change the state of a task so that they don't have to switch apps as often.<br />
<br />
== Open source ==<br />
The goal here is just to avoid vendor lock-in. If the tool is proprietary the pricing or availability of the tool might change in the future in a way that would prevent us from continuing to use the tool and we might also lose access to any data in it. If it's open source we will at least be able to host it ourselves if necessary and, at least theoretically, recover any critical data in some form.</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1662Task tracking tool evaluations2016-10-08T23:32:45Z<p>DBrettle: Initial matrix</p>
<hr />
<div>{| class="wikitable"<br />
!Tool<br />
!Task board<br />
!Mobile support<br />
!Cost<br />
!Task dependencies<br />
!Task groups<br />
!Slack integration<br />
!Open source<br />
|-<br />
|[https://Kyber.me Kyber.me]<br />
|No<br />
|Yes<br />
|Free<br />
|No<br />
|Yes. Via slack channels.<br />
|Yes<br />
|No<br />
|-<br />
|[https://taiga.io Taiga.io]<br />
|<br />
|<br />
|[https://taiga.io/#pricing Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Drupal's PM plugin<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PHProjekt<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|BugGenie<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Asana<br />
|<br />
|<br />
|No. Per user pricing. Declined to allow us to use the [https://asana.com/students Asana for Students] program.<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|Teamweek<br />
|<br />
|<br />
|Would need to [https://support.teamweek.com/pricing/#largeteams investigate non-profit discount]<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|PivotalTracker<br />
|<br />
|<br />
|[http://www.pivotaltracker.com/help/articles/other_free_options/#free_plan_limits Free for public projects]<br />
|<br />
|<br />
|<br />
|<br />
|}</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Task_tracking_tool_evaluations&diff=1661Task tracking tool evaluations2016-10-08T21:57:46Z<p>DBrettle: Created page with "{| class="wikitable" ! ! ! ! |- | | | | |- | | | | |- | | | | |}"</p>
<hr />
<div>{| class="wikitable"<br />
!<br />
!<br />
!<br />
!<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|}</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Information_Technology&diff=1660Information Technology2016-10-08T21:55:25Z<p>DBrettle: </p>
<hr />
<div><br />
[[Adding_extensions_to_the_wiki|Adding extensions to the wiki]]<br />
<br />
[[Task tracking tool evaluations]]</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Main_Page&diff=1658Main Page2016-10-08T06:48:12Z<p>DBrettle: </p>
<hr />
<div><br />
[[File:2016Logo.png|thumb|right|Team 199's Current Brand Logo]]'''Team 199: Deep Blue Robotics''' was created to support Carlmont High School Students and allow them to continue their in-depth STEM education.<br />
<br />
In 2003, students at Carlmont High School in Belmont, CA joined forces with Woodside High School’s FRC Team 100, pooling resources to build a competitive strong robotics team. However, in 2015, Woodside's program was so successful that it was suggested we create a second team at Carlmont, therefore reverting the team back to its original 1995 configuration.<br />
<br />
Many Carlmont students from Team 100 wanted a way to continue their involvement in a strong FRC team, and opted to create their own program. The students currently on Team 199 are highly motivated, and have worked hard to quickly build an incredible FRC team from scratch. The students of Carlmont High School currently face the challenge of creating a shop with limited funding, as Carlmont’s administration has indicated that it cannot supply the team with any funds. Therefore, we are actively searching for corporate sponsors and personal donors. As well as securing funding, we are also searching for team mentors to teach and guide the students of the team as they tackle the challenges inherent in building a complex robot in just six weeks.<br />
<br />
Our mission statement: The mission of the Carlmont Robotics FRC team is to provide an opportunity for students to learn engineering, project management, and community relations skills in an environment that is fun, yet competitive and challenging at times in order to simulate real world situations and prepare our students for real-world projects.<br />
<br />
== Team History ==<br />
<br />
From January 2016 to Feburary 2016, Team 199 participated in the FIRST FRC 2016 Season, in which teams all across the US and around the world had six weeks to build a robot for the 2016 game, [[FIRST_Stronghold|FIRST Stronghold]]. Team 199 competed at Silicon Valley Regional.<br />
<br />
Prior to 2015, Carlmont students share history with Team 100, a team based out of Woodside High School. For information on their robots and history, please see [http://team100.org Team 100's web site].<br />
<br />
== Stay Informed ==<br />
<br />
Use the [[Team_Dashboard|Team Dashboard]] to see what is currently going on and what's on the horizon.<br />
<br />
== Find Help ==<br />
<br />
Use the [[Mentor_Directory|Mentor Directory]] to find a mentor to help you.<br />
<br />
== Knowledge Base ==<br />
<br />
[[Information_Technology|Information Technology]] - Information about managing the website, this wiki, project management tools, classroom computers and other IT tools that the team uses.<br />
<br />
&nbsp;</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Main_Page&diff=1657Main Page2016-10-08T06:47:50Z<p>DBrettle: </p>
<hr />
<div><br />
[[File:2016Logo.png|thumb|right|Team 199's Current Brand Logo]]'''Team 199: Deep Blue Robotics''' was created to support Carlmont High School Students and allow them to continue their in-depth STEM education.<br />
<br />
In 2003, students at Carlmont High School in Belmont, CA joined forces with Woodside High School’s FRC Team 100, pooling resources to build a competitive strong robotics team. However, in 2015, Woodside's program was so successful that it was suggested we create a second team at Carlmont, therefore reverting the team back to its original 1995 configuration.<br />
<br />
Many Carlmont students from Team 100 wanted a way to continue their involvement in a strong FRC team, and opted to create their own program. The students currently on Team 199 are highly motivated, and have worked hard to quickly build an incredible FRC team from scratch. The students of Carlmont High School currently face the challenge of creating a shop with limited funding, as Carlmont’s administration has indicated that it cannot supply the team with any funds. Therefore, we are actively searching for corporate sponsors and personal donors. As well as securing funding, we are also searching for team mentors to teach and guide the students of the team as they tackle the challenges inherent in building a complex robot in just six weeks.<br />
<br />
Our mission statement: The mission of the Carlmont Robotics FRC team is to provide an opportunity for students to learn engineering, project management, and community relations skills in an environment that is fun, yet competitive and challenging at times in order to simulate real world situations and prepare our students for real-world projects.<br />
<br />
== Team History ==<br />
<br />
From January 2016 to Feburary 2016, Team 199 participated in the FIRST FRC 2016 Season, in which teams all across the US and around the world had six weeks to build a robot for the 2016 game, [[FIRST_Stronghold|FIRST Stronghold]]. Team 199 competed at Silicon Valley Regional.<br />
<br />
Prior to 2015, Carlmont students share history with Team 100, a team based out of Woodside High School. For information on their robots and history, please see [http://team100.org Team 100's web site].<br />
<br />
== Stay Informed ==<br />
<br />
Use the [[Team_Dashboard|Team Dashboard]] to see what is currently going on and what's on the horizon.<br />
<br />
== Find Help ==<br />
<br />
Use the [[Mentor_Directory|Mentor Directory]] to find a mentor to help you.<br />
<br />
== Knowledge Base ==<br />
<br />
[[Information_Technology|Information Technology]] - Information about managing the website, this wiki, project management tools, classroom computers and other IT tools that the team uses.<br />
<br />
Testing.<br />
<br />
&nbsp;</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Java_1:_Basics&diff=1621Java 1: Basics2016-10-06T06:28:46Z<p>DBrettle: /* Hello World */ Use syntaxhighlight extension</p>
<hr />
<div>Before you start programming robots, you must first learn the basics of the Java language. In this section, you will learn some fundamental Java concepts that will allow you to write simple programs.<br />
<br />
==Developer Tools==<br />
<br />
Before you can start programming you need to download some developer tools. <br />
<br />
'''Eclipse''' - Eclipse is a program used for writing and running code. You can download the latest version of the Java Development Kit (JDK) [http://www.oracle.com/technetwork/java/javase/downloads/index.html here] and the Eclipse Integrated Development Environment (Eclipse IDE) [http://www.eclipse.org/ here].<br />
<br />
'''GitHub''' - GitHub stores all of our code in an online repository, so that we can easily collaborate on projects, access code from any computer, save a record of past versions of the code (version control), and branch off into different projects during development. Follow [[Code Repository |this tutorial]] to install and use GitHub.<br />
<br />
==Hello World==<br />
<br />
Follow these steps to write a simple program that prints out the text "Hello, world." However, before we begin you should learn about Java's naming conventions. In general, when naming things in Java you should avoid using spaces, and instead use camelCase (i.e. capitalizingTheFirstLetterOfEachWordExceptTheFirst). You also cannot start names with a number, or include any punctuation besides underscores. Additionally, there are certain [https://docs.oracle.com/javase/tutorial/java/nutsandbolts/_keywords.html restricted words] that already have a meaning in the Java language, so they cannot be used as names either.<br />
#'''Create a project''' - In the Eclipse menu bar go to: File > New > Java Project. Enter a name for your project (e.g. "HelloWorld") and click Finish. Your project name can be anything you want because the normal naming rules don't apply.<br />
#'''Create a package''' - A package is a collection of files; essentially a folder to group code together. In the Package Explorer, right click on your project and go to New > Package. Package names should be entirely lowercase (e.g. "mypackage" or "helloworld"). Enter a name and click Finish.<br />
#'''Create a class''' - Classes are ".java" text files in which you put code. In the Package Explorer, right-click on your package and go to New > Class. The name of your class should start with a capital letter. Give your class a name and click Finish.<br />
#'''Write the program''' - Open the file that has appeared in your project. The class should look like this:<br />
<br />
<span style="color:#20AB7E"><br />
<syntaxhighlight lang="java"><br />
package helloworld;<br />
<br />
public class HelloWorld {<br />
<br />
}</syntaxhighlight><br />
</span><br />
Inside the { and } of the HelloWorld class write the main method. Code contained between the { and } of the main method is executed when the program is run. Do not worry about how the main method works yet; methods will be covered in a later section. The code for the main method is:<br />
<br />
<nowiki><br />
public static void main(String[] args) {<br />
<br />
}</nowiki><br />
<br />
Inside of the main method write System.out.println(); This line of code prints out text to the output log. The text you want to print out goes in quotation marks inside of the parenthesis. Notice that there is a semicolon at the end of the line. Semicolons signify the end of a line of code; they are the Java equivalent of periods.<br />
<br />
<nowiki><br />
System.out.println("Hello, World!");</nowiki><br />
<br />
Your complete class should now look something like this:<br />
<br />
<nowiki><br />
package helloworld;<br />
<br />
public class HelloWorld {<br />
public static void main(String[] args) {<br />
System.out.println("Hello, World!");<br />
}<br />
}</nowiki><br />
<br />
5. '''Run the program''' - Press the run button (the green arrow). The text "Hello, world!" should appear in the output log.<br />
<br />
==Data Types==<br />
<br />
There are many different ways to store data in Java. These are some of the most basic ones. You will learn how to utilize these data types in your code in the next section, variables.<br />
<br />
===Primitive types===<br />
The most basic data types in Java. There are 8 primitive types: byte, short, int, long, float, double, boolean, and char.<br />
*'''byte''': An 8-bit integer between -128 and 127 (-2<sup>7</sup> to 2<sup>7</sup>-1).<br />
*'''short''': A 16-bit integer between -32,768 and 32,767 (-2<sup>15</sup> to 2<sup>15</sup>-1).<br />
*'''int''': A 32-bit integer between -2<sup>31</sup> and 2<sup>31</sup>-1. The most commonly used type of integer.<br />
*'''long''': A 64-bit integer between -2<sup>63</sup> and 2<sup>63</sup>-1. Usually used for very large numbers. Required to have an L after the number (e.g. 87932658723L).<br />
*'''float''': A 32-bit floating-point number (i.e. a decimal). Required to have an F after the number (e.g. 56.3424F). Floating point numbers work by keeping track of the position of the decimal point (like scientific notation).<br />
*'''double''': A 64-bit floating-point number (i.e. a decimal). More commonly used than floats. Named double because it is twice the size of a float.<br />
*'''boolean''': Either true or false.<br />
*'''char''': A 16-bit unicode character. Surrounded by single quotes (e.g. ‘A’ or ‘÷’).<br />
<br />
===String===<br />
A line of text. Surrounded by double quotes (e.g. “Hello, world.”). Can be thought of as a group of chars. Not a primitive type, which is why it is capitalized whereas the primitive types are lower case.<br />
<br />
For more information on how the data is actually stored in the computer, see the [https://en.wikipedia.org/wiki/Two%27s_complement 2's Complement] and [https://en.wikipedia.org/wiki/Floating_point Floating Point] pages on Wikipedia.<br />
<br />
==Variables==<br />
<br />
Variables are used to store and manipulate data. A variable has three parts: a name, a value, and a data type. The name provides a way to refer to the variable in the code. The value is the information stored in the variable. The data type is the type of information that the variable can store. For example, you could have a variable named “x” that holds the value 42. The data type of the variable would be an int, because 42 is an integer. Then, whenever you type “x” in your program, the code will know that you are referring to the value 42. By storing values in variables, you can easily refer to values that your program used earlier, or even values that you don’t know until the program actually runs.<br />
===Declaration===<br />
<br />
Before using a variable, it must be declared. The main purpose of declaring a variable is to tell the program what type of data your variable can store. Note that variable names should always start with a lowercase letter (unlike classes, which are capitalized). The basic format to declare a variable is the datatype of the variable followed by the variable's name.<br />
<br />
int number;<br />
<br />
===Assignment===<br />
The value of a variable can be set using an equal sign, called the assignment operator. The variable on the left of the equal sign will be assigned the value on the right of the equal sign.<br />
<br />
number = 42;<br />
<br />
The declaration and assignment can be combined into a single statement:<br />
<br />
int number = 42;<br />
<br />
A value can also be another variable:<br />
<br />
int variable1 = 42;<br />
int variable2 = variable1; // variable2 is set to 42<br />
<br />
Multiple variables of the same type can be declared at once using commas:<br />
<br />
int a = 1, b = 2, c = 3;<br />
<br />
Multiple variables can by assigned the same value at once using chained equal signs. All of the variables will be assigned the rightmost value:<br />
<br />
a = b = c = 42; // a, b, and c are all set to 42<br />
<br />
==Operators==<br />
<br />
Operators allow you to perform various operations on variables.<br />
<br />
===Arithmetic Operators===<br />
Basic mathematic operations<br />
<br />
{| class="wikitable"<br />
! style="text-align:left;"|Operation<br />
! Notation<br />
! Description<br />
! Example<br />
|-<br />
| Addition<br />
| +<br />
| Same as normal math<br />
| 5 + 5 = 10<br />
|-<br />
| Subtraction<br />
| -<br />
| Same as normal math<br />
| 10 - 5 = 5<br />
|-<br />
| Multiplication<br />
| *<br />
| Same as normal math<br />
| 5 * 5 = 25<br />
|-<br />
| Division<br />
| /<br />
| Same as normal math, but the quotient of two integers will be truncated an integer (always rounded down)<br />
| 5.0 / 2.0 = 2.5<br />
5 / 2 = 2<br />
|-<br />
| Modulus<br />
| %<br />
| Finds the remainder when dividing the first number by the second number<br />
| 10 % 3 = 1<br />
10 % 2 = 0<br />
|}<br />
<br />
===Arithmetic Shorthand===<br />
Faster ways to perform mathematical operations on variables<br />
<br />
{| class="wikitable<br />
! style="text-align:left;"|Shorthand<br />
! Equivalent<br />
|-<br />
| a++<br />
| a = a + 1<br />
|-<br />
| a += b<br />
| a = a + b <br />
|-<br />
| a--<br />
| a = a - 1<br />
|-<br />
| a -= b<br />
| a = a - b<br />
|}<br />
Note that the <span style="color:#20AB7E">*=</span>, <span style="color:#20AB7E">/=</span>, and <span style="color:#20AB7E">%=</span> operators can be used in the same way as the <span style="color:#20AB7E">+=</span> and <span style="color:#20AB7E">-=</span> operators.<br />
<br />
===Equality/Relational Operators===<br />
Operations that compare two numbers and return a boolean<br />
<br />
{| class="wikitable"<br />
! style="text-align:left;"|Operator<br />
! Notation<br />
! Example<br />
! Returns<br />
|-<br />
| Equal to<br />
| ==<br />
| 3==4<br />
| false<br />
|-<br />
| Not equal to<br />
| !=<br />
| 3!=4<br />
| true<br />
|-<br />
| Less than<br />
| <<br />
| 3<4<br />
| true<br />
|-<br />
| Less than or equal to <br />
| <=<br />
| 3<=4<br />
4<=4<br />
| true<br />
true<br />
|-<br />
| Greater than<br />
| ><br />
| 3>4<br />
| false<br />
|-<br />
| Greater than or equal to <br />
| >=<br />
| 3>=4<br />
4>=4<br />
| false<br />
true<br />
|}<br />
<br />
===Conditional Operators===<br />
Operators that compare boolean expressions and return a single boolean<br />
<br />
{| class="wikitable Unicode"<br />
! style="text-align:left;"|Operator<br />
! Notation<br />
! Description<br />
! Example<br />
! Returns<br />
|-<br />
| and<br />
| &&<br />
| True if and only if both conditions are true<br />
| 3<5 && 3==4<br />
| false<br />
|-<br />
| or<br />
| | | | <br />
| True if and only if at least one condition is true<br />
| | 3==5 | | 1<2<br />
| true<br />
|-<br />
| not<br />
| !<br />
| True if and only if the condition is false<br />
| !(1<5)<br />
| false<br />
|}<br />
<br />
<br />
'''Bitwise Operators''' - Operators used to perform bitwise operations on integers. These operators are fairly complicated and rarely used, so they will not be covered in this tutorial. If you are still interested, see the [http://www.google.com/url?q=http%3A%2F%2Fdocs.oracle.com%2Fjavase%2Ftutorial%2Fjava%2Fnutsandbolts%2Fop3.html&sa=D&sntz=1&usg=AFrqEzflwMd7iUsaAznVWN27eeoKkGRCRw Oracle Bitwise Tutorial].<br />
<br />
'''Type Comparison Operator''' - The operator <span style="color:#20AB7E">instanceof</span> returns true if and only if a value is of a given data type. For example, <span style="color:#20AB7E">"Hello" instanceof String</span> would be true.<br />
<br />
'''Order of Operations''' - In general, <span style="color:#20AB7E">not</span> conditional operations occur first, then arithmetic operations (PEMDAS), then relational operations and type comparisons, then the <span style="color:#20AB7E">and</span> and <span style="color:#20AB7E">or</span> conditional operations (in that order), then lastly assignment operations. Operations with the same priority proceed from left to right. See the [https://docs.oracle.com/javase/tutorial/java/nutsandbolts/operators.html Oracle Order of Operations Tutorial] for more detail. When in doubt, you can always manually group operations using parentheses.<br />
<br />
==Control Statements==<br />
<br />
Normally a program runs sequentially; when one line of code finishes the next line of code starts. However, control statements allow you to redirect the flow of the program. Note that any variables declared inside of a control statement cannot be used outside of that control statement. If the statement only contains a single line of code, the brackets are not necessary.<br />
<br />
===If-Statement===<br />
If-statements take a condition that resolves to either true or false and execute the code inside if it resolves to true.<br />
<br />
<nowiki><br />
if (3 < 5) {<br />
System.out.println("I can do math!");<br />
}<br />
if (3 == 3 || 4 < 1) {<br />
System.out.println("I can't do math, but that's ok!");<br />
}</nowiki><br />
<br />
===Else-Statement===<br />
Else-statements are appended to if-statements to execute if the condition in the if-statement resolves to false.<br />
<br />
Else-if is another version of an if-statement which presents another condition if the first condition resolves to false. If the else-if also resolves to false, then the next else-if or else will be evaluated.<br />
<br />
In this example, since 1 is not less than 2, the code inside the first set of brackets will not be executed. Then the code will check if one equals two. Since this is also false, the code inside the final else statement will execute, and "one is less that two" will be printed.<br />
<br />
<nowiki><br />
if (1 > 2) {<br />
System.out.println("one is greater than two");<br />
} else if (1 == 2) {<br />
System.out.println("one equals two");<br />
} else {<br />
System.out.println("one is less than two");<br />
}</nowiki><br />
<br />
===While-Loop===<br />
<br />
While-loops will continuously execute the code inside of it as long as its argument resolves to true.<br />
<br />
In this example, all of the integers from 1 to 10 will be printed out. However, when the number reaches 11, the condition <span style="color:#20AB7E">number<=10</span> will be false, so the loop will terminate.<br />
<br />
<nowiki><br />
int number = 1;<br />
while (number <= 10) {<br />
System.out.println(number);<br />
number++;<br />
}</nowiki><br />
<br />
While-loops can also be used to create infinite loops if the condition is always true. For example, this code will print out numbers starting at one and continuing on to infinity until the program is manually terminated. Always be careful not to accidentally create infinite loops in your code, or your program will never finish.<br />
<br />
<nowiki><br />
int number = 1;<br />
while (true) {<br />
System.out.println(number);<br />
number++;<br />
}</nowiki><br />
<br />
One way to prevent infinite loops is to terminate a loop early using <span style="color:#20AB7E">break</span>. This keyword tells the compiler to exit the current innermost control statement that is not an if- or else-statement. This example will print out the numbers from 1 to 10, then break from the loop because <span style="color:#20AB7E">number==10</span> will be true.<br />
<br />
<nowiki><br />
int number = 0;<br />
while (true) {<br />
System.out.println(number);<br />
number++;<br />
if (number == 10) break;<br />
}</nowiki><br />
<br />
There is another keyword, <span style="color:#20AB7E">continue</span>, that skips to the end of the current iteration of a loop. This code will only print out the even numbers from 1 to 10.<br />
<br />
<nowiki><br />
int number = 1;<br />
while (number <= 10) {<br />
if (number%2 == 1) continue;<br />
System.out.println(number + " is even");<br />
}</nowiki><br />
<br />
===Do-While Loop===<br />
<br />
Do-while loops work similarly to while-loops. The main difference is that in a do-while loop, the code is executed once before the condition is evaluated.<br />
<br />
In this example, although <span style="color:#20AB7E">1>2</span> evaluates to false, since the code is executed before the argument is checked, the code will still print out "one is greater that two" one time.<br />
<br />
<nowiki><br />
do {<br />
System.out.println("one is greater than two");<br />
} while (1>2);</nowiki><br />
<br />
===For-Loop===<br />
<br />
For-loops are another type of loop that keeps track of a value and continually executes code according to that value. A for-loop has three arguments. The first argument declares and assigns a variable, usually an int. The second gives a condition for which the loop will execute code. The third argument describes how the value will change with each execution of the bracketed code.<br />
<br />
This for-loop is another way to print the integers from one to ten. The variable <span style="color: green">a</span> starts at one. Every time the for-loop executes, the value of <span style="color:#20AB7E">a</span> increases by one. The loop terminates once <span style="color:#20AB7E">a</span> equals eleven, which invalidates the condition that <span style="color:#20AB7E">a<=10</span>, so 11 will not be printed.<br />
<br />
<nowiki><br />
for (int a = 1; a <= 10; a++) {<br />
System.out.println(a);<br />
}</nowiki><br />
<br />
Note that a for-loop is essentially just a shorthand for a while-loop that executes a set number of times. The same code could be created using the while-loop from earlier.<br />
<br />
<nowiki><br />
int a = 1;<br />
while (a <= 10) {<br />
System.out.println(a);<br />
a++;<br />
}</nowiki><br />
<br />
===Switch-Statement===<br />
<br />
Switch statements are given an argument and execute different code depending on the value of that argument, called the "case".<br />
<br />
This code will execute depending on the value of <span style="color:#20AB7E">day</span>. If <span style="color:#20AB7E">day</span> is not equal to any of the provided cases, then the default case will execute. After each case, put the line <span style="color:#20AB7E">break</span>; This line of code tells the compiler to exit the control statement rather than continuing on to the other cases.<br />
<br />
<nowiki><br />
int day = 1;<br />
switch (day) {<br />
case 1: System.out.println("Today is Monday"); break;<br />
case 2: System.out.println("Today is Tuesday"); break;<br />
case 3: System.out.println("Today is Wednesday"); break;<br />
case 4: System.out.println("Today is Thursday"); break;<br />
case 5: System.out.println("Today is Friday"); break;<br />
case 6: System.out.println("Today is Saturday"); break;<br />
default: System.out.println("Today is Sunday");<br />
}</nowiki><br />
<br />
==Comments==<br />
<br />
Commented code is ignored by the compiler. Comments are essential to document and keep track of your code and help other people understand it. They are also often used to temporarily remove code for debugging purposes.<br />
<br />
'''Single-line Comments''' - Compiler ignores all code on the line after a <span style="color:#20AB7E">//</span> symbol<br />
<br />
// This code will not be executed<br />
<br />
'''Multi-line Comments''' - Compiler ignores all code between the <span style="color:#20AB7E">/*</span> and <span style="color:#20AB7E">*/</span> symbols<br />
<br />
<nowiki><br />
/*<br />
This code will not<br />
be executed either<br />
*/</nowiki><br />
<br />
'''Javadoc Comments''' - Comments that start with <span style="color:#20AB7E">/**</span> span multiple lines and can use [https://en.wikipedia.org/wiki/Javadoc Javadoc] to document code. When your cursor is over something that has a Javadoc comment a tool-tip will appear that has information from the comment on it (the tool-tip is an Eclipse feature, not part of the Java language).<br />
<nowiki><br />
/**<br />
* A javadoc comment.<br />
*/</nowiki><br />
<br />
<br />
Next Lesson: [[Java 2: Object Oriented Programming|Object-Oriented Programming]]</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=User:DBrettle&diff=1620User:DBrettle2016-10-06T06:10:55Z<p>DBrettle: </p>
<hr />
<div><br />
'''''Test''''' '''content'''.<br />
<br />
<syntaxhighlight lang=c><br />
int main()<br />
{<br />
printf ("Hello world!");<br />
return 0;<br />
}<br />
</syntaxhighlight></div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=User:DBrettle&diff=1619User:DBrettle2016-10-06T06:07:29Z<p>DBrettle: </p>
<hr />
<div><br />
'''''Test''''' '''content'''.<br />
<br />
<syntaxhighlight lang="python" line><br />
def quickSort(arr):<br />
less = []<br />
pivotList = []<br />
more = []<br />
if len(arr) <= 1:<br />
return arr<br />
else:<br />
pass<br />
</syntaxhighlight></div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Widget:Google_Presentation&diff=1614Widget:Google Presentation2016-10-05T05:08:57Z<p>DBrettle: Created page with "<noinclude>__NOTOC__ This widget allows you to add '''[http://documents.google.com/support/presentations/ Google Presentations]''' to your wiki page. It was originally create..."</p>
<hr />
<div><noinclude>__NOTOC__<br />
This widget allows you to add '''[http://documents.google.com/support/presentations/ Google Presentations]''' to your wiki page.<br />
<br />
It was originally created by [[mediawikiwiki:User:Sergey Chernyshev|Sergey Chernyshev]] for [http://www.semanticcommunities.com/ Semantic Communities LLC.]<br />
<br />
To insert this widget, use the following code:<br />
<br />
<nowiki>{{#widget:</nowiki>{{PAGENAME}}<nowiki>|docid=dcn37mcz_22cmnwnwf8}}</nowiki><br />
<br />
== Parameters ==<br />
* '''docid''' - docid parameter in document URL<br />
* '''size''' - (optional) allows you to change the size of presentation from small (410x342) to '''medium''' (555x451) or '''large''' (700x599)<br />
<br />
{{Template:Copy to your site}}<br />
<br />
== Related widgets ==<br />
* [[Widget:Google Document|Google Document]] - for embedding documents<br />
* [[Widget:Google Spreadsheet|Google Spreadsheet]] - for embedding spreadsheets<br />
* [[Widget:Google Form|Google Form]] - for embedding spreadsheet forms<br />
<br />
== Sample result ==<br />
{{#widget:Google Presentation|docid=dcn37mcz_22cmnwnwf8}}<br />
</noinclude><includeonly><!--{if $size eq 'medium'}--><iframe src='http://docs.google.com/EmbedSlideshow?docid=<!--{$docid|escape:'urlpathinfo'}-->&amp;size=m' frameborder='0' width='555' height='451'></iframe><!--{elseif $size eq 'large'}--><iframe src='http://docs.google.com/EmbedSlideshow?docid=<!--{$docid|escape:'urlpathinfo'}-->&amp;size=l' frameborder='0' width='700' height='559'></iframe><!--{else}--><iframe src='http://docs.google.com/EmbedSlideshow?docid=<!--{$docid|escape:'urlpathinfo'}-->' frameborder='0' width='410' height='342'></iframe><!--{/if}--></includeonly></div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Widget:Google_Form&diff=1613Widget:Google Form2016-10-05T05:06:51Z<p>DBrettle: </p>
<hr />
<div><noinclude>__NOTOC__<br />
This widget allows you to add '''[http://documents.google.com/support/spreadsheets/bin/answer.py?hl=en&answer=87809 Google Spreadsheet Forms]''' to your wiki page.<br />
<br />
It was originally created by [[mediawikiwiki:User:Sergey Chernyshev|Sergey Chernyshev]] for [http://www.semanticcommunities.com/ Semantic Communities LLC.]<br />
<br />
To insert this widget, use the following code:<br />
<br />
<nowiki>{{#widget:</nowiki>{{PAGENAME}}<nowiki><br />
|key=po-s58YMwf85Q3UxRzdGOBw<br />
|width=600<br />
|height=750<br />
}}</nowiki><br />
<br />
== Parameters ==<br />
* '''key''' - key parameter in emailing/embedding URL<br />
* '''width''' and '''height''' define form dimensions, 300x400 is default, but you might want to copy it from embed code since size depends on fields you have<br />
<br />
{{Template:Copy to your site}}<br />
<br />
== Related widgets ==<br />
* [[Widget:Google Document|Google Document]] - for embedding documents<br />
* [[Widget:Google Spreadsheet|Google Spreadsheet]] - for embedding spreadsheets<br />
* [[Widget:Google Presentation|Google Presentation]] - for embedding presentations<br />
<br />
== Sample result ==<br />
{{#widget:{{PAGENAME}}<br />
|key=po-s58YMwf85Q3UxRzdGOBw<br />
|width=600<br />
|height=750<br />
}}<br />
</noinclude><includeonly><iframe src="http://spreadsheets.google.com/embeddedform?key=<!--{$key|escape:'urlpathinfo'}-->" width="<!--{$width|escape:'html'|default:300}-->" height="<!--{$height|escape:'html'|default:400}-->" frameborder="0" marginheight="0" marginwidth="0">Loading...</iframe></includeonly></div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Widget:Google_Form&diff=1612Widget:Google Form2016-10-05T05:05:32Z<p>DBrettle: Created page with " <noinclude>__NOTOC__<br/> This widget allows you to add '''[http://documents.google.com/support/spreadsheets/bin/answer.py?hl=en&answer=87809 Google Spreadsheet Forms]''' to..."</p>
<hr />
<div><br />
<noinclude>__NOTOC__<br/> This widget allows you to add '''[http://documents.google.com/support/spreadsheets/bin/answer.py?hl=en&answer=87809 Google Spreadsheet Forms]''' to your wiki page.<br />
<br />
It was originally created by [[mediawikiwiki:User:Sergey Chernyshev|Sergey Chernyshev]] for [http://www.semanticcommunities.com/ Semantic Communities LLC.]<br />
<br />
To insert this widget, use the following code:<br />
<br />
&nbsp;<nowiki>{{#widget:</nowiki>{{PAGENAME}}<nowiki><br/> |key=po-s58YMwf85Q3UxRzdGOBw<br/> |width=600<br/> |height=750<br/> }}</nowiki><br />
<br />
== Parameters ==<br/> * '''key''' - key parameter in emailing/embedding URL<br/> * '''width''' and '''height''' define form dimensions, 300x400 is default, but you might want to copy it from embed code since size depends on fields you have<br />
<br />
{{Template:Copy to your site}}<br />
<br />
== Related widgets ==<br/> * [[Widget:Google Document|Google Document]] - for embedding documents<br/> * [[Widget:Google Spreadsheet|Google Spreadsheet]] - for embedding spreadsheets<br/> * [[Widget:Google Presentation|Google Presentation]] - for embedding presentations<br />
<br />
== Sample result ==<br/> {{#widget:{{PAGENAME}}<br/> |key=po-s58YMwf85Q3UxRzdGOBw<br/> |width=600<br/> |height=750<br/> }}<br/> </noinclude><includeonly><iframe src="http://spreadsheets.google.com/embeddedform?key=<!--{$key|escape:'urlpathinfo'}-->" width="<!--{$width|escape:'html'|default:300}-->" height="<!--{$height|escape:'html'|default:400}-->" frameborder="0" marginheight="0" marginwidth="0">Loading...</iframe></includeonly><br />
<br />
&nbsp;</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Widget:Google_Document&diff=1611Widget:Google Document2016-10-05T04:59:35Z<p>DBrettle: </p>
<hr />
<div><noinclude>__NOTOC__<br />
This widget allows you to add '''[http://documents.google.com/support/ Google Documents]''' to your wiki page.<br />
<br />
It was originally created by [[mediawikiwiki:User:Sergey Chernyshev|Sergey Chernyshev]] for [http://www.semanticcommunities.com/ Semantic Communities LLC.]<br />
<br />
To insert this widget, use the following code:<br />
<br />
<nowiki>{{#widget:</nowiki>{{PAGENAME}}<nowiki><br />
|id=1hhpWRL4oyH6Aqf42laXo_lElObX_1JiaV4FMt8llA_U<br />
|width=500<br />
|height=300<br />
}}</nowiki><br />
<br />
== Parameters ==<br />
* '''width''' and '''height''' define document dimensions, 500x300 is default<br />
* '''id''' - id parameter used in the URL<br />
* '''key''' - docID parameter used in old document URL (use it instead of '''id''' to embed old document)<br />
<br />
; Note: In order for your embedded Google Doc to be visible on your wiki, you must first '''publish it to the web'''.<br />
# Open your document.<br />
# From the document menu, choose File > Publish to the Web...<br />
# Click "Start publishing" button.<br />
# See also: [http://support.google.com/docs/bin/answer.py?hl=en&answer=183965 Publishing does not affect visibility options]<br />
<br />
== Sample result ==<br />
{{#widget:{{PAGENAME}}<br />
|id=1hhpWRL4oyH6Aqf42laXo_lElObX_1JiaV4FMt8llA_U<br />
|width=500<br />
|height=300<br />
}}<br />
<br />
=== Old document ===<br />
Old document that has '''docID''' attribute in the URL instead of '''id'''.<br />
<br />
{{#widget:{{PAGENAME}}<br />
|key=dcn37mcz_34cvfjpmhf<br />
|width=500<br />
|height=300<br />
}}<br />
<br />
{{Template:Copy to your site}}<br />
* Since Google Migration to Google Drive, the template reference has changed. See [http://wiki.glitchdata.com/index.php?title=Widget:Google_Document here] for latest template code.<br />
<br />
<br />
== Related widgets ==<br />
* [[Widget:Google Spreadsheet|Google Spreadsheet]] - for embedding spreadsheets<br />
* [[Widget:Google Form|Google Form]] - for embedding spreadsheet forms<br />
* [[Widget:Google Presentation|Google Presentation]] - for embedding presentations<br />
<br />
</noinclude><br />
<includeonly><br />
<iframe width="<!--{$width|escape:'html'|default:500}-->" height="<!--{$height|escape:'html'|default:300}-->" frameborder="1" src="http://docs.google.com/<!--{if isset($id)}-->document/d/<!--{$id|escape:'urlpathinfo'}-->/edit?usp=sharing<!--{elseif isset($key)}-->View?docID=<!--{$key|escape:'urlpathinfo'}-->&hgd=1<!--{/if}-->"><br />
</iframe><br />
</includeonly></div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Widget:Google_Document&diff=1610Widget:Google Document2016-10-05T04:57:24Z<p>DBrettle: </p>
<hr />
<div><br />
__NOTOC__ This widget allows you to add '''[http://documents.google.com/support/ Google Documents]''' to your wiki page.<br />
<br />
It was originally created by [[http://www.mediawiki.org/wiki/User:Sergey_Chernyshev|Sergey Chernyshev]] for [http://www.semanticcommunities.com/ Semantic Communities LLC.]<br />
<br />
To insert this widget, use the following code:<br />
<br />
<nowiki>{{#widget:</nowiki>{{PAGENAME}}<nowiki><br />
|id=1hhpWRL4oyH6Aqf42laXo_lElObX_1JiaV4FMt8llA_U<br />
|width=500<br />
|height=300<br />
}}</nowiki><br />
<br />
== Parameters ==<br />
<br />
*'''width''' and '''height''' define document dimensions, 500x300 is default <br />
*'''id''' - id parameter used in the URL <br />
*'''key''' - docID parameter used in old document URL (use it instead of '''id''' to embed old document) <br />
<br />
;Note <br />
:In order for your embedded Google Doc to be visible on your wiki, you must first '''publish it to the web'''. <br />
<br />
#Open your document. <br />
#From the document menu, choose File > Publish to the Web... <br />
#Click "Start publishing" button. <br />
#See also: [http://support.google.com/docs/bin/answer.py?hl=en&answer=183965 Publishing does not affect visibility options] <br />
<br />
== Sample result ==<br />
<br />
{{#widget:{{PAGENAME}}<br />
|id=1hhpWRL4oyH6Aqf42laXo_lElObX_1JiaV4FMt8llA_U<br />
|width=500<br />
|height=300<br />
}}<br />
<br />
=== Old document ===<br />
<br />
Old document that has '''docID''' attribute in the URL instead of '''id'''.<br />
<br />
{{#widget:{{PAGENAME}}<br />
|key=dcn37mcz_34cvfjpmhf<br />
|width=500<br />
|height=300<br />
}}<br />
<br />
== Related widgets ==<br />
<br />
*[[Widget:Google_Spreadsheet|Google Spreadsheet]] - for embedding spreadsheets <br />
*[[Widget:Google_Form|Google Form]] - for embedding spreadsheet forms <br />
*[[Widget:Google_Presentation|Google Presentation]] - for embedding presentations <br />
<br />
</noinclude><br />
<includeonly><br />
<iframe width="<!--{$width|escape:'html'|default:500}-->" height="<!--{$height|escape:'html'|default:300}-->" frameborder="1" src="http://docs.google.com/<!--{if isset($id)}-->document/d/<!--{$id|escape:'urlpathinfo'}-->/edit?usp=sharing<!--{elseif isset($key)}-->View?docID=<!--{$key|escape:'urlpathinfo'}-->&hgd=1<!--{/if}-->"><br />
</iframe><br />
</includeonly></div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Widget:Google_Document&diff=1609Widget:Google Document2016-10-05T04:53:43Z<p>DBrettle: </p>
<hr />
<div><br />
__NOTOC__ This widget allows you to add '''[http://documents.google.com/support/ Google Documents]''' to your wiki page.<br />
<br />
It was originally created by [[http://www.mediawiki.org/wiki/User:Sergey_Chernyshev|Sergey Chernyshev]] for [http://www.semanticcommunities.com/ Semantic Communities LLC.]<br />
<br />
To insert this widget, use the following code:<br />
<br />
<br />
&nbsp;<br />
<nowiki>{{#widget:</nowiki><br />
<br />
{{PAGENAME}}<br />
<nowiki><br />
|id=1hhpWRL4oyH6Aqf42laXo_lElObX_1JiaV4FMt8llA_U<br />
|width=500<br />
|height=300<br />
}}</nowiki><br />
<br />
== Parameters ==<br />
<br />
*'''width''' and '''height''' define document dimensions, 500x300 is default <br />
*'''id''' - id parameter used in the URL <br />
*'''key''' - docID parameter used in old document URL (use it instead of '''id''' to embed old document) <br />
<br />
;Note <br />
:In order for your embedded Google Doc to be visible on your wiki, you must first '''publish it to the web'''. <br />
<br />
#Open your document. <br />
#From the document menu, choose File > Publish to the Web... <br />
#Click "Start publishing" button. <br />
#See also: [http://support.google.com/docs/bin/answer.py?hl=en&answer=183965 Publishing does not affect visibility options] <br />
<br />
== Sample result ==<br />
<br />
{{#widget:{{PAGENAME}}<br />
|id=1hhpWRL4oyH6Aqf42laXo_lElObX_1JiaV4FMt8llA_U<br />
|width=500<br />
|height=300<br />
}}<br />
<br />
=== Old document ===<br />
<br />
Old document that has '''docID''' attribute in the URL instead of '''id'''.<br />
<br />
{{#widget:{{PAGENAME}}<br />
|key=dcn37mcz_34cvfjpmhf<br />
|width=500<br />
|height=300<br />
}}<br />
<br />
</noinclude><br />
<includeonly><br />
<iframe width="<!--{$width|escape:'html'|default:500}-->" height="<!--{$height|escape:'html'|default:300}-->" frameborder="1" src="http://docs.google.com/<!--{if isset($id)}-->document/d/<!--{$id|escape:'urlpathinfo'}-->/edit?usp=sharing<!--{elseif isset($key)}-->View?docID=<!--{$key|escape:'urlpathinfo'}-->&hgd=1<!--{/if}-->"><br />
</iframe><br />
</includeonly><br />
<br />
== Related widgets ==<br />
<br />
*[[Widget:Google_Spreadsheet|Google Spreadsheet]] - for embedding spreadsheets <br />
*[[Widget:Google_Form|Google Form]] - for embedding spreadsheet forms <br />
*[[Widget:Google_Presentation|Google Presentation]] - for embedding presentations</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Widget:Google_Document&diff=1608Widget:Google Document2016-10-05T04:47:38Z<p>DBrettle: Created page with "<noinclude>__NOTOC__ This widget allows you to add '''[http://documents.google.com/support/ Google Documents]''' to your wiki page. It was originally created by mediawikiwi..."</p>
<hr />
<div><noinclude>__NOTOC__<br />
This widget allows you to add '''[http://documents.google.com/support/ Google Documents]''' to your wiki page.<br />
<br />
It was originally created by [[mediawikiwiki:User:Sergey Chernyshev|Sergey Chernyshev]] for [http://www.semanticcommunities.com/ Semantic Communities LLC.]<br />
<br />
To insert this widget, use the following code:<br />
<br />
<nowiki>{{#widget:</nowiki>{{PAGENAME}}<nowiki><br />
|id=1hhpWRL4oyH6Aqf42laXo_lElObX_1JiaV4FMt8llA_U<br />
|width=500<br />
|height=300<br />
}}</nowiki><br />
<br />
== Parameters ==<br />
* '''width''' and '''height''' define document dimensions, 500x300 is default<br />
* '''id''' - id parameter used in the URL<br />
* '''key''' - docID parameter used in old document URL (use it instead of '''id''' to embed old document)<br />
<br />
; Note: In order for your embedded Google Doc to be visible on your wiki, you must first '''publish it to the web'''.<br />
# Open your document.<br />
# From the document menu, choose File > Publish to the Web...<br />
# Click "Start publishing" button.<br />
# See also: [http://support.google.com/docs/bin/answer.py?hl=en&answer=183965 Publishing does not affect visibility options]<br />
<br />
== Sample result ==<br />
{{#widget:{{PAGENAME}}<br />
|id=1hhpWRL4oyH6Aqf42laXo_lElObX_1JiaV4FMt8llA_U<br />
|width=500<br />
|height=300<br />
}}<br />
<br />
=== Old document ===<br />
Old document that has '''docID''' attribute in the URL instead of '''id'''.<br />
<br />
{{#widget:{{PAGENAME}}<br />
|key=dcn37mcz_34cvfjpmhf<br />
|width=500<br />
|height=300<br />
}}<br />
<br />
{{Template:Copy to your site}}<br />
* Since Google Migration to Google Drive, the template reference has changed. See [http://wiki.glitchdata.com/index.php?title=Widget:Google_Document here] for latest template code.<br />
<br />
<br />
== Related widgets ==<br />
* [[Widget:Google Spreadsheet|Google Spreadsheet]] - for embedding spreadsheets<br />
* [[Widget:Google Form|Google Form]] - for embedding spreadsheet forms<br />
* [[Widget:Google Presentation|Google Presentation]] - for embedding presentations<br />
<br />
</noinclude><includeonly><iframe width="<!--{$width|escape:'html'|default:500}-->" height="<!--{$height|escape:'html'|default:300}-->" frameborder="1" src="http://docs.google.com/<!--{if isset($id)}-->document/pub?id=<!--{$id|escape:'urlpathinfo'}-->&amp;embedded=1<!--{elseif isset($key)}-->View?docID=<!--{$key|escape:'urlpathinfo'}-->&hgd=1<!--{/if}-->"></iframe></includeonly></div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Mentor_Directory&diff=1607Mentor Directory2016-10-05T04:45:53Z<p>DBrettle: Switch to Widget:Google Spreadsheet</p>
<hr />
<div><br />
== Need a Mentor? ==<br />
<br />
If you are looking for help, use this table to find a mentor with the appropriate expertise:<br />
<br />
{{#widget:Google Spreadsheet<br />
|key=101yfPnSgnmLKwPORn9BLFHgl8G5CLtORHV_HcvoCrxo<br />
|width=100%<br />
|height=1400<br />
}}</div>DBrettlehttp://wiki.carlmontrobotics.org/index.php?title=Widget:Google_Spreadsheet&diff=1606Widget:Google Spreadsheet2016-10-05T04:41:38Z<p>DBrettle: Created page with "<noinclude>__NOTOC__ This widget allows you to add '''[http://documents.google.com/support/spreadsheets/ Google Spreadsheets]''' to your wiki page. * Created by [http://www.me..."</p>
<hr />
<div><noinclude>__NOTOC__<br />
This widget allows you to add '''[http://documents.google.com/support/spreadsheets/ Google Spreadsheets]''' to your wiki page.<br />
* Created by [http://www.mediawikiwidgets.org/User:Sergey_Chernyshev Sergey Chernyshev]<br />
* Since Google Docs migrated to Google Drive, the reference for the template code has change. The latest is available [http://wiki.glitchdata.com/index.php?title=Widget:Google_Spreadsheet here].<br />
<br />
== Using this widget ==<br />
For information on how to use this widget, see [http://www.mediawikiwidgets.org/Google_Spreadsheet widget description page on MediaWikiWidgets.org].<br />
<br />
== Copy to your site ==<br />
To use this widget on your site, just install [https://www.mediawiki.org/wiki/Extension:Widgets MediaWiki Widgets extension] and copy the [{{fullurl:{{FULLPAGENAME}}|action=edit}} full source code] of this page to your wiki as page '''{{FULLPAGENAME}}'''.<br />
</noinclude><includeonly><iframe width="<!--{$width|escape:'html'|default:500}-->" height="<!--{$height|escape:'html'|default:300}-->" frameborder="0" src="http://spreadsheets.google.com/pub?key=<!--{$key|escape:'urlpathinfo'}--><!--{if not $page}-->&output=html&widget=true<!--{/if}-->"></iframe></includeonly></div>DBrettle