Comprehensive software reviews to make better IT decisions
New Features and Enhancements Come With TeamForge’s Latest Release
CollabNet TeamForge ensures development governance, compliance, and standards are maintained whether an organization is using Agile, Waterfall, or hybrid software methodologies. This platform supports a team’s automated delivery pipeline and workflows by enabling integration with third-party and open-source tools, such as Jira, Jenkins, Chef, Git, and Subversion.
Source: SoftwareReviews, Accessed January 31, 2020
CollabNet’s suite of products (such as GitAgile and Continuum) and integration partners complement TeamForge’s delivery management features. The 2017 merger with VersionOne brought a much-needed capability to the CollabNet ecosystem: enterprise portfolio and program level Agile lifecycle management, which many vendors in the ALM space do not have. Industry has yet to see how the recent acquisition of CollabNet VersionOne by TPG Capital will influence and steer the evolution of CollabNet’s flagship products.
The TeamForge 19.3 release has a number of new features and fixes that were deployed in two separate updates, including:
- Addition of the “Documents” widget to the “My Workspace” page
- Attachment reminder for Tracker Artifacts
- Download folders from a Git repository
- Audit/Change log for file releases
A notable new feature of the previous TeamForge 19.0 release is the Project Baseline, which represents an approved snapshot of selected configurations items from a given TeamForge project at a given point in time. This new feature assists in the root cause analysis of changes that occurred after a release or milestone and can serve as a starting point for the extension of the current project or start of a similar new project.
CollabNet offers a solid ALM solution that is well suited to companies who aim to streamline the development and delivery of products and changes. TeamForge’s technology partners (e.g. IBM, Microsoft, HP) enable interested organizations to build an integrated toolchain, and CollabNet’s merger with VersionOne extends software development up into the business.
Want to Know More?
Traditional accounting practices are tailor made for waterfall project management. Organizations that have transitioned to the use of standing product teams using Agile and DevOps need to transform their accounting practices as well or they will leave valuable capital expenditure dollars on the table.
IBM is changing the terms of its ubiquitous Passport Advantage agreement to remove entitled discounts on over 5,000 on-premises software products, resulting in an immediate price increase for IBM Software & Support (S&S) across its vast customer landscape.
So you’ve gone Agile. You do daily scrums, retrospectives, and all the “right” Agile ceremonies. But still your organization isn’t quite convinced. It is now critical to balance the drivers and goals of both Agile and traditional thinking in order to achieve organizational success.
Do you feel like your Agile teams are treading water – going through the motions but never going anywhere? It’s a risk, and practices such as daily standups, retrospectives, and demonstrations need to be used wisely or you risk losing discipline to meeting fatigue.
Stakeholders expect the speed and responsiveness of product delivery does not come at the expense of quality. QA tools offer retailers the ability to continuously ensure both business and technical quality standards are upheld, but these tools should not be viewed as a silver bullet.
No matter how good your product roadmap and backlog are, they are only as good as your audience’s ability to understand your vision and priority.
The scrum master is like the conductor of an orchestra, ensuring that every piece fits together at the right time to create something greater than the sum of the parts. You don’t have to know how to play each instrument, but you do have to understand what each part contributes to the overall masterpiece.
Tools are important to product teams, but only when they support solid people and processes.
Aha! introduces scenario planning to give product owners the ability to create and compare multiple release approaches based on team capacity and backlog priority.