On-boarding Experiences, Lessons, and tactics from Prowareness Software Development Center Bangalore by Marudhamaran Gunasekaran.
Screen recording at - https://vimeo.com/gmaran23/HowToKickStartANewScrumTeam
Event Details @ http://www.agileacademy.nl/event/?eventtitle=agility-hr&utm_source=CustomMail&utm_medium=LeesMeer&utm_campaign=LeesMeer
How to Kick Start a New Scrum Team - Agility and HR at Delft Netherlands 21 January 2016
1. What we have learnt..
Agility & HR, Jan 2016
@
Delft, Netherlands
How to Kick Start a New Scrum Team
Screen recording of the presentation at - https://vimeo.com/gmaran23/HowToKickStartANewScrumTeam
6. To manage complexity or to control chaos –
Splits time into slices (Iterations) and provides opportunities (Events) to
compare reality with expected outcome (Feedback)
• Frequent Inspection and Adaption based on transparency
Agile and Scrum
7. For complex and adaptive software development
A framework of principles, roles and rules that thrives on people doing Scrum
Is very much about behavior, much more than it is about process
Is hard and disruptive
Scrum
8. Is it about finding the right people?
Or
Is it only about finding the right people?
Scrum, people, behavior, and company culture
16. Training helps – but;
Is it tangible?
How to quantify or validate someone’s learning?
17. Build an onboarding – How?
Set expectations - define boundaries, define goals together
Intensify the feedback cycles - as frequent as possible
Create team environment - bring them together on a common purpose
Equip with the tools - they are comfortable working with
They like to be challenged - give them one & leave the room, however be available and approachable
Create roles (Scrum) within the team - and hold them accountable
Validations for learning - quiz, assessments, real software itself, recap, homework
18. Set expectations: ProX – Prowareness Experience
before they join, call them for an office tour
facilitated by the existing employees and the recruiters
20. Intensify the feedback cycles
At least once per day
Transparent feedback
Based on evidence
Direct feedback
Facilitate feedback circle within the team
22. Transparent feedback – Self Evaluation
Remember: Feedback is about providing information
23. Transparent feedback – Progress in 3 months
After the one month Pro-Seed (Induction) program, meet with them every
fortnight
24. They like to be challenged
Engineers like to design, create and build systems
Create a backlog of challenges that software could solve
(Operations automation, POC for a new business idea, … )
Real world challenges – identify them or ask other software teams
that do not have time to work on some dream features
Throw a challenge at them, and visit after a couple of hours
26. Create team environment
A dedicated team room
No individual cubicles that impede communication in the name of privacy
Make the team accountable for a software creation
Create Scrum roles
Product Owner
Scrum Master
Cross functional Development Team
28. “Pair programming is a social skill …... You are striving for a cooperative way to
work that includes give and take from both partners regardless of corporate
status”
Pair them
http://www.extremeprogramming.org/rules/pair.html
“The best pair programmers know when to say
"let's try your idea first." ”
29. Equip with tools
Computer configuration with their preferred operating systems (Windows or
Linux)
High resolution dual monitors
Software and frameworks access
IT person and Scrum Coach at their disposal
tactics and cheat sheets
31. Scrum Coach
Coach them at their Scrum Events
Facilitate tip and tops, instill it as a habit
Always be available and approachable
32. Validations for learning
Assessments (Not the Yes or No type)
Assessments with open ended questions that require descriptive
answers
Provide some homework
Recap the next day
Let them teach
35. Learning tactics – presentations – make them the
tutor
If they are uncomfortable doing it, it is even better – they just spotted their area of improvement
