Why Does Your Enterprise Need a Git Strategy?

Git is the world’s leading distributed version control system (DVCS). Developers praise Git for its flexibility, local access speed, and powerful branching and merging capabilities. Git has already become a mainstream technology for individual developers, open source projects, as well as small companies. Large and geographically distributed enterprises also increasingly believe that Git represents an opportunity for speeding up the development process. Even when enterprise organizations are happy with their legacy source control solutions (such as Subversion), it is hard to avoid the presence of Git in development environments. Also, the use of open source libraries often makes it inevitable for the enterprise to at least become familiar with Git.


Effective SCM Strategy for the Modern Enterprise

Today’s organizations need to consider many factors when defining a Software Configuration Management (SCM) strategy for modern world-class enterprise software development teams. Over the past several years, organizations have been affected by new market forces that were hard to foresee a decade ago when the current SCM landscape was forming: decentralized development teams, increased use of short-term and remote workforce, greater concerns over intellectual property protection, growing complexity and costs of compliance audits, and increased demand for managing risks. The combination of these seemingly unrelated forces have created unique technology and business challenges for enterprise development organizations.


Making Git Safe for the Enterprise

Take Control of Git’s Obliterate Feature and Get Security and Compliance

Did you know that Git breaks with one traditional paradigm of all other version control systems:

Sacrificing immutable commit history for greater developer flexibility and the possibility to remove problematic content forever (obliterate feature). From a management perspective, that’s a security and compliance risk.


Scrum Reference Card

This single document provides a six page summary of Scrum. What are the roles that are defined by Scrum? What are the meetings that are part of the Scrum approach? What are the Scrum artifacts (documents, lists, reports) that are most helpful? How is Scrum related to other programming approaches? What is self organization? This is the perfect document to use as a quick reference card when you are just getting started with Scrum, or as a quick overview to people who are interested in the mechanics of how Scrum works.