• Opening slide: Introduce session title & ourselves
K: public sector / education / training / web development / design /site building / client liaison / PM (loosely) / corporate international ft / short sharp (painful) contracts.

T: 

  • WHY - HOW - WHAT:
ONBOARDING / ENABLE / BENEFITS
our takeaways from working such environments - no definite solutions but some considerations

  • SPECIFICALLY:
clarify the purpose 'function' of this session...

  • BAAAD EXPERIENCES: (2 slides one quote)
Throwing out the questions, 
"who here has had a horrendous [and or wonderful! - you lucky bunny!!]" experience being on-boarded into a job/project"
Reflect on the quote ...

  • GITHUB:
There are some wonderful examples, on team management, project management...

BACK POCKET MOMENT!

  • VALVE:
2nd example... identifies qualities of the individual and inspires them "lets make great things" 

  • Here comes the science bit:
kinda
  • Maslows Hierarchy of Needs: (image)
Famous tool for education, psychology and human interaction...
    • Physiological needs
    • Safety & security
    • Social needs
    • Esteem
    • Self-actualisation
  • Maslow quote: 

  • Summarize those those thoughts:

  • Maslows Hierarchy of Needs -new- : (image)
hehehe... but seriously! the interwebz access is VERY important for this job! 

  • WHY bother?
Read through emphasize the points:
    • Communication
    • Productivity
    • Learning
    • HAPPY PEOPLE! \o/

  • did you get that?
Happy people = infinite loop of productivity!

ok this might be an oversimplification.... 

So briefly that was WHY!

  • How the **** do we do this!
7 main points to consider
  • Ideally... (even before on-boarding happens they know:
WHO WHERE WHY

people comforts (remember maslow) team comms/log ins
place of work
admin

  • On boarding documentation
    • Codebase location
    • Install profile instructions
      • Can drush site-install be used or GUI only
      • Content generation scripts? Built into profile, bash or other method?
    • Wiki location
    • Design/theme styleguide
    • Naming conventions for features, modules, themes
    • Theming instruction
    • Main theme to be used
    • Preprocessor setup if exists (SASS/LESS, terminal, modules, local or server based)
    • Custom module theming inside module or theme (location of template, CSS & JS)

  • Introduction session after giving them a brief of their role to read

  • Communication tools
    • How does the team communicate?
    • Skype/irc/other?
    • Development procedures
    • type of procedure
      • Brief intro and/or links about procedure (agile, kanban, CI, deployment)
      • Explanation of implementation of procedure
      • Who to ask for help
    • Source control management
      • CI while always working on a single branch
      • Ticket based branches per task: documented solution/execution
      • Code review via Pull requests?
    • Point of contact per category question
      • Question for designs or styleguide implementation
      • Functionality - UX issues
      • Task allocation
      • Admin/Finance queries
    • Deployment/Build
      • How to?
      • How often?
      • Updates on build changes (new functionality affecting current tasks)
    • Ticket system
      • Concise, one line titles
      • Bullet point description
      • Internal link to relevant tickets
      • Commit linked comments
      • Time based tickets/tasks - ability for dev to add time tracking
    • Technical specification
      • Modules used broken down into features they implement
      • Modules present but not used and their role (development/staging...)

  • Project Management
    • Practises/Methodology
    • Resources/intro to methodology: don't assume they know
    • Implementation: format of scrum/standup (what's the difference)

  • Easy feedback solution needed
    • Independent of project

  • WHAT is the point... (especially if only a contractor! duh)
    • Visibility
    • Documentation
    • KISS ... avoiding over complications... 
    • Happy People, 
conclusion.