Scrum Transition Stories by Ajithesh Hegde

scrumindia

Download

Post to :

URL :

Related Presentations :

Add to Flag Embed

Views: 119

Category: Science & Tech..

Presentation Description

No description available.

Comments

Presentation Transcript

Story of a successful Scrum Transition:

About the Presenter:

About the Presenter Name – Ajithesh G. Hegde An independent Agile Trainer/Coach/Consultant Has an industry experience of 18+ years Graduated from KREC, Surathkal (now NITK) in 1992 Worked for C-DOT (4+ yrs) and Motorola (13 yrs) Worked in the Telecom Domain PSTN, ISDN, Call Processing, Fault Tolerance, GSM/GPRS, 3G UMTS, ECMA Initial 13 years in the regular technical and leadership roles Last 5+ years in Process Improvements including Agile/Scrum Training/Consulting Agile/Scrum Training, Coaching and Consultancy in Motorola, India Agile/Scrum Training at Mphasis , Bangalore and Operative Media Ltd., Bangalore Copyright © 2011, Ajithesh G. Hegde, All Rights Reserved 2

Project specifics:

Project specifics Telecom project Mobile handset protocol and signalling application modules Involved two sub domains Distributed development over 3 locations Involving US and India Involving 20 to 25 developers (excluding UAT testers) A span of 6 to 7 months Copyright © 2011, Ajithesh G. Hegde, All Rights Reserved 3

My Role:

Beginning:

Beginning Earlier AdHoc Agile implementation Triggered interest in Agile Started reading and understanding about Agile Discussions with and Presentations from Agile experts AdHoc implementation set a wrong impression about Agile with Management team Copyright © 2011, Ajithesh G. Hegde, All Rights Reserved 5

Initial Approval:

Initial Approval Management Buy in Presentation to India Manager and buy in The India Manager acted as the management sponsor for rest of the venture Presentation to the client in US and buy in Approval received for: Adoption of Scrum and Some XP practices Specific XP practices were decided later Copyright © 2011, Ajithesh G. Hegde, All Rights Reserved 6

Scrum teams:

Scrum Teams:

Scrum Teams Independent Scrum Masters in each location ‘Scrum of Scrums’ across locations Overall Product Owner in US Domain level Product Owners in Blore and Hyd Overall Product Backlog Split into domain level product Backlogs Copyright © 2011, Ajithesh G. Hegde, All Rights Reserved 9

Initial Training and Kick-off:

Initial Training and Kick-off Separate training at each location of: Bangalore Hyderabad US Agile Process Document drafted (Just enough documentation) Sprints planned The first sprint kicked off Copyright © 2011, Ajithesh G. Hegde, All Rights Reserved 10

XP practices:

Constraints and Limitations:

Constraints and Limitations Single Product Owner sitting in US Domain teams spread across: Blore and US Hyd and US High level Dependency on external team Poor API documentation No frequent access for clarifications Copyright © 2011, Ajithesh G. Hegde, All Rights Reserved 12

Deviations in Implementation:

Deviations in Implementation ScrumMaster also acts as Product owner Proxy ScrumMaster has some direct reports in the team Product Owner never participated in Sprint Planning Sprint review (excepting for sprint 1) Not much process rigor in US Process rigor in that order: Blre (Highest), Hyd , US UAT did not happen as part of sprints Copyright © 2011, Ajithesh G. Hegde, All Rights Reserved 13

Deviations in Implementation:

Deviations in Implementation Sprint Review happened only for Sprint 1 Interruptions in several sprints Due to clarifications in API interfaces Due to unavoidable spurious requests 20 to 40% disturbance in the planned activities Only Designs were completed in some sprints Iterative but not truly Incremental Incremental visioning was only partially done Tasks were estimated in days as opposed to hours Copyright © 2011, Ajithesh G. Hegde, All Rights Reserved 14

+ve things in Implementation:

+ ve things in Implementation Agile coach co-located with team in Blore Sincere adherence and cooperation from Blore team Observed all Scrum practices religiously Team once tried daily scrum on alternative days and reverted back to daily meetings Scrum of Scrums happened religiously Copyright © 2011, Ajithesh G. Hegde, All Rights Reserved 15

Benefits:

Benefits Team found immense value and benefit in all Scrum meetings New engineers : Felt at ease due to communication Found Seniors more accessible Received implicit training Copyright © 2011, Ajithesh G. Hegde, All Rights Reserved 17

Benefits:

Benefits Huge gains in Quality! Reduction in externally found defects: By a huge factor of 3.5 to 6.5 as compared to non-Agile projects Reduction in design faults By a huge factor of 10!! Attributed to Design Brainstorming Pair Programmed code Quality is much superior Faults less by a factor of 2.5 as compared to non-Pair Programmed code Copyright © 2011, Ajithesh G. Hegde, All Rights Reserved 18

Coaching/Consulting needs:

Coaching/Consulting needs Without the coach/consultant, this would not have been a success The team would have abandoned Agile and gone back to the earlier process Initially, there was a lot of resistance in the team Daily Scrum was looked at as a regiment, an added discipline , a new ceremony A lot of handholding happened in the beginning Copyright © 2011, Ajithesh G. Hegde, All Rights Reserved 19