Mindtree community stories

About Stories

Stories on this page are the outcomes of various community initiatives and interactions. Since the community is driven voluntarily, passionate Mindtree Minds decide the community objective, identify gaps, chart out a roadmap, leverage different techniques and intervention models that benefit other like-minded members. This also helps them network with each other, stay connected, make friends and build trust.

We did a community survey and found out that 23% saw a great progress in the way community initiative has evolved in 2011. 8% said the community activities have made a direct impact in their work/project and it was a life saver for them. 47% noticed a positive impact (personally/professionally) on themselves as well as others.

Please click here to download the PDF version of our success stories


Community snapshots

Madhusudhan KM, Chief Architect of MindTree, facilitating an event on 'Rules of the Thumb do not Apply' for breakthrough applications. He gave examples of Skype, eBay, Twitter where the thumb rules did not apply.


Building Configuration Management Expertise for the Benefit of the Community

Building Configuration Management Expertise for the Benefit of the Community

Tech Leads Community

The Need

People understood the need for good configuration management in projects but never learnt it the way it needed to be applied. Stories ranged from, “Clients look up to us to own and streamline this complex landscape” to “We were struggling. Client escalated. We brought in an expert. Build stabilized.” There were fewer experts than we needed. Developers were not motivated enough to learn configuration management skills since the usage of the skills by project managers were not articulated properly. This also stemmed from the belief that configuration managers are not needed full time on projects.

A concerned community member thought:

“Why can’t we support projects to set it up right the first time?” Or even “How can we identify (and recognize) experts in different build automation tools and sustain an ongoing interaction around this topic?”

The Engagement

The objective of this engagement was to provide a detailed overview on how to approach and implement select areas in Configuration Management with a large project serving as context. The series was divided into 6 main areas, as outlined below. Scope, scenarios and takeaways were identified for each.

  • Context setting: Provided an overview of a large project, its project/program landscape, technical architecture, key challenges and its configuration landscape.
  • Source code repository: Dwelled into details of how source code is stored & structured.
  • SVN Branching approach: Elaborate why branching is implemented & how
  • Build Management & Continuous Integration: Elaborated why and how branching is implemented.
  • Building dependent projects: Explained the context of multiple projects, challenges & solution approach.
  • Release Packaging and Deployment: Elucidated the need for right packaging and demonstrated various deployment scenarios

The engagement lasted around 90 minutes each with hands-on demonstration of how a module/aspect works.

The Outcome

The event series got an overwhelming response. Approximately 240 members participated and got the opportunity to get insights in build automation. This included live examples & scenarios. Also, they were exposed to tools & techniques of how to do successful build automation in projects – irrespective of project size. Post event around 21 documents and 15 blogs were published. In addition 9 SMEs who used different configuration management tools were identified and felicitated. Some of the specific outcomes were:

  • Real project scenario of one of the large MindTree accounts showcasing complex configuration landscape & CM plan template.
  • Source code repository (SVN) configuration, folder structure, backup, selection considerations & working branching strategy.
  • Continuous Integration setup and its constituents. Showcased few sample build scripts.
  • Demonstrated working solution in ‘multiple dependent projects’ scenario.
  • Real life release situation that involves packaging and multiple deployment environments.

Tags: ,


Your email address will not be published. Required fields are marked *