Talk:Outreach programs/Life of a successful project/Archive 2

Previous discussion was archived at Talk:Outreach programs/Life of a successful project/Archive 1 on 2015-10-02.

My personal experience has been that reporting on a daily or near daily basis is good exercise, especially for students working independently and / or remotely. In particular, more regular reports help:

• Identify work actually accomplished and try to get something done (reportable) on a given day.

• Provide good records of accomplishments when needing to summarize at project end for a postmortem, CV, blog, etc.

• Encourage good communication, give some peace of mind to the author as everyone knows they're working hard even if there hasn't necessarily been a deliverable that day, and allows the reader to promptly offer help in areas the author may be struggling with.
• Consolidate the author's thoughts on the problems and solutions of the day.
• Do a timeline and project status check.
• Practice quick, clear writing and thinking, especially useful for developers and / or nonnative speakers that must communicate ideas with others.

Of course, all of these are relevant for weekly checkins, too. I don't think the format matters so much. The author will figure out what is most useful. Once the author learns their value, these checkins can become quite rewarding for both author and reader.

That is good piece of advise, Stephen. We should add this to the page, Tony.

Generally teams decide for themselves what works best for them but daily/alternate day reporting has proven excellent in our past rounds. In my opinion it works better if the reports aren't being scribbled on a task/wiki page but the reporting happens by talking to the mentor directly. Via IRC or Hangouts or something similar. In the initial few weeks, the student tends to get stuck at every other step and talking to the mentor frequently will help them not be blocked for days at end. They generally pick up enough pace by midterm to work independently mostly.

I just realized that microtasks are not even mentioned in this doc. I don't have time to make a proper edit now, but here goes a rushed description: microtasks are key for candidates and mentors to understand the skills required for a project and whether the candidate has a basic handling of these skills. They are also a good opportunity to start working together, show communication styles, and other practical details that a project application alone will not show. The basic type of microtasks are existing open bugs related with the area of the project idea. Be careful to offer a combination of easy an not so easy bugs, but never tasks that would take more than, say, a full day of an experienced contributor to fix. micro-tasks. :) If there are no open bugs (lucky you!) then first basic tasks related with the implementation of the project idea are good as well.

added in https://www.mediawiki.org/w/index.php?title=Outreach_programs%2FLife_of_a_successful_project&type=revision&diff=1911036&oldid=1910882