Saturday 22nd February, 2014
2:00pm to 2:45pm
It is now common to hear about IT organizations kicking off big Agile transformations. While there is a lot of training offered on how to improve the delivery process, culture change and mindset shifting, people are not prepared on how to shift their roles. In traditional environments, everyone has a clear job description that explains their function and what they should/shouldn't do. In a functional role, it is clear from whom to receive the work and where to send it after a certain expertise/skill is applied. In Agile, all these roles change to "Agile Team member". What does a Team member do? What is the job description for this role? How can someone use the previous skills and expertise under this new role? What University Degree do I need to be "Product Owner", one of the "3 Amigos", "On-Site Customer"? And why does everyone talk about collaboration?
This session will focus on these questions. I will talk about the Roles in Agile, how to create an Agile Team (T shaped people) out of traditional roles (I shaped people) such a Tester, Business Analyst, Developer, Solution Architect, Database Admin, Business Project Manager, Project Manager, Operations Engineer, etc. I will explain why collaboration is the key that opens a lot of doors for people to use their skills and learn new ones, create roles that do not exist yet and grow professionally.
You will also have a chance to participate on an exercise to build an Agile team by using functional roles from traditional environments. You will be the one to decide on these roles, based on the skills required to deliver Value.
Sign in to add slides, notes or videos to this session