Application Lifecycle Management (ALM)
What is Application Lifecycle Management
Application Lifecycle Management is the software lifecycle from governance, development, and maintenance of a particular software application. At TEDI we’ve been exposed to various methods and models in both the private sector and government. The primary method’s we have performed include CMMI, Waterfall, AGILE, and AGILE/SCRUM. Our background and capability allows us to be flexible and adaptable to any method. In addition, our extent of tool exposure to enforce these lifecycles range from Team Foundation Server (TFS) to Mercurial, Git, GitHub and more. We pride ourselves on the development knowledge and experience we deliver.
Utilizing our Combined Lifecycle Model (CLM), TEDI approaches complex IT challenges with a structured step by step strategy for .NET, infrastructure, or ALM solution.
ALM Method & Tool Proficiency
Our capabilities surrounding our ALM method proficiency and ALM tool proficiency is vast and intricate. TEDI has installed, configured, and implemented various tools and methods for clients in many industries. Our specialization is to provide a full scale ALM capability which Microsoft and TFS provides, however, many organizations utilize many resources to accomplish their individual ALM strategies. Therefore, we ensure to keep up on the latest technologies and tools for development. We pride ourselves on the adaptability we deliver and utilize what we have learned over years to both our clients and our internal product development.
- AGILE 100%
- AGILE/SCRUM 100%
- Waterfall 90%
- CMMI 100%
- Team Foundation Server 100%
- GitHub 100%
- GIT 95%
- Mercurial 95%
- JIRA 100%
Our Most Implemented ALM Methods
CMMI for Development
Our development efforts utilizing CMMI has been focused around DoD and US Federal Agencies. This process has been in use for numerous years and used to assist in improving processes surrounding the development effort. Integrated directly into Team Foundation Server (TFS), CMMI has been a template process we have deployed on numerous occasions and customized to address specific requirements for DoD and Intelligence Community (IC) development efforts. In recent years we have noticed a trend of DoD and US Federal Agencies moving toward Agile methods with integrated CMMI components. These “Hybrid” methods have also proven highly effective. In either case, TEDI has worked closely with US Government Agencies to ensure efficiency regardless of how the process has evolved.
SCRUM is defined as an iterative software development framework for managing software projects and application development (Wikipedia). SCRUM, like Agile, supports an iterative approach that is flexible and capable of changes during sprints. Depending on the size and complexity of the development effort several key roles are defined throughout the process. We have our development team, environment team(s), Scrum Master, Project Manager, Build Master, and Tech Lead. Some players can combine roles such as Scrum Masters with Build Masters (etc), all depending on the size and complication of the engagement. Our Product Backlog contains all high priority requirements or user stories or use cases and the “parking lot items” (nice-to-have’s). The complexity of the engagement generally dictates the lengths of the Sprints and we attempt to keep an effort at 5 Sprints but this has extended for larger, more complex development operations. Amongst all of the development models, SCRUM is the most widely used amongst TEDI clients and the method used for internal development efforts.
Microsoft defines Agile as focusing on individuals, interactions and customer collaboration that is responsive to change to produce working software. Agile processes promote sustainable development by teams of motivated individuals providing incremental delivery of technically excellent working software in short iterations. Business people and developers work together daily, embracing change for the customer’s competitive advantage. Within TFS, our primary difference between SCRUM and Agile is the use of User Stories, which is unique to the Agile process template.
ALM Implementation with Team Foundation Server (TFS)
TEDI’s primary demand when implementing ALM strategies have been around Microsoft’s Team Foundation Server. Unlike other ALM tools, TFS provides full lifecycle support with code repository, testing, and collaboration tools. TFS offers the gamut of functionality to support any small or large team the efficiency of an ALM tool. And unlike other tools on the market, TFS can be customized to any development effort or niche requirement for software development shops. TEDI lives and breathes TFS both in supporting clients and our products we prepare for patent and market release. Recently, TEDI has moved to TFS Online and performs cloud ALM strategies to support development teams with global needs for collaboration.