Time Sheet Web App: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=MVP Requirements= | |||
=Documentation Requirements= | |||
*App is fully documented so anyone can manage its subsequent modification (coding level) | |||
*Admin side is documented, including a 1 minute video | |||
*User howto is documented, including a 1 minute video | |||
=Automation= | |||
* | |||
*Input hours at any time, or all at once | *Input hours at any time, or all at once | ||
*App should encourage time logging on an ongoing basis, as it provides an automatic week tally. | *App should encourage time logging on an ongoing basis, as it provides an automatic week tally. | ||
| Line 9: | Line 21: | ||
*Graphs the total size of the dev team at one point | *Graphs the total size of the dev team at one point | ||
*Provides a stats dashboard with all contributors like current graph, agraph broken down by each contributor and labeled, a graph of wiki editors, number of wiki articles, number of edits | *Provides a stats dashboard with all contributors like current graph, agraph broken down by each contributor and labeled, a graph of wiki editors, number of wiki articles, number of edits | ||
*Pull in alalytics from wiki to track overall Number of Editors, Number of Wiki Pages, Machines Documented | *Pull in alalytics from wiki to track overall Number of Editors, Number of Wiki Pages, Machines Documented | ||
*Create a burndown for each project. Burndown goes up to a successful enterprise. | *Create a burndown for each project. Burndown goes up to a successful enterprise. | ||
| Line 32: | Line 42: | ||
*All the notice emails are handled based on a clear algorithm for participation, which automates and clarifies our retention procedures | *All the notice emails are handled based on a clear algorithm for participation, which automates and clarifies our retention procedures | ||
=Good Standing Algorithm= | |||
=Other= | |||
==Content Feed== | |||
*Has auto feed from contributor logs to a single wiki page gallery,where Devs mark up their wiki for inclusion into weekly Results Gallery | |||
*Results Gallery wiki page feed happens automatically, with new wiki pages created automatically | |||
==Good Standing Algorithm== | |||
*65% is our absolute minimum cutoff | *65% is our absolute minimum cutoff | ||
*If 65% cutoff is not attained over a month duration, Dev is removed from Dev status and asked to rejoin if their time frees up | *If 65% cutoff is not attained over a month duration, Dev is removed from Dev status and asked to rejoin if their time frees up | ||
*Regular Track is defined as someone who just participates | *Regular Track is defined as someone who just participates | ||
*Advanced Track is defined. This means that a certain person is preparing for running workshops. This includes building a machine and then | *Advanced Track is defined. This means that a certain person is preparing for running workshops. This includes building a machine and then committing 2 weeks on site for a [[Dedicated Project Visit]]. | ||
Revision as of 20:53, 18 July 2017
MVP Requirements
Documentation Requirements
- App is fully documented so anyone can manage its subsequent modification (coding level)
- Admin side is documented, including a 1 minute video
- User howto is documented, including a 1 minute video
Automation
- Input hours at any time, or all at once
- App should encourage time logging on an ongoing basis, as it provides an automatic week tally.
- Sends notification - when person did not fill it out
- Sends notification to Developer if they are not filling their commitment at the absolute minimum level (6.5)
- Boots people off if they don't meet their average absolute minimum after 1 month
- Rewards with an Outstanding Badge for meeting 90% of their quota after 3 months
- Produces the graph that we use currently on an ongoing basis
- Graphs the number of wiki editors on an ongoing basis
- Graphs the total size of the dev team at one point
- Provides a stats dashboard with all contributors like current graph, agraph broken down by each contributor and labeled, a graph of wiki editors, number of wiki articles, number of edits
- Pull in alalytics from wiki to track overall Number of Editors, Number of Wiki Pages, Machines Documented
- Create a burndown for each project. Burndown goes up to a successful enterprise.
- Can app talk to Piwik?
- Can app query Mediawiki database?
- Can app query Wordpress database?
Automation
- Automates welcome email
- Automates interview calendar
- Automates regret letter
- Automates badge creation and update
- Automates sticker sending + swag sending
- Integrates with main website (WordPress) for automatic display via simple iframe or embed code
- integrates display to wiki with iframe or embed code, and is updated automatically on those pages
Emails
- Integrates with phpList so Developees List this is not YAEL (Yet Another Email List)
- Adds and removes emails from Dev List automatically
- Contains emails of all contributors
- All the notice emails are handled based on a clear algorithm for participation, which automates and clarifies our retention procedures
Other
Content Feed
- Has auto feed from contributor logs to a single wiki page gallery,where Devs mark up their wiki for inclusion into weekly Results Gallery
- Results Gallery wiki page feed happens automatically, with new wiki pages created automatically
Good Standing Algorithm
- 65% is our absolute minimum cutoff
- If 65% cutoff is not attained over a month duration, Dev is removed from Dev status and asked to rejoin if their time frees up
- Regular Track is defined as someone who just participates
- Advanced Track is defined. This means that a certain person is preparing for running workshops. This includes building a machine and then committing 2 weeks on site for a Dedicated Project Visit.