Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

SCM Team Strategy

This is an outline of where I want to lead the SCM team in the coming months and years.
by

Chris Evers

on 22 April 2010

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of SCM Team Strategy

The SCM Team Strategy What is our purpose?
What are our goals?
Where do we fit in?
What are our achievements to date?
What are our challenges?
How will we succeed?

Current Team Structure Karey Chris BAU
ClearCase Support
Legacy Buids
First point of contact Planning for new projects
Assisting in SCM plans
Reviewing new build solutions
Assisting new build solutions
Team Leader tasks
This structure has enabled Chris to implement some new standards for .NET apps and new project.
We have established defined processes.
Chris has been able to establish relationships with projects to ensure quality build solutions.
We have introduced a new cental build management solution to ensure that all new applications will have automated one click builds in the future.
We have assisted in automated EAI builds. Is this the BEST way to assign our team NOW? It may be time to shake things up a little.
Chris needs to become more knowlegable in the legacy systems, so that when karey is away there is little impact.
Karey needs to be more knowlegable of the new projects and how they build and will probably have some great ideas for improving the work Chris has done. Karey Hudson Support
.NET Build Support
ClearCase Upgrade
SCM Plans Chris BAU
ClearCase Support
Legacy Buids
First point of contact
Team Leader Tasks What is our pupose? 1. Provide Version Control tools and support 2. Manage Software Compilations 3. Manage Software Deployments 4. Provide Software Change Management We Support and Maintain:
ClearCase
ClearQuest
SVN
VSS
TFS
We are responsible for choosing the most appropriate tools for the company and supporting those tools.
Our goal is to be experts in the SCM tools we use at SuperPartners.
We make sure each team is using a correct code base.
We identify and support the code merging needs.
What are our goals? 1. Upgrade ClearCase/ClearQuest 3. Automate Builds 4. Automate Deployment 2. Take Ownership of TFS 5. Automate BAU Processes Where do we fit in? Software Configuration Management is fairly new to this company, and until now the lines between software development and SCM have been quite vague.
Lets define SCM for SuperPartners 1. We are a service to developers and testers 2. We are a software compilation experts 3. We are a middleware experts 4. We always consider whats best for the enterprise Build Scripts The SCM team takes ownership of all approved build/compile scripts once a project transitions into production.
The entire build process must be appoved and documented in an SCM Plan.
The SCM team is here to offer advice for projects building new components.
Why? Becuase the SCM team manages builds for the enterprise. What does "Build" mean? Build means a lot of different things, even in this organisation. In the SCM team "Build" only has one meaning which is to compile code into a build pack ready for a "Deployment". Deployment Scripts The SCM team takes ownership of all approved deployment scripts once a project transitions into production.
The entire deployment process must be appoved and documented in an SCM Plan.
The SCM team is here to offer advice for projects deploying new components.
Why? Becuase the SCM team manages deployments for the enterprise. What does "Ownership" of scripts mean? Ownership of a build or deployment script means that we are responsible for running, maintaining and improving a script. We are responsible for understanding how the script works in order to offer IT Ops the ability to perform root cuase analysy on any errors or failures that might occur. Task breakdown Initiation In the initiation of a project, or change the SCM team is engaged to do the following:

Consult with the change owner or PM about the SCM process
Constult with the change owner or PM about the SCM Plan
Approve the SCM Plan, or
Work with the development team to improve the SCM solution, and approve the documented solution in the SCM Plan Compilation In the compilation of a project, or change the SCM team is engaged to do the following:

Maintaining Hudson and/or any other enterprise build tool
Offering support for failed builds
Running all legacy builds
Auditing Version Control tool usage
Development In the Development of a project, or change the SCM team is engaged to do the following:

Providing support for the version control tool
Providing the correct baselines of code
Managing change management tool when code has been merged
Assist with any automation/ build/deployment scripting issues Deployment In the deployment of a project, or change the SCM team is engaged to do the following:

Assist release management by managing changes in Change Management tool
Manage and apply all deployments to test environements Production Project Involvement Projects will be run independantly of the SCM team, however they will not run as a black box.
In order for a project to move into a test environment their entire SCM process must be documented and agreed, afterwhich the SCM team will take responsibility for any builds or deployments needed into the test environments.
Projects are responsible for implementing the agreed SCM solution
If a project is delivering a green fields application, the SCM team will need to be resourced into the project to develop the SCM solutions
Chris the "SCM Guy" The SCM Team approves the methods of sofware compilation, and manages any builds needed for test environments or App Support and OI.
All projects must follow the SCM Teams standards
SCM team maintains all build scripts once the scripts have progressed into test and into production.
The SCM Team approves the methods of sofware compilation, and manages any builds needed for test environments or App Support and OI.
All projects must follow the SCM Teams standards
SCM team maintains all build scripts once the scripts have progressed into test and into production.
We work closely with release management to make sure that ONLY the approved and tested content progresses into each environment and ultimately into Production.

We currently use ClearQuest as our Change Management system. Upgrading ClearCase and ClearQuest is out number one priority. It will enable IBM to support out most important version control tool, will improve build times (by installing on new hardware) and it will enable .NET support.

The key business drivers are:
ITOPS Tactical Plan
Retiring HPXMel26
Supporting Windows 7
Improving CC/CQ usage
Our role in assisting Release Management with Change Management is hindered by the fact that we currently do not have any visibility of change sets or work items in TFS, the version control tool used by Project Delivary.

The SCM Team needs to take ownership of TFS, and deliver either a Change Management lifecycle tempalte for use by both waterfall and Agile project, OR an integration with ClearQuest/ The SCM Team has delivered an SCM policy that states that all builds must be automated. We have also delivered a build management system along with standards that allow for projects to use Continuous Integration or standard build methods to build their software over any platform on any technology.

When the SCM team has capacity we will revist the automated builds of all the applications we manage and bring them all up to our new standards. The SCM Team has delivered an SCM policy that states that all builds must be automated. We have also delivered a build management system along with standards that allow for projects to use Continuous Integration or standard build methods to build their software over any platform on any technology.

When the SCM team has capacity we will revist the automated builds of all the applications we manage and bring them all up to our new standards. The SCM Team has delivered an SCM policy that states that all builds must be automated. We have also delivered a build management system along with standards that allow for projects to use Continuous Integration or standard build methods to build their software over any platform on any technology.

When the SCM team has capacity we will revist the automated builds of all the applications we manage and bring them all up to our new standards. What are out achievements to date? Running BAU and Supporting Development
Developed one click vanilla deployment solution in Autosys
Defined an Enterprise SCM Policy
Defined an end to end SCM process
Developed SCM Plans for the enterprise
Instrumental in developing Enterprise Release Management Process
Introduced Hudson to the enterprise as a Build Management Tool
Assisted all new Support, OI and Projects to use Hudson and Autosys Deployments
Assisted MSS project with development of one click installations
Assisted EAI developers to develop CI model for EAI Where do we spend our time? Running Database Builds
Running Database Deployments
Running EAI Deployments
Running .NET Deployments
Root Cause Analysis on Build/Deployment issues
Reviewing SCM Plans
Consulting with projects about SCM plans and process
Developing SCM solutions with projects
Reviewing Build/Deployment scripts
Managing changes (release management) in ClearQuest
Process Improvement (mainting scripts, maintaining software including upgrading Version Control tools like ClearCase/ClearQuest
Version/Build/Change control tool support to developers
Database refreshes after major builds


Full transcript