Alfred: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Project Alfred is an experiment in status reporting and accountability tracking for small teams. ==Background== ;Goals * Create a dashboard for viewing weekly status reports...") |
|||
| Line 2: | Line 2: | ||
==Background== | ==Background== | ||
Regular meetings with roundtable status updates are great for teams which strive to be efficient and transparent. However the process of editing a status update is tedious and repetitive. Furthermore most tools used for collecting updates (e.g. wiki) offer no way to track an evolution of an update. If something was reported to be a struggle one week, what happens to it the following week? | |||
;Goals | ;Goals | ||
| Line 7: | Line 8: | ||
* Design a workflow for rolling updates over to the following week. | * Design a workflow for rolling updates over to the following week. | ||
* Allow an easy data input via a chat bot. | * Allow an easy data input via a chat bot. | ||
* Integrate the dashboard with Bugzilla and GitHub. | |||
;Non-goals | ;Non-goals | ||
Revision as of 17:11, 23 January 2017
Project Alfred is an experiment in status reporting and accountability tracking for small teams.
Background
Regular meetings with roundtable status updates are great for teams which strive to be efficient and transparent. However the process of editing a status update is tedious and repetitive. Furthermore most tools used for collecting updates (e.g. wiki) offer no way to track an evolution of an update. If something was reported to be a struggle one week, what happens to it the following week?
- Goals
- Create a dashboard for viewing weekly status reports.
- Design a workflow for rolling updates over to the following week.
- Allow an easy data input via a chat bot.
- Integrate the dashboard with Bugzilla and GitHub.
- Non-goals
- Create a project management tool.
- Create a to-do list.
Design Philosophy
Alfred is simple, ambient and reactive.