Bridging the gap between your Agile project organisation and the traditional HR department
-
Upload
siddhi -
Category
Technology
-
view
1.614 -
download
1
description
Transcript of Bridging the gap between your Agile project organisation and the traditional HR department
Bridging the gap between your Agile Project organization and the traditional HR department
_________________________Thushara Wijewardena
CPO@ Exilesoft
Presented @ Agile2012- Bangalore
Production/Project organization
Sales
Other Facilitating organizations
h
Production/Project organization
Sales
Other Facilitating organizations
h
http://www.amazon.com/Start-Why-Leaders-Inspire-Everyone/dp/1591842808
http://www.amazon.com/Start-Why-Leaders-Inspire-Everyone/dp/1591842808
http://www.bized.co.uk/educators/16-19/business/hrm/lesson/hrm1.htm
Case Study
Case Study: Agile adoption at Exilesoft
2008 2009 2010 2011 2012
15 people 40 people More and more
Evolving with agility… D S
70 people
Organization culture was challenged
Control culture Collaboration culture
Competence cultureCultivation culture
Day to day functions were challenged
1.Beware of individual performance reviews 2.Pair-programming is a great way of recruiting
developers3. Certificates are not that important for software developers4. Shorter feedback loops than once a year feedback5. Job Descriptions may create confusion among the developers6. NO NO they don’t report to the scrum master…
Created disrespect
Effect:organization wide performance drop.
Everyone felt the “stress”
Looking at the organizational
picture
Fact finding & Route cause analysis
Common patterns and causes
Covered under: Section II The problem and
Section III The causes
E-ISBN: 978-0-7695-4370-3 Print ISBN: 978-1-61284-426-8
Findings- Isolation and lack of transparency- The meaning of “agile”- Requirements are thrown over the wall- Too much of working progress tasks- Lack of recognition and trust
Customer Project Organization
Human resource
Proposed Solution
Improve the knowledge of agile concepts among HR staff
Agile implementation
Observing the Results
Transition
Feasibility of implementing KANBAN over Scrum
Looking at Scrum
• Time boxing• Scheduled releases • Story point estimation• Sprint burn down • Team consistency
Looking at KANBAN
KANBAN wall
Backlog
Definition of “Done”
Done =
Complexities
We are no more a software factory
Today…
Before..
After..
Twitter : @[email protected]