1 www.scrumi ndia.in Date: 07 – 09 December Name: Manish Sinha ScrumIndia.In 2012 © Tata Consultancy Services Ltd. All Rights Reserved. Building High Performance.

Slides:



Advertisements
Similar presentations
The Road to Agile From the Bottom Up Kevin Malley Tracey Clark 1 March 20 th, 2013 SWOQG.
Advertisements

practicing agile development since 2002 csm x 4, cspo x 2 contracted ken schwaber taught agile to 100s agile alliance, acm, ieee mike cohn disciple delivered.
COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. 1 Agile documentation development methodology Giby Panicker and Judith Benjamin 1-Dec-2012.
<<replace with Customer Logo>>
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
NAUG NAUG Knowledge Evening – th February 2007.
Agile PM Basics Dr. Vijay Kanabar © Boston University
Muthu Swamy S, APSM, PMP, CSM, PM-2008 Friday, October 1, 2010
Rules of the Game  Loosely based upon the TV show, “Who wants to be a millionaire.®”  Once the question is read, you will have 30 seconds to discuss.
Agile development By Sam Chamberlain. First a bit of history..
EXtreme Programming Quick Introduction Daniel Arraes Pereira Eduardo Lourenço Apolinário Ricardo de Oliveira Cavalcanti.
Agile-SCRUM. Introduction to SCRUM Sanil Xavier What is Scrum?
Introduction to Agile.
Agile Methodologies for Project Management By – Komal Mehta.
PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.
Trusted IT Group. The challenge: 40 active, concurrent IT projects  Unsatisfactory Project Delivery.
Mobile Apps: Review and Retrospectives Refresher Agile Transformation Team 1.
Gaining Support for a Sustainable Agile Transformation Dennis Stevens, VP Enterprise Engagements LeadingAgile November 12, 2013.
Adopting Agile for Enterprise Software Joe Bedell, Software Engineer Jason Breen, Software Engineer Peter Melko, Scrum Master June 15 th, 2015.
Team Launch Introduction. Real projects are large and complex, and most software is created by teams Merely throwing people together does not result in.
Tuesday, June 8 th, Agile Development-Successful Delivery & Implementing Across the Enterprise.
Scrum’s Product Owner Role Jeff Patton Agile Product Design
“Kuality” Assurance What does that look like? Scott Heise Indiana University KFS - Quality Assurance Manager Paul Sandoval University of Arizona KRA –
Testing Challenges in an Agile Environment Biraj Nakarja Sogeti UK 28 th October 2009.
When is Agile the Best Project Management Method? Lana Tylka.
1 FROM DEVELOPERS TO ENGINEERS ENGINEERING ROLE IMPLEMETED AT EXPEDIA August 26, 2015.
Copyright © 2012 by Mark J. Sebern Scrum Overview (from
OFFICE OF INFORMATION AND TECHNOLOGY Mobile Applications Scrum Framework November 21, :00 am (EST) Seal of the U.S. Department of Veterans Affairs.
Theories of Agile, Fails of Security Daniel Liber CyberArk.
Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.
SCRUM.
Agenda: Overview of Agile testing Difference between Agile and traditional Methodology Agile Development Methodologies Extreme Programming Test Driven.
WHEN TITLE IS NOT A QUESTION N O ‘WE CAN’ CA Agile Vision Product Manager Michael Lester.
Agile 101. Feasibility Study SDLC – What is it? Systems Development Life Cycle: The most commonly used, and generally accepted, project management approach..
Agile Development Chapter 10 - part 2. Agile Philosophy  A guiding philosophy and set of guidelines for : developing information systems in an unknown,
Geoff Davis Software Development Leader Software Development at eWater.
Successful Software Practice How to successfully work as a team to create software Chris Mendes, Chief Technology Officer Sirca Limited March 2012.
 SBOK™ (SCRUM Body of Knowledge)  Student course workbook  Case study booklet  Scrum in a page  Scrum Product Owner Certified physical certificate.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Barnes & Noble Alonda Morgan. Agile UX Agile.
Business Intelligence in Classroom WHY:.  Purpose – knowledge to make an informed career decision  Process – Use Scrum method of project management.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum.
SCRUM.
Agile Training – Agile Overview
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum Project Transition Case Study
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Agile Software Development Brian Moseley.
Advantages OF BDD Testing
CEN 4010 Intro to Software Engineering Professor Alex Roque
CSCE 741 Software Process Lecture 04 Availability
Summarizing Our Models to Date
Scrum Overview.
Scrum - Plan a Sprint Great Video (but added release /sprint layer)
IS&T Project Reviews September 9, 2004.
Agile practices for documentation teams
Sprint Planning April 2018.
Introduction to Agile Blue Ocean Workshops.
Scrum Science NGSS: Engineering, Technology, Applications of Science
QA Reviews Lecture # 6.
Software Development In Agile
Scrum in Action.
Code Reviews Assignment Each team should perform a code review
Sprints.
Scrum From the
Agile product development
Software Development In Agile
Presentation transcript:

1 ndia.in Date: 07 – 09 December Name: Manish Sinha ScrumIndia.In 2012 © Tata Consultancy Services Ltd. All Rights Reserved. Building High Performance Distributed Scrum Teams Lessons Learnt & Best Practices Manish Sinha

2 ndia.in Date: 07 – 09 December Name: Manish Sinha ScrumIndia.In 2012 © Tata Consultancy Services Ltd. All Rights Reserved. Agenda What Scrum Expects? Team Structure - When We Started Challenges Restructured Distributed Teams Adapting and Innovating

3 ndia.in Date: 07 – 09 December Name: Manish Sinha ScrumIndia.In 2012 © Tata Consultancy Services Ltd. All Rights Reserved. What Scrum Expects?  Co-location of the team.  Effective communication (preferably face-to-face communication).  Frequent interaction between developers and end-users.  Daily stand-up meetings with all team members.  Self organized teams.  Inspect and Adapt.

4 ndia.in Date: 07 – 09 December Name: Manish Sinha ScrumIndia.In 2012 © Tata Consultancy Services Ltd. All Rights Reserved. Team Structure - When We Started Onshore/Near ShoreOffshore Product Owner Scrum Master Team 1Team 2 DEV QA BA DEV QA BA Proxy Product Owner QAPrimary responsibility of Tester DEVPrimary responsibility of Developer

5 ndia.in Date: 07 – 09 December Name: Manish Sinha ScrumIndia.In 2012 © Tata Consultancy Services Ltd. All Rights Reserved. Challenges  Highly distributed teams (Minneapolis, New Jersey, London, New Delhi, Mumbai, Pune and Lucknow)  Collaboration issues due to team members working in four different time zones  Less interaction of team with end user and Product Owner  High wait time leading to low productivity of the teams  Scrum Master can do little to resolve issues at offshore  Scrum Master not able to coordinate between teams during offshore timings.  Developing and maintaining high team synergy

6 ndia.in Date: 07 – 09 December Name: Manish Sinha ScrumIndia.In 2012 © Tata Consultancy Services Ltd. All Rights Reserved. Restructured Distributed Teams Product Owner Scrum Master Team 1 DEV QA BA Team 2 DEV QA BA Product Owner Scrum Master Team 2 DEV QA BA Team 3 DEV QA BA Scrum Master Team 1 DEV QA BA Onshore/Near ShoreOffshore Challenges:  Highly distributed teams  Collaboration issues BAProxy Product Owner QAPrimary responsibility of Tester DEVPrimary responsibility of Developer Challenges Handled:  Highly distributed teams  Collaboration issues

7 ndia.in Date: 07 – 09 December Name: Manish Sinha ScrumIndia.In 2012 © Tata Consultancy Services Ltd. All Rights Reserved. Restructured Distributed Teams Product Owner Scrum Master Team 1 DEV QA BA Team 2 DEV QA BA Product Owner Scrum Master Team 2 DEV QA BA Team 3 DEV QA BA Scrum Master Team 1 DEV QA BA Onshore/Near ShoreOffshore BAProxy Product Owner QAPrimary responsibility of Tester DEVPrimary responsibility of Developer Challenges:  Less interaction of teams with end-user and PO.  High wait time. Challenges Handled:  Less interaction of teams with end-user and PO.  High wait time.

8 ndia.in Date: 07 – 09 December Name: Manish Sinha ScrumIndia.In 2012 © Tata Consultancy Services Ltd. All Rights Reserved. Restructured Distributed Teams Product Owner Scrum Master Team 1 DEV QA BA Team 2 DEV QA BA Product Owner Scrum Master Team 2 DEV QA BA Team 3 DEV QA BA Scrum Master Team 1 DEV QA BA Onshore/Near ShoreOffshore BAProxy Product Owner QAPrimary responsibility of Tester DEVPrimary responsibility of Developer Challenges:  Scrum Master handling impediments at offshore.  Scrum Master coordinating between teams. Challenges Handled:  Scrum Master handling impediments at offshore.  Scrum Master coordinating between teams.

9 ndia.in Date: 07 – 09 December Name: Manish Sinha ScrumIndia.In 2012 © Tata Consultancy Services Ltd. All Rights Reserved. ADAPTING AND INNOVATING

10 ndia.in Date: 07 – 09 December Name: Manish Sinha ScrumIndia.In 2012 © Tata Consultancy Services Ltd. All Rights Reserved. Pass the Baton Day 1Day 2 Scenario  High business value PBI to be delivered within two weeks  Team estimates story points  Approx 15 working days (3 weeks) required for implementation Distributed SCRUM Teams Can Help - Just Pass the Baton 16 Hours of Work Team 2/3 IST Time Zone Team 1 EST Time Zone Team 2/3 IST Time Zone Team 1 EST Time Zone Pass the Baton

11 ndia.in Date: 07 – 09 December Name: Manish Sinha ScrumIndia.In 2012 © Tata Consultancy Services Ltd. All Rights Reserved. Create Team Interaction Forums Team Synergy Code and Scripts Review Ownership Deployment Ownership Weekly or Biweekly Check-in meetings  Create roles and responsibilities that mandates inter-team interactions.  Assign ownerships on rotational basis to ensure involvement of all team members from all SCRUM teams.  Have No-Agenda meets (preferably on Video­Con) that involves all team members..  Create “Culture of Appreciation”.  Celebrate Success Together!

12 ndia.in Date: 07 – 09 December Name: Manish Sinha ScrumIndia.In 2012 © Tata Consultancy Services Ltd. All Rights Reserved. Just Don’t Adapt - INNOVATE Apply Lean and become a high performing Scrum Team

13 ndia.in Date: 07 – 09 December Name: Manish Sinha ScrumIndia.In 2012 © Tata Consultancy Services Ltd. All Rights Reserved. Example - Reduce Analysis Time BA Briefing/Design Meeting  Explain documented requirement  Address QA and Dev needs  Examine feasibility  Identify potential dependencies and roadblocks  Create combined approach  Take expert’s advice  Identify collaboration required with third party Benefits  Forum for offshore teams to interact with onsite business analysts (closer to end user)  Faster QA and Dev analysis  Fosters team decision  Earlier identification of potential roadblocks  Ensures best design  Less effort spent on s\wiki communication These activities are also part of planning meetings but are performed here in more detailed manner with more specific audience (only those team members who are expected to be working directly on a backlog item or a technical\functional expert). QA BA Expert (Tech\ Functional) DEV

14 ndia.in Date: 07 – 09 December Name: Manish Sinha ScrumIndia.In 2012 © Tata Consultancy Services Ltd. All Rights Reserved. Example - Reducing Wait Time (Lean) Start Team starts working on PBIs Document Requirements for PBIs Developers send query to Business Analyst Development work completed as per BA comments QA Queries to BAs QA Testing completed as per BA comments Fix defects found in BA Testing Final BA Testing & Close PBI Final BA Testing & Close PBI BA Testing 6.0 hr hr 2.0 hr 0.25 hr 1.00 hr 0.5hr 0.10 hr WWWWWWWW 4.0 hrs 0.1hr 0.25hr 2.0hrs 0.5hr Non value added activity Value added activity Wait Time Processing Time Total Wait Time Hours

15 ndia.in Date: 07 – 09 December Name: Manish Sinha ScrumIndia.In 2012 © Tata Consultancy Services Ltd. All Rights Reserved. Example - Reducing Wait Time (Lean) (Contd..) Start Team starts working on PBIs Document Requirements for PBIs Developers send query to Business Analyst Development work completed as per BA comments QA Queries to BAs QA Testing completed as per BA comments Fix defects found in BA Testing Final BA Testing & Close PBI Final BA Testing & Close PBI BA Testing 6.0 hr hr 2.0 hr 0.25 hr 1.00 hr 0.5hr 0.10 hr WWWWWWWW Non value added activity Value added activity Wait Time Processing Time 0.1 hr 0.25hr 0.1hr 0.5hr Total Wait Time Hours

16 ndia.in Date: 07 – 09 December Name: Manish Sinha ScrumIndia.In 2012 © Tata Consultancy Services Ltd. All Rights Reserved. Q & A Questions and Answers?

17 ndia.in Date: 07 – 09 December Name: Manish Sinha ScrumIndia.In 2012 © Tata Consultancy Services Ltd. All Rights Reserved. THANK YOU