Time Sheet Web App: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
=MVP Requirements=
=Rollout Sequence=
==Phase 1==
*Input hours at any time, or all at once
*Generates hours graph equivalent of [[Volunteer_Timesheet#Contributor_Graph]] (sum of all contributors'  hours, number of contributors). This is an overall graph over all of time since 2017.
*Generates embeddable Contributor Graph is embeddable (wiki, wordpress)
*Generates graph by contributor for the last 90 days
*Generates overall graph by contributor (over all of their time), with x axis time, and hours on y graph
*Generates embed code for each contributor graph (to paste in Work Log)
*Graphs the number of wiki editors (is this possible?)


==Phase 2==
*Integrates with phpList so Developees List can be used for dev team emails as needed
*Adds and removes emails from active Dev List automatically if people leave the team
*Contains emails of all contributors
*Automatic send of welcome email (to be written up)
*Automatic followup email if 2 weeks pass after Video Cover Letter, to see where a person is.
*Automatic followup email for people to create work log if they don't do so by 2 days.
*Automatic send of regret letter (for devs let go, or for applicants who do not create a work log)
:*Note that work log documents at which point people get stuck - for quality improvement purposes where OSE learns what of its procedures are adequate/clear
*Sends auto emails if logging has not occurred for 7 days (email to be written)
*Sends warning emails if a person is below 6.5 hours per week
*Sends auto email warning if 4 week average is trending below 6.5
*Kicks people off the team if 4 week average is below 6.5. This must be approved by HR admin.


=Documentation Requirements=
=Documentation Requirements=
Line 6: Line 28:
*Admin side is documented, including a 1 minute video
*Admin side is documented, including a 1 minute video
*User howto is documented, including a 1 minute video
*User howto is documented, including a 1 minute video
=Other=
==Other Automation==
*Automates interview calendar
*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




=Automation=
=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.
*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 - when person did not fill it out
Line 22: Line 51:
*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


=Questions=
*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 28: Line 58:
*Can app query Wordpress 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





Revision as of 21:14, 18 July 2017

Rollout Sequence

Phase 1

  • Input hours at any time, or all at once
  • Generates hours graph equivalent of Volunteer_Timesheet#Contributor_Graph (sum of all contributors' hours, number of contributors). This is an overall graph over all of time since 2017.
  • Generates embeddable Contributor Graph is embeddable (wiki, wordpress)
  • Generates graph by contributor for the last 90 days
  • Generates overall graph by contributor (over all of their time), with x axis time, and hours on y graph
  • Generates embed code for each contributor graph (to paste in Work Log)
  • Graphs the number of wiki editors (is this possible?)

Phase 2

  • Integrates with phpList so Developees List can be used for dev team emails as needed
  • Adds and removes emails from active Dev List automatically if people leave the team
  • Contains emails of all contributors
  • Automatic send of welcome email (to be written up)
  • Automatic followup email if 2 weeks pass after Video Cover Letter, to see where a person is.
  • Automatic followup email for people to create work log if they don't do so by 2 days.
  • Automatic send of regret letter (for devs let go, or for applicants who do not create a work log)
  • Note that work log documents at which point people get stuck - for quality improvement purposes where OSE learns what of its procedures are adequate/clear
  • Sends auto emails if logging has not occurred for 7 days (email to be written)
  • Sends warning emails if a person is below 6.5 hours per week
  • Sends auto email warning if 4 week average is trending below 6.5
  • Kicks people off the team if 4 week average is below 6.5. This must be approved by HR admin.

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

Other

Other Automation

  • Automates interview calendar
  • 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


Automation

  • 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

Questions

  • 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?



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.