-
Notifications
You must be signed in to change notification settings - Fork 69
"Let's make a roadmap together" hangout 12 Aug 2014
Pietro Di Bello edited this page Aug 12, 2014
·
1 revision
#Some opionions gathered during our hangout (see #6)
- Be careful to not put too much stuff in each sigle path, put an explicit limit to the number of elements in each path
- Inspired to the "code school" paths, valuable only when completed
- Github is fine as a platform to share the study path
- Ok to limit elements in each path
- What about sizing each path so that could be completed in a week at most?
- How do we compose an actual path for a "new kid in town"? ** forking the repo?
- This path will be used by us too
- Should we estimate with story points each item in the path so to have a weight on each path?
- Github is fine as a platform to share the study path
- We should fix some blocks of the path as mandatory for each new xpepper guy, while other should be declared optional. ** e.g. agile methods and practices, SOLID principles, OOP should all be mandatory, while the single language should not ** How do we support each "student" and follow his steps on the path? ** Should we introduce a "sysop" path?
What about using Trello to track the progress of each "student" and share his progress with the team?
- To track and share the progress of each "student" I propose to use gist (https://gist.github.com): each one use it as a wiki where he copy&paste&adapt the single elements of the path and then publish the link somewehere.
- Forking may be used to have each student have a personal copy of the path