1. Copyright BSPIN 2009 1 Agile Practices Benchmarking Case Study by Cosmonet Solutions Pvt. Ltd. www.cosmonetsolutions.com

2. Copyright BSPIN 2009 2 About Cosmonet  IT services and product company headquartered in Bangalore  We design, develop and deliver tailored IT solutions for leading companies around the globe – Switzerland being main market  60 employees contributing to our growth and success  Sustained high Quality has been the key to Cosmonet’s success  More than 10 years of excellence with success stories  Quality and Process driven – CMM level 3 practice  Focus on Insurance and Manufacturing verticals  Contact person: Raveesha@cosmonetsolutions.com

3. Copyright BSPIN 2009 3 Agile Penetration @ Cosmonet Agile Related Information Type of Project Product Development : TOPQM – Quality and Project Management Suite for Monitoring Projects Domains Project and Quality Management Technologies.NET 3.5, SQL Server 2008 Number of Projects & % of Projects 3 Projects are using Agile Methodology Agile Institutionalized since October 2010 Key success factor 1 Improvement in efficiency of team members Key success factor 2 Product development got faster Key success factor 3 Motivation and Collaborative working of all stake holders

4. Copyright BSPIN 2009 4 Agile Execution @ TOPQM Project NameTOPQM Project Size 1 Product Owner, 1 Scrum Master, 5 team member including one dedicated tester who writes test cases for valid user stories for each sprint. The user stories are ranked based on the priority levels. Stories are written by the team with the guidance of PO and reviewed by the PO. Project Structure Product Backlogs are prepared by PO and user stories are compiled with all the team members. Then these user stories are taken in a sprint(14 working days) along with the test cases for each detailed user story. Agile Approach Scrum & XP Agile Practices Currently in TOPQM, the team follows sprint/iteration, Standup meeting, continuous integration, Automated build process and sanity testing, code refactoring and at the end of the sprint demo and retrospection Agile Metrics Burn down chart and source monitor tool for code quality metrics. Agile Skills Better coordination with the team technically and more accountability Why Agile in this project To induce more ownership, remain focused and to take the product forward

5. Copyright BSPIN 2009 5 Measurement and Analysis MetricsCriteriaAnalysisResults Product progress Measure daily progress of the Scrum team of the for a particular sprint Daily stand up meetings during the sprint, burndown chart Team could honor in accomplishing the Committed tasks within the sprint time frame. Code quality Number of linearly independent paths through a program source code like functions, properties, classes etc.. -No of lines of code, - commented lines, - % of comments, - classes, - methods/classes, - calls/methods, - max complexity, - max depth, - average depth, - average complexity Through source monitor(2.6 version) we were able to reduce the cyclomatic complexity. Acceptable limits are 20- 25.

6. Copyright BSPIN 2009 6 Challenges & Solutions Focus AreasChallengesSolutions Scope and estimationTo understand the scope of the development with granular details and also have a realistic estimation of schedule User stories were developed and reviewed by the stake holders. All the team members who are part of particular sprint should be part of the scope and estimation so that the end objective is met and mitigate the risks PeopleMotivation and Accountability.Each team member is the part of every step and that helps to induce the ownership and accountability. Product / Process QualityMaintainability and code qualityDeployment of peer reviews, measurement of code complexity, periodic retrospection. Tools / TechnologyNot exposed to usage of tools and automation. Tools were identified and used for quantification of code complexity, build scripts were introduced to have daily integration and builds, test cases were automated to reduce the manual testing CustomerMeet the customer expectations in terms of scope (functionality), speed up the development Customer’s inputs were taken at the time of creating user stories, sprint demos helped us to secure the feedback in quick succession and adapt them swiftly. PracticesTendency of following waterfallSCRUM & XP MetricsNo clear cut definition and fear of individual performance Global metrics are collected to avoid individual insecurity. Burndown chart and Velocity are tracked to assess the team performance

7. Copyright BSPIN 2009 7 Limitations & Recommendations Focus AreasCurrent LimitationFuture Recommendation Scope and estimationImprove the estimation and meet the customer expectations with lesser gaps. More elaborative user stories to be created. Customer’s involvement to be enhanced. Retrospection feedback to be taken into consideration. Carefully analyzing the burn down charts and velocity charts, estimation to be refined to attain more realistic estimates. PeopleTo understand Agile further and adapt more of Agile concepts and methodology Use of Agile training from time to time, participation in Agile conferences and Forums Product / Process Quality Lack of Agile awareness and minimum process and product mindset The entire development teams across the company should embrace Agile methodologies Tools / TechnologyNewer technologies on Web, test automation Apart from normal testing, the testers will be able to value add by learning test automation techniques and new development skills CustomerAgile awarenessAgile awareness should be given to the customer and customer should be made part of the entire process all throughout the sprint PracticesRetrospection meetings to feed the input to the process and practice Record the retrospection and use some Agile tools for tracking them. MetricsSprint Burn down chartsvelocity tracking,Effort Trend

8. Copyright BSPIN 2009 8 Few Highlights..  Total sprints covered so far : 7  Total user stories implemented : 300  Total retrospections : 7  Total efforts in 7 sprints : 2,500 hours  No. of Test cases automated using Selenium RC automation tool : 500  Testing time reduced from 12 person hours to 2 person hours due to automation

9. Copyright BSPIN 2009 9 Significant Benefits  Helped to remain focused  The product could surely move forward in terms of futures  The development got aggressive  Team’s motivation increased and team members took full ownership  Test case automation helped us to increase testing speed and quality  Customer escalations reduced – Bridged the expectation gap  Helped us to understand Agile methodology fully with self experience  Our sincere thanks to – Opcord who helped us to achieve this

10. Copyright BSPIN 2009 10 THANK YOU!