TEAM SHARING
once per iteration, on Thursday at 2PM 14.00-15.00 in the second week
non-technical, high-level, aimed at everybody in the team
- providing context for TIS work within HEE / NHS
- providing insight into what makes team members tick (see ‘About me’ section)
TECH SHARING
at least once or twice every iteration, no fixed slot allocated
technical, code-heavy, dev-focused
- an element of continuous professional development
- to help turn us from “I” shaped into “T” and “M” shaped people
At the beginning of each iteration, during PLANNING, there should be a moment dedicated to reviewing the Team Sharing and Tech Sharing pages to:
schedule highlight what will be covered in the upcoming iteration’s Team Sharing @ 2pm on the ‘off’ week
schedule the upcoming iteration’s Tech Sharings
based on tickets in
Ready for Developmentthat would be great to mobbased on what devs expressed an interest in , if somebody has such knowledge to share(check the Tech Sharings confluence page - there’s a suggestions box of things people want to talk about and want to know about)
based on the findings of a spike ticket
based on team members attending courses
may be impromptu, if the opportunity arises mid-iteration
Look to record somewhere in the new Trainee Information Systems Sharepoint site (Tech_Sharing folder) what's being shared in a Tech Sharing so that such knowledge doesn't get lost in time. Ideally, a result of
One of the outputs from a Tech Sharing should be the transcription of such knowledge into a service's Readme or Dev Handbook, lest so we need don’t have to have the same Tech Sharing time and time again for newcomers.
Endeavor Endeavour to protect Tech Sharings from other conflicting meetings where possible. Tech Sharings may interest only a handful of people, but the rest of the team should try not to schedule something else that may be interesting to those who are on the Tech Sharing, unless reasonably unavoidable.